From: Hans Hagen <j.hagen@xs4all.nl>
To: Richard Mahoney <rmahoney@indica-et-buddhica.org>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: [#1] CJK regression? | lmtx-20210613 &c.
Date: Mon, 14 Jun 2021 17:28:06 +0200 [thread overview]
Message-ID: <2512c1e0-e78f-8ba8-5c85-9b95f6048f3e@xs4all.nl> (raw)
In-Reply-To: <8c2653e6-6172-16eb-5337-2c8c392fb69e@xs4all.nl>
On 6/13/2021 10:54 PM, Hans Hagen wrote:
> On 6/13/2021 9:42 PM, Richard Mahoney wrote:
>> I'm wondering if there has been a regression in the rendering of
>> CJK recently? I'm attaching two screenshots from the same code:
>> one with lmtx-20210509 (correct); and the other lmtx-20210613
>> (incomplete).
> no, it's a side effect of something else (which shows up with these
> extremeely large fonts > 65k glyphs) .. i'll look into it tomorrow
I uploaded a new lmtx ... kind of experimental because I changes some of
the background bist that deals with embedding. The problem is that we
need to deal with the previously reported clash between different
unicode entries that share shapes (normally no issue but in this case it
was a side effect of 'effective' monospaces where the font decided that
invisible shapes should he visual anyway) as well as with the fact that
soem cjk fonts have many duplicates which makes us cross the 65 boundary.
The variant approach is ok but I might have overlooked some soecial
cases. Because this also drops 'stream compatibility' between mkiv and
lmtx (which had already become somewhat loose) I can now also clean up
(simplify) some other parts of the font system but let's do that
stepwise (I'm in no hurry here).
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:[~2021-06-14 15:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-13 19:42 Richard Mahoney
2021-06-13 20:54 ` Hans Hagen
2021-06-14 15:28 ` Hans Hagen [this message]
2021-06-14 22:21 ` Richard Mahoney
2021-06-15 7:13 ` Hans Hagen
2021-06-15 8:25 ` luigi scarso
2021-06-15 11:07 ` Hans Hagen
2021-06-15 17:53 ` Alan Braslau
2021-06-15 18:29 ` Hans Hagen
2021-06-15 18:47 ` luigi scarso
2021-06-15 19:00 ` Hans Hagen
2021-06-16 15:14 ` luigi scarso
2021-06-16 20:53 ` Alan Braslau
2021-06-17 9:33 ` luigi scarso
2021-06-17 10:09 ` luigi scarso
2021-06-15 18:54 ` Alan Braslau
2021-06-15 18:57 ` Hans Hagen
2021-06-15 19:17 ` Alan Braslau
2021-06-15 19:15 ` Wolfgang Schuster
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=2512c1e0-e78f-8ba8-5c85-9b95f6048f3e@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=ntg-context@ntg.nl \
--cc=rmahoney@indica-et-buddhica.org \
/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).