On 2013-12-06, Scott Kostyshak wrote: > On Thu, Dec 5, 2013 at 1:45 PM, Guenter Milde <mi...@users.sf.net> wrote: >> On 2013-12-05, Scott Kostyshak wrote:
> The contact email bounced, and I found this (that Nicola is no longer > maintaining the package): > http://users.dimi.uniud.it/~nicola.vitacolonna/software/europecv/ So we could consider doing the changes ourself. The internal loading of "utf8x" happens, because some language files provide the localization strings in utf8 encoding. My idea for a change would be: * Remove the hard-coded call to utf8x, * remove the "inputenc" options, * check which language files use utf-8 instead of LICR and a) document that for language(s) ... one of inputenc-utf8, inputenc-utf8x, or Xe/LuaTeX (with Unicode fonts) is required, or b) transform the language strings to LICR ... > I sent it to our Spanish translator. I'll commit a change with the > note and explain in our testing files why the test does not pass. Could you also have a look at europecv in other languages? The problem is not confined to Spanish, the current version of europecv does not work with non-TeX fonts in any language and does not (or not stable) work with Xe/LuaTeX in 8-bit compatibility mode either -- even if the tests did not find this problem. Günter
