I agree it should be skipped.
In some ideal world, but in this world, I think doing so would lead to
huge problems. For the present, it seems far more feasible to me to
keep using the UTF-8 code in texinfo.tex for the immediate problem than
refactor all the font stuff, all the character supp
On 31 December 2015 at 13:48, Werner LEMBERG wrote:
>
>> So here's what's happening. When @documentencoding UTF-8 is given,
>> it makes bytes 128-255 active. However, for LuaTeX, it's actually
>> making characters 128-255 active.
>
> Do we need active characters in that range at all for luatex (a
> So here's what's happening. When @documentencoding UTF-8 is given,
> it makes bytes 128-255 active. However, for LuaTeX, it's actually
> making characters 128-255 active.
Do we need active characters in that range at all for luatex (and
xetex)? The UTF8 support (this is, the code that convert
On 31 December 2015 at 12:58, Gavin Smith wrote:
> On 31 December 2015 at 11:17, Werner LEMBERG wrote:
>>
>>> I think the "Undefined control sequence" message comes for an active
>>> character (that is, a byte with category code 13) which doesn't have a
>>> definition. This would be hex c2.
>>
>>
On 31 December 2015 at 11:17, Werner LEMBERG wrote:
>
>> I think the "Undefined control sequence" message comes for an active
>> character (that is, a byte with category code 13) which doesn't have a
>> definition. This would be hex c2.
>
> Can you really make byte 0xC2 active in luatex? This wou
>> You could try the attached file and send the log here to see if we
>> can find any enlightenment from it. [...]
XeTeX fails in a similar way, see attached log.
Werner
This is XeTeX, Version 3.14159265-2.6-0.2 (TeX Live 2015) (preloaded
format=xetex 2015.12.31) 31 DEC 2015 12:18
en
> I think the "Undefined control sequence" message comes for an active
> character (that is, a byte with category code 13) which doesn't have a
> definition. This would be hex c2.
Can you really make byte 0xC2 active in luatex? This would completely
break Unicode support, since 0xC2 is an incomp
On 30 December 2015 at 23:24, Werner LEMBERG wrote:
>
> Processing the attached document with luatex, I get
>
> ! Undefined control sequence.
> l.7 which assigns the symbols *, †, ‡, §
> , ¶ to
>
> It works just fine with pdtex. A bug?
I think the
