[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: XeTeX encoding problem
From: |
Masamichi HOSODA |
Subject: |
Re: XeTeX encoding problem |
Date: |
Mon, 21 Mar 2016 18:34:18 +0900 (JST) |
> Thanks for working on this. I'd like to avoid going back to the way it
> was done before if possible because this means that all the
> definitions of the Unicode characters are run through every time a
> macro is used. The following patch seems to give good results:
>
> Index: doc/texinfo.tex
> ===================================================================
> --- doc/texinfo.tex (revision 7047)
> +++ doc/texinfo.tex (working copy)
> @@ -7823,7 +7823,9 @@
> % backslash to get it printed correctly.
> % FIXME: This may not be needed.
> address@hidden \catcode`\\=\active \escapechar=`\@
> + \passthroughcharstrue
> \edef\temp{\noexpand\scanmacro{#1}}%
> + \passthroughcharsfalse
> \temp
> \egroup
> }
>
> ===================
>
> but I want to understand what the point of the \edef was in the first
> place, and what the point was of changing the catcode of backslash,
> and test whether this is still necessary. Hopefully I'll get to this
> soon.
Your patch works fine on my environment.
Thank you.
- Re: XeTeX encoding problem, Gavin Smith, 2016/03/06
- Re: XeTeX encoding problem, trueroad, 2016/03/07
- Re: XeTeX encoding problem, Masamichi HOSODA, 2016/03/20
- Re: XeTeX encoding problem, Masamichi HOSODA, 2016/03/20
- Re: XeTeX encoding problem, Gavin Smith, 2016/03/20
- Re: XeTeX encoding problem,
Masamichi HOSODA <=
- Re: XeTeX encoding problem, Gavin Smith, 2016/03/22
- Re: XeTeX encoding problem, Masamichi HOSODA, 2016/03/22
- Re: XeTeX encoding problem, Masamichi HOSODA, 2016/03/22
- Re: XeTeX encoding problem, Gavin Smith, 2016/03/22
- Re: XeTeX encoding problem, Masamichi HOSODA, 2016/03/23
- Re: XeTeX encoding problem, Gavin Smith, 2016/03/22
- Re: XeTeX encoding problem, Karl Berry, 2016/03/25
- Re: XeTeX encoding problem, Gavin Smith, 2016/03/26
- Re: XeTeX encoding problem, Karl Berry, 2016/03/28
- Re: XeTeX encoding problem, Masamichi HOSODA, 2016/03/27