texinfo.tex ver. 2016-02-07.16 can not compile following attached files.
test-U201E.texi
test-set-value.texi
I've fixed it.
Here's the patch for texinfo.tex ver. 2016-02-07.16.
ChangeLog:
Improve XeTeX PDF outline support
2016-02-XX Masamichi Hosoda
* doc/texinfo.tex:
Impro
On 7 February 2016 at 15:53, Masamichi HOSODA wrote:
>>> I'm not sure if this is correct: shouldn't the conditional be inside a
>>> single definition, instead of two definitions (starting \gdef~ and
>>> \edef~) inside the conditional?
>>
>> Sorry.
>> It's comletely incorrect.
>> It can not swith t
>> I'm not sure if this is correct: shouldn't the conditional be inside a
>> single definition, instead of two definitions (starting \gdef~ and
>> \edef~) inside the conditional?
>
> Sorry.
> It's comletely incorrect.
> It can not swith to ``pass-through''.
>
> Even if to use \gdef for ``pass-thr
>> \def\DeclareUnicodeCharacterNative#1#2{%
>>\catcode"#1=\active
>> - \begingroup
>> -\uccode`\~="#1\relax
>> -\uppercase{\gdef~}{#2}%
>> - \endgroup}
>> + \ifnativeunicodereplace
>> +\begingroup
>> + \uccode`\~="#1\relax
>> + \uppercase{\gdef~}{#2}%
>> +\endgroup
On 7 February 2016 at 14:20, Masamichi HOSODA wrote:
> \def\DeclareUnicodeCharacterNative#1#2{%
>\catcode"#1=\active
> - \begingroup
> -\uccode`\~="#1\relax
> -\uppercase{\gdef~}{#2}%
> - \endgroup}
> + \ifnativeunicodereplace
> +\begingroup
> + \uccode`\~="#1\relax
> +
On 7 February 2016 at 14:20, Masamichi HOSODA wrote:
>> I have a different suggestion for fixing this issue: execute
>> \unicodechardefs only once in each run, and make the expansion of each
>> character use a condition. The value of the condition can be changed
>> to control what the characters d
> I have a different suggestion for fixing this issue: execute
> \unicodechardefs only once in each run, and make the expansion of each
> character use a condition. The value of the condition can be changed
> to control what the characters do without redefining all of the
> characters.
>
> The sam
On 31 January 2016 at 13:25, Masamichi HOSODA wrote:
>> If the empty lines are really the cause, I agree that it deserves a
>> separate commit since it doesn't seem to be related to the encoding
>> problem.
>
> The issue occurs in native Unicode only.
>
> If native Unicode is enabled,
> \nativeuni
