>> Thank you for your comments.
>> I've updated the patch.
>>
>> I want the following.
>> UTF-8 auxiliary file.
>> Handling Unicode filename (image files and include files).
>> Handling Unicode PDF bookmark strings.
>
> Thanks for working on this. I've had a look at the most recent patch,
>
Sorry, it is not so good.
LANG can be changed often.
For example, I use es, de, cz when read e-mails from European friends.
And use "C" when install softwares.That is, locale is ja & I have UTF-8 locale,
but LANG is C when intall texinfo.
--- Kiyoshi
- Original Message -
> From: Ki
How about deduce the name from `locale -a|grep $LANG` ?
--- Kiyoshi
- Original Message -
> From: Gavin Smith
> To: Kiyoshi KANAZAWA
> Cc: "bug-texinfo@gnu.org"
> Date: 2016/1/23, Sat 07:13
> Subject: Re: texinfo-6.0.92 make check has 12 FAILs on Solaris10 x86/x64
>
> On 22 January
On 22 January 2016 at 22:04, Kiyoshi KANAZAWA
wrote:
> % locale
> LANG=ja
> LC_CTYPE="ja"
> LC_NUMERIC="ja"
> LC_TIME="ja"
> LC_COLLATE="ja"
> LC_MONETARY="ja"
> LC_MESSAGES="ja"
> LC_ALL=
>
>
> % locale -a
> C
> POSIX
> iso_8859_1
> ja
> ja_JP.PCK
> ja_JP.UTF-8
> ja_JP.eucJP
>
Okay, you have a U
% locale
LANG=ja
LC_CTYPE="ja"
LC_NUMERIC="ja"
LC_TIME="ja"
LC_COLLATE="ja"
LC_MONETARY="ja"
LC_MESSAGES="ja"
LC_ALL=
% locale -a
C
POSIX
iso_8859_1
ja
ja_JP.PCK
ja_JP.UTF-8
ja_JP.eucJP
I used to install everything on my Solaris,
but minimum since I switched the storage from HDD to SSD.
--- Ki
On 18 January 2016 at 14:12, Masamichi HOSODA wrote:
>> If I understand correctly, you are changing the category codes of the
>> Unicode characters when writing out to an auxiliary file, but only for
>> those Unicode characters that are defined. This leads the Unicode
>> character to be written ou
On 20 January 2016 at 23:04, Kiyoshi KANAZAWA
wrote:
> Hello, Gavin.
>
> All of the FAILs say: "Couldn't set UTF-8 character type in locale.", such as
> ===
>
> % t/stdout.sh
> 1d0
> < Couldn't set UTF-8 character type in locale.
>
> ===
> log & diffs files are attached.
Thanks for sending the lo
> I think it misses some percent signs, e.g.
>
> \def\utfeightchardefs{% <- here
> \let\DeclareUnicodeCharacter\DeclareUnicodeCharacterUTFviii
> \unicodechardefs
> }
>
> Maybe they aren't necessary, but I would add them for consistency.
Thank you for your advice.
Here is fix
On 21 January 2016 at 22:13, Karl Berry wrote:
> Web browsers don't hyphenate words anyway.
>
> Yes they do, or can. I think it's abominable, but no one asked me :).
> In code, they take it upon themselves to consider breaking lines at
> explicit hyphens.
>
> So that's the whole reason the i
