From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id C3FEA3858C52; Sun, 19 Feb 2023 22:57:00 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C3FEA3858C52 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1676847420; bh=dDSaXqiL8tNdq5gGM87o1eWCHRCyuCvE0psw5jfzakI=; h=From:To:Subject:Date:In-Reply-To:References:From; b=aRPnXjN5WpgfIeGKvm+6BPsWp2N67Ap+aAFby4herM3xWJuqxXA+NKWaacImj0Yqd xd6pAYOCZSPF4vcNADIbGSLAwYswT2IN1JdykaG6dZo91kGeKJHwP5xfHnIUe9z7m9 GqnMvAwneV+sh4itow4PbmV7wCABnOTLeueqtqmY= From: "steffen at sdaoden dot eu" To: glibc-bugs@sourceware.org Subject: [Bug libc/29913] iconv(3) is not POSIX compliant, and does not conform to linux man-pages manual Date: Sun, 19 Feb 2023 22:57:00 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: libc X-Bugzilla-Version: 2.36 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: steffen at sdaoden dot eu X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D29913 --- Comment #10 from Steffen Nurpmeso --- 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? --=20 You are receiving this mail because: You are on the CC list for the bug.=