On 2016-02-20, Uwe Stöhr wrote: > Am 19.02.2016 um 10:44 schrieb Kornel Benko:
>> This comment seems misleading. With pdflatex it was compilable also >> before this commit. > It was only compilable with many hacks in the preamble. That file was > not compilable in the current modernCV version because of a babel issue > with Spanish. We found now a solution (the preamble line) and could > update the file. OK, then this would be the more accurate description. I am glad you found a way to clean up the document. >> Now 2 more testcases fail. >> 6/7 Test #3357: EXAMPLES_export/examples/es/modernCV_pdf4_systemF >> ......................***Failed 61.93 sec >> 7/7 Test #3356: EXAMPLES_export/examples/es/modernCV_pdf4_texF >> .........................***Failed 61.93 sec >> I know, you don't care. > I still don't understand your goal. The user should be able to click on > the view button and get a nice PDF. Ignacio assures this and as long as > this works we can be happy. > The play with different export methods might be nice for experts while > the average user don't care about how his PDF was internally created. I > don't say that it is bad to play around but it is not important for the > user, only for us to uncover possible bugs. I agree with this regarding changes that lead to a "cleaner" (less hackisch, less ERT, less preamble) document. OTOH, I think it is good to make documents "robust" by ensuring they compile with a variety of export routes - not only for finding bugs but also as a bonus for the user. But, as a bonus means this is on top of the primary purpose of compilable, clean and simple user documentation/templates. > Nevertheless special text classes like e.g. the CVs are not designed to > work with all engines nor to be translatable nor to work with babel > and/polyglossia so I am wondering that our tests expect that. Well, if you look at moderncv, you will see that it is actually designed to work with pdftex, xetex, and luatex. However, the design is hidden in the class and may interfere with LyX's way to handle the differences. Especially, it tries to automate things and internally calls "fontspec" whenever xetex or luatex is detected. This may clash with manually setting fonts in LyX -- something that should be expored and described. Günter
