From: Khaled Hosny <khaledhosny@eglug.org>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Wrong spacing using stretch effect
Date: Tue, 1 Oct 2013 11:45:45 +0200 [thread overview]
Message-ID: <20131001094545.GA16124@khaled-laptop> (raw)
In-Reply-To: <524A93F4.1010705@wxs.nl>
On Tue, Oct 01, 2013 at 11:20:52AM +0200, Hans Hagen wrote:
> On 10/1/2013 10:05 AM, Marco Patzer wrote:
> >On 2013–09–30 Hans Hagen wrote:
> >
> >>these are unrelated mechanisms where the first one just does some
> >>pdf magic ... no feedback to tex about widths (ok, i could write
> >>something better but never had and still don't have a reason for
> >>that kind of low level pdf based approach to be really deeply
> >>integrated)
> >
> >Thanks for the explanation. I was looking for a way to do slight
> >letter spacing without breaking ligatures and thought I could
> >leverage the stretch effect for that.
>
> well, we break ligatures because ligatures make no sense in that
> kind of kerned text (if they make sense at all, but that's a
> different issue
Some ligatures should not be broken in letter-spaced text, typically
represented by rlig in OpenType, e.g. Fraktur ch, ck, ſt and tz
ligatures:
http://unifraktur.sourceforge.net/letterspacing.html
Regards,
Khaled
___________________________________________________________________________________
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:[~2013-10-01 9:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 10:32 Marco Patzer
2013-09-30 8:36 ` Hans Hagen
2013-10-01 8:05 ` Marco Patzer
2013-10-01 9:20 ` Hans Hagen
2013-10-01 9:45 ` Khaled Hosny [this message]
2013-10-01 9:53 ` Philipp Gesang
2013-10-01 10:17 ` Marco Patzer
2013-10-01 17:58 ` Hans Hagen
2013-10-03 16:47 ` Hans Hagen
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=20131001094545.GA16124@khaled-laptop \
--to=khaledhosny@eglug.org \
--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).