Date: Fri, 31 Jan 2014 03:01:16 +0400 From: Andrey Chernov <ache@freebsd.org> To: Tijl Coosemans <tijl@FreeBSD.org> Cc: =?UTF-8?B?R8OhYm9yIEvDtnZlc2TDoW4=?= <gabor@kovesdan.org>, svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, ports-committers@freebsd.org Subject: Re: svn commit: r341775 - in head: Mk/Uses converters/libiconv devel/gettext Message-ID: <52EAD9BC.4060707@freebsd.org> In-Reply-To: <20140130225350.5260dc47@kalimero.tijl.coosemans.org> References: <201401292024.s0TKOomF031237@svn.freebsd.org> <52E97640.5020703@freebsd.org> <52EA297E.6030607@kovesdan.org> <20140130132652.5d945d44@kalimero.tijl.coosemans.org> <52EA862C.30201@freebsd.org> <20140130225350.5260dc47@kalimero.tijl.coosemans.org>
index | next in thread | previous in thread | raw e-mail
On 31.01.2014 1:53, Tijl Coosemans wrote:
> //IGNORE I've never encountered yet and I don't know why anyone would
> want to use it.
It seems the code have some //IGNORE handling hooks, but I don't test is
it really work or just fake as "transliteration", see iconv.c:
handle->cv_shared->ci_discard_ilseq = strcasestr(out, "//IGNORE");
handle->cv_shared->ci_hooks = NULL;
return ((iconv_t)(void *)handle);
> And lack of //TRANSLIT isn't as bad as I initially thought it was because
> system iconv does transliteration by default. It's just that the output
> is not as good as with libiconv. The examples so far only involve ASCII
> and ISO-8859-1. I do seem to get good transliteration with ISO-8859-15.
Transliteration by converting everything to '?' (that's all I got in my
testings with several charsets, including 8859-15) means transliteration
is simple not working, it isn't 'not as good as'. Despite of false
claims in the system iconv code, see just a definition of
transliteration term.
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52EAD9BC.4060707>