ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
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: Mon, 17 Feb 2020 19:49:02 +0100	[thread overview]
Message-ID: <9c1df0d0-5cfd-7412-a275-93a00c98aef6@xs4all.nl> (raw)
In-Reply-To: <79e0f242-9105-944b-fe52-b8da5362f2a6@gmx.es>

On 2/17/2020 4:51 PM, Pablo Rodriguez wrote:
> 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.
hm, i uploaded a maybe better variant

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
___________________________________________________________________________________

  reply	other threads:[~2020-02-17 18:49 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
2020-02-17 18:49     ` Hans Hagen [this message]
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=9c1df0d0-5cfd-7412-a275-93a00c98aef6@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).