>> I\\\'ve finally finished this. It does appear a bit faster as well as >> being simpler. Where it could potentially break is chapter names with >> non-ASCII characters, and index entries with non-ASCII characters, as >> well as macros using non-ASCII characters (either in the macro >> definition or in the arguments), as well as macros giving chapter >> names and index entries. I\\\'ll do a bit more testing later. >> >> Masamichi, does the native multibyte support still work well? Is there >> any more that you wanted to do with it? If it looks good we should >> look to releasing it as an official version for non-developers. > > LGTM > > Native Unicode support works fine with some texi source including Japanese. > Thank you.
I've noticed that the definition of \ifpassthroughchars is duplicated. Here is the patch for fix it. ChangeLog: Remove duplicated definition of \ifpassthroughchars 2016-03-XX Masamichi Hosoda <[email protected]> * doc/texinfo.tex (\ifpassthroughchars): Remove duplicated definition.
--- texinfo.tex.org 2016-03-08 22:46:15.850782600 +0900 +++ texinfo.tex 2016-03-14 22:34:30.708418900 +0900 @@ -10865,9 +10865,6 @@ \unicodechardefs } -\newif\ifpassthroughchars -\passthroughcharsfalse - % For native Unicode (XeTeX and LuaTeX) % Definition macro to replace / pass-through the Unicode character %
