[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: XeTeX encoding problem

From: Gavin Smith
Subject: Re: XeTeX encoding problem
Date: Fri, 15 Jan 2016 18:24:32 +0000

On 15 January 2016 at 18:13, Masamichi HOSODA <address@hidden> wrote:
>> the following is created in the output auxiliary table of contents file:
>> @numchapentry{f@"ur}{1}{}{1}
>> Without it, it would be
>> @numchapentry{für}{1}{}{1}
>> Do you understand now how changing the active definitions can change
>> what's written to the output files?
> Thank you for your demonstration.
> I understand it.
> Exactly, it can be effective.
> I've come up with another idea.
> If I understand correctly, in current texinfo.tex,
> 0xC3 and 0xBC are set to active and are replaced with \"u.
> This behavior change as following:
> If native Unicode support is enabled,
> U+00FC is set to active and is replaced with \"u.

U+00FC being the codepoint of ü. Yes, it is possible, with the right
conditionals. But I thought we were talking about getting it to work
when native Unicode is not enabled. I don't see the need to setting an
active definition when native Unicode support is enabled, either for
writing to auxiliary files or for the final output. When native
Unicode is used, the character would just be written out as-is, read
in as the Unicode character and the corresponding glyph from the
Unicode font would be typeset.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]