From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Pablo Rodriguez <oinos@gmx.es>
Subject: Re: font expansion MkXL vs. MkIV
Date: Sun, 16 Feb 2020 23:00:52 +0100 [thread overview]
Message-ID: <43e41514-06bf-064d-6ae9-03f723aa877e@xs4all.nl> (raw)
In-Reply-To: <47ca69dd-b7da-05eb-9b19-b8f930a5edef@gmx.es>
On 2/16/2020 9:22 PM, Pablo Rodriguez wrote:
> Hi Wolfgang and Hans,
>
> I have the following sample:
>
> \setuppapersize[A5]
> \definefontfeature[default][default]
> [protrusion=quality, expansion=quality]
> \definefontfamily[mainface][rm][Source Serif Pro]
> \setupalign[hanging, hz]
> \setupbodyfont[mainface, 17pt]
> %~ \setupbodyfont[helvetica, 17pt]
> \starttext
> \input zapf
> \stoptext
>
> hz doesn’t work fine in MkXL, but it works fine in MkIV.
>
> I think the flow of characters is broken in MKXL. Some
>
> With TeX Gyre Heros (https://pdf.ousia.tk/mkiv-hz.pdf and
> https://pdf.ousia.tk/mkxl-hz.pdf):
>
> - "computer": line 5.
> - "basic": line 8.
> - "showing": line 10.
>
> With Source Serif Pro, also (https://pdf.ousia.tk/ssp-mkiv-hz.pdf and
> https://pdf.ousia.tk/ssp-mkxl-hz.pdf):
>
> - "publishing": line 2.
> - "about": line 4.
> - "between": line 10.
>
> I’m experiencing this wherever I use hz with MkXL.
>
> Sorry, but cannot the default values for quality font expansion be the
> same in MkIV and MkXL?
>
> Many thanks for your help,
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]
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2020-02-16 22:00 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 [this message]
2020-02-17 15:51 ` Pablo Rodriguez
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=43e41514-06bf-064d-6ae9-03f723aa877e@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=ntg-context@ntg.nl \
--cc=oinos@gmx.es \
/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).