[Bug libc/29913] iconv(3) is not POSIX compliant, and does not conform to linux man-pages manual

["steffen at sdaoden dot eu" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=29913

--- Comment #10 from Steffen Nurpmeso <steffen at sdaoden dot eu> ---
I mean the GNU approach definetely has merits.
If it only would not be automatic, but require //OUCNVERR
or some other hypothetic explicit configuration.

As it stands GNU stands out with its behaviour, and i as
a programmer do not know how to differentiate in between an input
ILSEQ (dramatical!) or and output ILSEQ (email use case might try
different character set).  I can maybe a bit -- if i know for sure
that the iconv i use is the GNU one, which might not be true in
practice (though i know of no other dynamic library that can
replace it, only of libc-built-in and GNU iconv lib choices).
If only it were a dedicated errno value.

For me the need to go //TRANSLIT is a well hm painful GNU-specific
need and way, and it shall be noted it is "transliteration":
something entirely different than "an implementation-defined
conversion on this character" that in reality is either * or ?.
It could do whatever, say turning a hypothetic calligraphic "tiger
protects the house" with a download link for a book of Dostojewski
or something.

How can i test this??
How can i as a programmer write a test that tests my program works
correctly regarding iconv if i have to use //TRANSLIT that may
change behind the lines and "improve" the transliteration because
someone spend time on some character set and found a better one?
I currently use "U+1FA78/f0 9f a9 b9/;DROP OF BLOOD" which right
now works everywhere, but //TRANSLIT may turn it to an embedded
picture of Bela Lugosi?  Nosferatu?

-- 
You are receiving this mail because:
You are on the CC list for the bug.