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.
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. 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.
regards Uwe
