[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: luatex problems with texinfo.tex
From: |
Werner LEMBERG |
Subject: |
Re: luatex problems with texinfo.tex |
Date: |
Thu, 31 Dec 2015 14:48:29 +0100 (CET) |
> 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 converts UTF-8 byte
sequences to Unicode LICR forms) in texinfo.tex should be simply
skipped since it is unnecessary.
> The section and paragraph marks have a character number less than
> 256 in Unicode, so those characters are made active. The obelisk and
> diesis marks have character numbers more than 256, so they aren't
> made active and are set as normal characters.
Note that there is another bug: For 8bit engines, the glyphs for † and
‡ are taken from other fonts, but this substitution mechanism fails
for both luatex and xetex – a simple solution would be to use the CM
super fonts instead of 8bit Computer Modern.
Werner
- luatex problems with texinfo.tex, Werner LEMBERG, 2015/12/30
- Re: luatex problems with texinfo.tex, Karl Berry, 2015/12/30
- Re: luatex problems with texinfo.tex, Gavin Smith, 2015/12/31
- Re: luatex problems with texinfo.tex, Werner LEMBERG, 2015/12/31
- Re: luatex problems with texinfo.tex, Werner LEMBERG, 2015/12/31
- Re: luatex problems with texinfo.tex, Gavin Smith, 2015/12/31
- Re: luatex problems with texinfo.tex, Gavin Smith, 2015/12/31
- Re: luatex problems with texinfo.tex,
Werner LEMBERG <=
- Re: luatex problems with texinfo.tex, Gavin Smith, 2015/12/31
- Re: luatex problems with texinfo.tex, Karl Berry, 2015/12/31