From: Pablo Rodriguez <oinos@gmx.es>
To: ntg-context@ntg.nl
Subject: Re: bug with hz in LMTX?
Date: Tue, 13 Oct 2020 16:47:12 +0200 [thread overview]
Message-ID: <1a9339eb-214e-976c-69e1-573fcd9696da@gmx.es> (raw)
In-Reply-To: <8786f4ba-fa79-00cc-b45a-e7d629350605@xs4all.nl>
On 10/13/20 1:36 PM, Hans Hagen wrote:
> On 10/12/2020 4:59 PM, Pablo Rodriguez wrote:
>> [...]
>> On page 36 (https://pdf.ousia.tk/wrong-font-expansion.pdf#page=36),
>> lines 4, 11 and 20 are wrong.
>>
>> Current LMTX (LuaTeX 2.07 20200920 + ConTeXt MkIV 2020.09.20 23:02) has
>> the issue, while MkIV (LuaTeX 1.11 7226 + ConTeXt MkIV 2020.01.30 14:13)
>> has no problem with that.
>>
>> I think this might be a bug. Could you confirm the issue?
> I need to keep count of how frequently i suggest typo also
>
> \setupalign[verytolerant,stretch]
>
> when one uses hz and/or protrusion. I don't know why folks expect
> expansion and protrusion to give better (or intended) output when the
> other constraints are such that tex either not even ends up in the phase
> where expansion is applied, or when fitting the constraints is only
> possible with excessive and visible expansion. When expansion is max or
> min and there is not enough spacing to stretch and shrink the results
> will not get better. Read: expansion is a last resort in getting things
> right. Also, protrusion actually add to the constraints so that is never
> a way to get a better fit.
Many thanks for your reply, Hans.
If both expansion and protrusion add problems to line breaking, I’m
disabling both features in my documents.
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-10-13 14:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 14:59 Pablo Rodriguez
2020-10-13 11:36 ` Hans Hagen
2020-10-13 14:47 ` Pablo Rodriguez [this message]
2020-10-13 15:15 ` 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=1a9339eb-214e-976c-69e1-573fcd9696da@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).