lyx file from 2015 not converted to pdf

Wolfgang Engelmann engelmann at
Tue Mar 24 18:28:14 UTC 2020

Am 24.03.20 um 19:17 schrieb 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

Yes Jürgen, you are right. I unchecked literal and pdf output is ok.
Can I uncheck all 'literal' in the various nomenclature inserts at once?

More information about the lyx-users mailing list