On 2017-02-26, Jürgen Spitzmüller wrote:
> Am Sonntag, den 26.02.2017, 11:49 +0000 schrieb Guenter Milde:
>> We can either
>> a) Report this as a bug (as even the default fonts will lead to
>> "missing
>> glyph" warnings).
>>
>> b) Overwrite the TU-specific definition with the generic one:
>>
>> \DeclareTextCommand{\textcompwordmark}{TU}{\leavevmode\kern\z@}
>>
>> c) Use \/ instead of \textcompwordmark for the ligature break-up.
>>
>> Possibly
>> - only for "TeX ligature break up"
>> - only with (non-TeX) Unicode fonts.
>>
>> d) Add an exception to our "missing glyph reporting" for
>> U+200C, ZERO WIDTH NON-JOINER
>>
>> In this case, a warning is more appropriate than an error: also
>> the
>> missing character breaks the ligature, so the output looks OK.
>> My preference is d).
> Mine is a).
Of course it would be the simplest option for LyX, if this were fixed soon
upstream. So reporting is in any case advisable.
However, if the LaTeX developers decline to see this as a bug or don't have
the time to fix this before the next TeXLive release, LyX should add a
workaround.
Günter
