Am Thu, 27 Sep 2018 09:14:01 +0200 schrieb luigi scarso:

On Wed, Sep 26, 2018 at 11:14 PM Ulrike Fischer wrote:

...

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/SourceHanSan... 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

what does the trackers say at your end ?

\enabletrackers[*] \nopdfcompression [...]

a lot ;-) https://www.dropbox.com/s/jgwvytl7hi2doi5/test-utf8.log?dl=0 One can see how the glyphs are replaced under locl: fonts > otf direct > feature 'locl', type 'gsub_single', lookup 's_s_42': replacing U+5203 by single U+F0608 but I can find nothing about tounicode/cmap or something like that. -- Ulrike Fischer http://www.troubleshooting-tex.de/

On Thu, Sep 27, 2018 at 9:42 AM Ulrike Fischer wrote:

Am Thu, 27 Sep 2018 09:14:01 +0200 schrieb luigi scarso:

...

On Wed, Sep 26, 2018 at 11:14 PM Ulrike Fischer wrote:

...

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/SourceHanSan...

...

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

what does the trackers say at your end ?

...

\enabletrackers[*] \nopdfcompression [...]

a lot ;-)

https://www.dropbox.com/s/jgwvytl7hi2doi5/test-utf8.log?dl=0

One can see how the glyphs are replaced under locl:

fonts > otf direct > feature 'locl', type 'gsub_single', lookup 's_s_42': replacing U+5203 by single U+F0608

but I can find nothing about tounicode/cmap or something like that.

ok, then you can see the font as seen by context mtxrun --script fonts --convert SourceHanSans-Regular.otf (keep track also of its output ) -- luigi

On Thu, Sep 27, 2018 at 10:16 AM Ulrike Fischer wrote:

Am Thu, 27 Sep 2018 09:55:02 +0200 schrieb luigi scarso:

...

ok, then you can see the font as seen by context mtxrun --script fonts --convert SourceHanSans-Regular.otf (keep track also of its output )

That is the output of the mtxrun call:

https://www.dropbox.com/s/xszihzv21snxdiv/contextmtx.log?dl=0

fine now, you can use ttx to have an unrelated view of the same font and then you can find the answer .

(ok, this time hans was faster than you, so warm-up for the next time... ) -- luigi

Am Thu, 27 Sep 2018 10:25:51 +0200 schrieb Hans Hagen:

...

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

wait till i update ...

Thanks. Will it be also in the generic fontloader? -- Ulrike Fischer http://www.troubleshooting-tex.de/

Am Thu, 27 Sep 2018 10:25:51 +0200 schrieb Hans Hagen:

these glyphs have no names

Side remark: if you think that the font is wrong here I could add a comment on the github site. -- Ulrike Fischer http://www.troubleshooting-tex.de/