ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: [#1] CJK regression? | lmtx-20210613 &c.
Date: Tue, 15 Jun 2021 21:15:18 +0200	[thread overview]
Message-ID: <aafa66bd-3c62-7ed8-76bc-7b50f6d1f0ca@gmail.com> (raw)
In-Reply-To: <6ecb9b4d46642c25db1a400d0b23012f2b4430cb.camel@indica-et-buddhica.org>

Richard Mahoney schrieb am 13.06.2021 um 21:42:
> 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).
> 
> This is what I have in the setups:
> 
> % Support for Japanese
> 
> \setscript[hanzi]
> 
> \starttypescript[serif][sourcehanserifregular]
> 
> \definefontsynonym[Serif][name:sourcehanserifregular][features={aalt,hist,kern,liga}]
> 
> \stoptypescript
> 
> \definetypeface[sourcehanserifregular][rm][serif][sourcehanserifregular]
> 
> \define[1]\JA{\language[ja]{{\setscript[hanzi]\sourcehanserifregular #1}}}


You can try to play with this font setup, all settings within the 
setups-block are applied when you change the language.


% font setup for english ...

\definefontfamily [source] [rm] [Source Serif]

\switchtobodyfont [source]

% font setup for japanese

\definefontfamily [source-han] [rm] [Source Han Serif]

\startsetups [japanese]
   \switchtobodyfont [source-han]
   \setscript [hanzi]
\stopsetups

\setuplanguage
   [ja]
   [setups=japanese]

\starttext
English {\ja 日本語}
\stoptext

Wolfgang
___________________________________________________________________________________
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
___________________________________________________________________________________

      parent reply	other threads:[~2021-06-15 19:15 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
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 [this message]

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=aafa66bd-3c62-7ed8-76bc-7b50f6d1f0ca@gmail.com \
    --to=wolfgang.schuster.lists@gmail.com \
    --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).