On Tue, Dec 3, 2013 at 10:16 AM, Guenter Milde <mi...@users.sf.net> wrote:
> On 2013-12-03, Scott Kostyshak wrote:
>> On Sat, Nov 30, 2013 at 2:01 AM, Scott Kostyshak <skost...@lyx.org> wrote:
>>> On Fri, May 17, 2013 at 8:49 PM, Scott Kostyshak <skost...@lyx.org> wrote:
>>>> On Sun, Apr 14, 2013 at 3:39 AM, Scott Kostyshak <skost...@lyx.org> wrote:
>>>>> I get utf-8 and utf8x errors.
>
>>>>> Is there a fix for this while preserving export with pdflatex and latex?
>
>>>> Any ideas?
>
>>> It is still failing for me with LuaTeX and XeTeX.
>>> Adding the option "latin2" fixes it for me. Is that the right thing to do?
>>> The following seems relevant:
>>> (from http://mirrors.ctan.org/macros/latex/contrib/europecv/europecv.pdf)
>>> The default input encoding for the europecv class is UTF-8. If you have
>>> a Unicode capable text editor, you should be able to directly type text
>>> with accents, diacritics and so on (i.e., no need to use LATEX commands for
>>> special characters). In order for this to work, you must ensure that your
>>> document is saved using the UTF-8 text encoding. As an alternative, you
>>> may specify a different input encoding for your document (see options
>>> below). Please note that the ucs and inputenc packages are needed no
>>> matter which encoding you use (see Section 5).
>
>> I will change the encoding to "latin2" unless someone objects.
>
> I propose to change Document>Settings>Language>encoding to utf8x.
> This way it is in line with the default setting of europecv
> (where the utf8 option selects utf8x).

Document > Settings > Language > encoding is currently set to "Unicode
(ucs-extended) (utf8x)". So if I understand correctly, you suggest not
changing this.

What option do you suggest passing to the class?

Are you able to compile with XeTeX and LuaTeX?

> Additionally, I would file a bug report/request to the europecv author to
> ask for an option to bypass the internal call to inputenc so that
> customization (like using the standard utf8 option) becomes possible.

OK I will look into this.

Scott

Reply via email to