[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Initial test code for \U

From: John Kearney
Subject: Re: Initial test code for \U
Date: Sun, 26 Feb 2012 18:51:32 +0100
User-agent: Mozilla/5.0 (X11; Linux i686; rv:10.0) Gecko/20120129 Thunderbird/10.0

On 02/22/2012 08:59 PM, Eric Blake wrote:
> On 02/22/2012 12:55 PM, Chet Ramey wrote:
>> On 2/21/12 5:07 PM, John Kearney wrote:
>>> Initial code for testing \u functionality.
>> Thanks; this is really good work.  In the limited testing I've
>> done, ja_JP.SHIFT_JIS is rare and C.UTF-8 doesn't exist
>> anywhere.
> C.UTF-8 exists on Cygwin.  But you are correct that...
>> en_US.UTF-8 seems to perform acceptably for the latter.
Also on Ubuntu. I only really started using it because it is
consistent with C

Actually this was the reason I made the comment about not being able
to detect setlocale error in bash. wanted to use a fallback list of
the locale synonyms.

The primary problem with this test is you need the locales installed.

thoretical plan
1. compile list of destination code sets.
3. some method to auto install codesets.
3. Get Unicode mappings for said code sets.
2. use iconv to generate bash test tables
4. start crying at all the error messages ;(

now locale -m gives charsets.
Any ideas about finding unicode mappings for said charsets?
I've been looking through the iconv code but all seems a bit laborious.
What charsets would make sense to test?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]