From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Not wanted hidden spaces when you compress fonts
Date: Fri, 6 Jan 2012 12:46:39 +0100 [thread overview]
Message-ID: <B5FC216F-3D1B-4DEB-87B4-7D2E95461B4E@googlemail.com> (raw)
In-Reply-To: <20120106112310.GA27824@eureca.de>
Am 06.01.2012 um 12:23 schrieb Susan Dittmar:
> Dear Jan,
>
>> when I turn off the compression [extend=0.8] -> [extend=1]
>> the problems are gone :-) ... the compression unfourtunately
>> also :-(
>> What do I have to configure to get the compression without
>> spaces? :-)
>
> I guess you will need a new font, or a new version of the same font with
> compression. I am sure there are tools out there that can do the
> compression of a font.
>
> As far as I understand, TeX itself knows nothing about the glyphs. They are
> just some boxes for the TeX engine. It does not handle the glyphs itself --
> TeX just places them. So the only way TeX has to compress fonts is to push
> the glyphs closer together -- thus introducing these 'spaces' (in fact,
> they are negative spaces, places where TeX interrupts words to push the
> glyphs closer together).
>
> In very special cases you might be able to use postscript's (or pdf's)
> transformation engine to archieve condensed fonts. I once used that by
> creating a minipage with 'normal' font within a picture environment that
> itself then did the transformation. But I guess that's not what you really
> are after.
As you can in the example below the font is stretched to the given value
but the problem when you copy the text can be in the algorithm Adobe Reader
use to determine spaces in the text.
\starttext
\define[1]\ExtendFont
{\definefontfeature[condensed][default][extend=#1]
\definedfont[name:allerlight*condensed]The quick brown fox jumps over the lazy dog.\endgraf}
\processcommalist[0.4,0.6,0.8,1.0,1.2,1.4]\ExtendFont
\stoptext
Wolfgang
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2012-01-06 11:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-06 10:55 Jan Heinen
2012-01-06 11:23 ` Susan Dittmar
2012-01-06 11:46 ` Wolfgang Schuster [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-01-05 2:25 Jan Heinen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B5FC216F-3D1B-4DEB-87B4-7D2E95461B4E@googlemail.com \
--to=schuster.wolfgang@googlemail.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).