[Top][All Lists]

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

Re: luatex problems with texinfo.tex

From: Gavin Smith
Subject: Re: luatex problems with texinfo.tex
Date: Sat, 2 Jan 2016 10:36:59 +0000

On 2 January 2016 at 06:20, Werner LEMBERG <address@hidden> wrote:
>>     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 support,
>> all the engine support, etc., to take account of native UTF-8.
>> [...]
> Masamichi-san did some experiments.  Here is what he sent to the
> lilypond-devel list.
>   I've made attached quick hack patch for texinfo.tex.  The following
>   command [to compile the lilypond documentation] does not occur
>   `Undefined control sequence.'  with the patch.

Thanks for working on this. This patch uses native LuaTeX support for
Unicode. If we wanted to support this in texinfo.tex, it should
probably be optional. The only think I can think of right now would be
an option enabled something like

@end tex

Unless someone has a nicer way of doing it?

Maybe whether a "@documentencoding UTF-8" line is given should affect
whether native Unicode is used by default.

The changes in the patch should be conditional upon whether native
Unicode support is enabled, and whether LuaTeX is being used.

Are these changes likely to work for most LuaTeX installations, e.g.
will luaotfload.sty exist for everyone?

reply via email to

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