svn commit: r341775 - in head: Mk/Uses converters/libiconv devel/gettext

Gábor Kövesdán gabor at kovesdan.org
Tue Feb 4 14:06:18 UTC 2014


On 2014.02.03. 22:25, Andrey Chernov wrote:
> On 31.01.2014 12:53, Tijl Coosemans wrote:
>>> Just an example:
>>> # perl -e 'print "\xc1\n";' | iconv -f "ISO8859-15" -t "US-ASCII//TRANSLIT"
>>> ?
>>> iconv: warning: invalid characters: 1
>>> (what ever this warning does here?)
>>>
>>> # perl -e 'print "\xc1\n";' | /usr/local/bin/iconv -f "ISO8859-15" -t "US-ASCII//TRANSLIT"
>>> 'A
> For BSD iconv internal name of "US-ASCII" is "ISO646-US", as
> iconv_canonicalize(3) shows. And for that name only one conversion table
> exists, from US-ASCII to UCS, which is void (does nothing):
> /usr/src/share/i18n/csmapper/ISO646/ISO646-US%UCS.646.src
> What we need to make to US-ASCII translation work is
> MISC/UCS%ISO646-US.src table, which can be made from f.e.
> ISO-8859/UCS%ISO-8859-15.src table. BTW, I see
> ISO-8859/UCS%ISO-8859-1.src transliteration is missing too.
> It will be better when somebody who knowns Citrus internals will look
> there. Who "owns" our Citrus code now and in contact with Citrus
> developers? We need some coordination here.
I ported Citrus iconv to FreeBSD but unfortunately nowadays I lack time 
to work on it. Peter imported the code to our tree. There are no active 
Citrus developers so no contact person either...

Gabor



More information about the freebsd-i18n mailing list