Am Samstag, den 25.02.2017, 15:39 -0500 schrieb Scott Kostyshak: > After a TL update today, I now get missing glyphs errors from > > latex/languagenesting2_pdf5_systemF > > We could ignore the glyphs errors, but it would be nice to figure out > if > the change is expected or if this is a bug that should reported.
The crucial glyph is U+200C, ZERO WIDTH NON-JOINER, which is used to
break ligatures.
With TU encoding, this glyph is produced by the \textcompwordmark
macro:
\DeclareTextSymbol{\textcompwordmark} \UnicodeEncodingName{"200C}
We produce that macro with our ligature break special character and to
break up unwanted ligatures in the code, as for subsequent "<" (which
is the case in the test in question, which break at this chunk in sec.
3.1.5.1:
<<Mein Code>>=
Noch mehr Code
@
I don't know if it's a bug proper, but you could point the latex core
developers to the fact that this glyph is not covered by some (most?)
fonts and that it could be considered to break up ligatures by other
means (i.e., TeX's).
Jürgen
>
> Scott
signature.asc
Description: This is a digitally signed message part
