ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Ulrike Fischer <news3@nililand.de>
To: ntg-context@ntg.nl
Subject: tounicode mapping missing for locl-variants
Date: Wed, 26 Sep 2018 23:13:58 +0200	[thread overview]
Message-ID: <1s2c2u9a7qcb1.dlg@nililand.de> (raw)


When I compile the following document I see in the output localized
variants for the various glyphs. But copy & paste works only for the
last line. The first two gives notdef chars. 

In the pdf e.g. the first glyph has the numbers 2D0E, 2D0F, 2D0D in
the three lines but only for the last there is a unicode mapping:
<2D0D> <5203>.

What can one do to get a mapping also for the other glyphs? 

The font can be downloaded here
https://github.com/adobe-fonts/source-han-sans/blob/release/OTF/SourceHanSansJ.zip
A related bug report is
https://github.com/adobe-fonts/source-han-sans/issues/200


\pdfvariable compresslevel 0
\pdfvariable objcompresslevel 0
\setupheader[state=stop]
\starttext

\font\zhs=
{file:SourceHanSans-Regular.otf:mode=node;script=hani;language=ZHS;+locl}
\zhs 刃令毒骨縣誤

\font\zht=
{file:SourceHanSans-Regular.otf:mode=node;script=hani;language=ZHT;+locl}
\zht 刃令毒骨縣誤

\font\test=
{file:SourceHanSans-Regular.otf:mode=node;script=hani;language=DFLT;}
\test 刃令毒骨縣誤

\stoptext


-- 
Ulrike Fischer 
https://www.troubleshooting-tex.de/

___________________________________________________________________________________
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:[~2018-09-26 21:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-26 21:13 Ulrike Fischer [this message]
2018-09-27  7:14 ` luigi scarso
2018-09-27  7:42   ` Ulrike Fischer
2018-09-27  7:52     ` Hans Hagen
2018-09-27  7:55     ` luigi scarso
2018-09-27  8:15       ` Ulrike Fischer
2018-09-27  8:29         ` luigi scarso
2018-09-27  8:25 ` Hans Hagen
2018-09-27  8:32   ` Ulrike Fischer
2018-09-27  8:54     ` Hans Hagen
2018-09-27  8:44   ` Ulrike Fischer
2018-09-27  8:53     ` 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=1s2c2u9a7qcb1.dlg@nililand.de \
    --to=news3@nililand.de \
    --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).