From: Pablo Rodriguez <oinos@gmx.es>
To: ntg-context@ntg.nl
Subject: Re: font expansion MkXL vs. MkIV
Date: Mon, 17 Feb 2020 16:51:16 +0100 [thread overview]
Message-ID: <79e0f242-9105-944b-fe52-b8da5362f2a6@gmx.es> (raw)
In-Reply-To: <43e41514-06bf-064d-6ae9-03f723aa877e@xs4all.nl>
On 2/16/20 11:00 PM, Hans Hagen wrote:
> [...]
> in lmtx there is more precise handling of edge cases (protrusion) that
> are ignored in mkiv ... so any difference that you observe can simply be
> a side effect of tex deciding otherwise (because these calculations do
> influence linebreaks)
>
> anyway, you should use 'stretch' to because otherwise expansion and
> protrusion has not enough options to do better (the linebreak third pass
> that is)
>
> \setupalign[hanging, stretch, hz]
Many thanks for your reply, Hans.
I’m afraid that "stretch" doesn’t make any difference with TeX Gyre
Heros (https://pdf.ousia.tk/stretch-mkxl-hz.pdf) and it only corrected
one problematic case with Source Serif Pro
(https://pdf.ousia.tk/stretch-ssp-mkxl-hz.pdf).
Sorry if I hadn’t expressed myself accurately before. The issue here
isn’t having exactly the same output in both MkIV and MkXL. The real
problem is that characters are misplaced in MkXL with hz enabled. I
think this might be a bug.
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2020-02-17 15:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-16 20:22 Pablo Rodriguez
2020-02-16 22:00 ` Hans Hagen
2020-02-17 15:51 ` Pablo Rodriguez [this message]
2020-02-17 18:49 ` Hans Hagen
2020-02-17 21:56 ` Pablo Rodriguez
2020-02-18 7:45 ` 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=79e0f242-9105-944b-fe52-b8da5362f2a6@gmx.es \
--to=oinos@gmx.es \
--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).