On 2019-01-23, Kornel Benko wrote: > Am Dienstag, 22. Januar 2019 21:34:53 CET schrieb Guenter Milde > <mi...@users.sf.net>: >> On 2019-01-22, Kornel Benko wrote: >> > Am Dienstag, 22. Januar 2019 11:07:33 CET schrieb Guenter Milde >> > <mi...@users.sf.net>: >> >> On 2019-01-21, Scott Kostyshak wrote:
>> >> > Currently, if I try to compile lib/examples/fa/splash.lyx to PDF I get >> >> > the following error with pdflatex: >> >> > ! LaTeX Error: Encoding scheme `LAE' unknown. ... >> >> > In Settings > Fonts > LaTeX font encoding we currently set it to custom >> >> > and choose "OT1". If I change this instead to "Automatic", compilation >> >> > to PDF seems to work fine (although I cannot tell if the output is >> >> > reasonable). ... >> >> > Is there a reason to keep the custom LaTeX font encoding as "OT1" or can >> >> > we change it to "Automatic"? >> >> There is a reason (avoid bitmap fonts with CM) but we can change it to >> >> "auto" because a bitmap font is less of a problem than a non-compiling >> >> document. >> >> Could you try whether `fa/splash.lyx` compiles with roman fonts set to >> >> LatinModern, please? This would avoid bitmap fonts also with "auto" font >> >> encoding. >> > Same error message, does not compile, does not create pdf. >> This is strange. Maybe you did not change the "Font encoding" setting from >> OT1 to auto? > Sure, your post did suggest only the change of font. Sorry for beeing misleading: Setting the encoding to "auto" works around the non-compilation bug but leads to bitmap fonts for Latin text parts. Additionally setting the font to LatinModern prevents the bitmap (Type 3) fonts. > And setting the font encoding to auto worked also before the font change. > Now it compiles. Thank you for confirming. I committed the change. Ahoj, Günter
