lyx file from 2015 not converted to pdf

[Jürgen Spitzmüller]

Am Dienstag, den 24.03.2020, 19:08 +0100 schrieb Pavel Sanda:
> As we figured out in background, the problem is using ligature 'fl'
> as one character instead of normally using two characters. Replacing
> them fixes the problem.
> 
> Attached is minimal example.
> 
> I was not capable to have lyx segfault because of it.
> 
> Question, I guess either for Juergen or Guenter, is whether
> we should know unicode inside nomenclature and should be fixing
> this issue or this kind of use should not be supported.
> From the users point of view we don't report any useful error.

Of course it shouldn't crash but rather report the uncodable character.
Can you file a report wrt this?

However, if you uncheck "Literal" in the nomencl dialog, then the
character is resolved properly (this is the default mode with newer
documents; older documents are converted with Literal=true as this was
the only possibility back then). "Literal" means that you can enter
LaTeX code.

Jürgen

> 
> Pavel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part
URL: <http://lists.lyx.org/pipermail/lyx-users/attachments/20200324/3054a067/attachment.asc>