public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rrt at sc3d dot org" <sourceware-bugzilla@sourceware.org>
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 10:22:08 +0000	[thread overview]
Message-ID: <bug-29913-131-y0X6fqYCpS@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29913-131@http.sourceware.org/bugzilla/>

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

--- Comment #9 from Reuben Thomas <rrt at sc3d dot org> ---
(In reply to Bruno Haible from comment #5)
> 
> If you need code that works with multiple iconv implementations, take a look
> at gnulib/lib/unicodeio.c lines 137..154 or gnulib/lib/striconveh.c lines
> 950..962. You see that the problem is that replacing unknown or
> inconvertible inputs with '?' or '*' or NUL is
> - just not yielding practically useful behaviour (especially because the
> caller then cannot transform a buffer all at once, a purpose for which the
> iconv function was initially designed),
> - requiring platform dependent recognition heuristics.

For those who need to work with multiple implementations, it looks like this
code could usefully be exposed in its own gnulib API.

Since most of the problems I've had with Recode since taking it over have
arisen from iconv, and coping with different implementations just makes it
worse, I think I will retreat to using GNU libiconv (which Recode used to use)
where at least I only have one implementation to deal with.

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

  parent reply	other threads:[~2023-02-19 10:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-16 23:03 [Bug libc/29913] New: " steffen at sdaoden dot eu
2023-02-18 20:48 ` [Bug libc/29913] " rrt at sc3d dot org
2023-02-18 21:20 ` rrt at sc3d dot org
2023-02-18 22:43 ` steffen at sdaoden dot eu
2023-02-19  0:40 ` bruno at clisp dot org
2023-02-19  0:51 ` bruno at clisp dot org
2023-02-19  1:58 ` steffen at sdaoden dot eu
2023-02-19 10:06 ` rrt at sc3d dot org
2023-02-19 10:15 ` rrt at sc3d dot org
2023-02-19 10:22 ` rrt at sc3d dot org [this message]
2023-02-19 22:57 ` steffen at sdaoden dot eu
2023-02-19 23:02 ` steffen at sdaoden dot eu
2023-02-20 20:09 ` steffen at sdaoden dot eu
2023-02-20 20:54 ` steffen at sdaoden dot eu
2023-02-20 21:52 ` steffen at sdaoden dot eu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-29913-131-y0X6fqYCpS@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).