ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: (bug?) wrong hyphenation with external fonts
Date: Thu, 4 Feb 2016 22:13:56 +0100	[thread overview]
Message-ID: <56B3BF14.5000606@wxs.nl> (raw)
In-Reply-To: <56B3B438.30605@gmx.es>

On 2/4/2016 9:27 PM, Pablo Rodriguez wrote:
> On 02/03/2016 02:18 PM, Hans Hagen wrote:
>> On 2/2/2016 12:28 PM, Pablo Rodriguez wrote:
>>> Dear list,
>>> [...]
>>> Hyphenation is wrong with fonts that don’t come with the ConTeXt
>>> distribution. TeX Gyre Pagella is hyphenated right, but MinionPro or
>>> even TeX Gyre Pagella Math are wrong hyphenated.
>>>
>>> I’m afraid it may be a bug. Could anyone confirm it?
>>
>> to what extend hyphenation is supported depends on the interaction
>> between ligature building / kerning / trickery and possible hyohenation
>> points; the font handler tries to do its best
>
> Many thanks for your reply, Hans.
>
> I reported the issue in the opposite way it happens:
>
>      \definefontfamily[mainface][rm][MinionPro]
>      \definefontfamily[anotherface][rm][TeX Gyre Pagella]
>      \setupbodyfont[mainface]
>
>      \starttext
>      \startTEXpage[offset=1em]
>      \hyphenatedword{LibreOffice libre office}
>
>      \setupbodyfont[anotherface]%
>      \hyphenatedword{LibreOffice libre office}
>      \stopTEXpage
>      \stoptext
>
> The ff-ligature prevents hyphenation with TeX Gyre Pagella, but not with
> MinionPro. (This is the opposite of what I reported before.)

it depends on the complexity of the ligature .. ff is not so much an 
issue but you can have ff + i = ffi etc and we need to deal with kerning 
too (it depends a bit on how the opentype features are applied and we 
can handle quite some weird ligature implementations)

the latest mechanism in context can deal with quite some situations but 
at some point has to make decisions (in order not to loose for instance 
kerns; double chained ligatures would result in way more overhead and is 
not worth the trouble)

one might wonder if we never had these  f[fil] ligatures of if ancient 
technology had provides hundreds of them combining upto 4 characters etc 
etc.

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
       tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2016-02-04 21:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-02 11:28 Pablo Rodriguez
2016-02-03 13:18 ` Hans Hagen
2016-02-04 20:27   ` Pablo Rodriguez
2016-02-04 21:13     ` Hans Hagen [this message]
2016-02-05  7:47       ` Pablo Rodriguez
2016-02-05  8:42         ` 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=56B3BF14.5000606@wxs.nl \
    --to=pragma@wxs.nl \
    --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).