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:15:41 +0000	[thread overview]
Message-ID: <bug-29913-131-lmvxqv3GH4@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 #8 from Reuben Thomas <rrt at sc3d dot org> ---
(In reply to Bruno Haible from comment #4)
> 
> According to my interpretation of the man page (and I wrote that man page
> originally), "An invalid multibyte sequence is encountered in the input" may
> also - depending on the implementation - include the case of input that
> cannot be meaningfully converted, neither in a reversible nor in a
> nonreversible way.

Sorry, but this is an unwarranted interpretation. It's unreasonable without
extra explanation to expect the reader to recognize that "invalid" refers to
the wider context of the conversion. The fact that it says "invalid multibyte
sequence" reinforces this impression: if your interpretation were correct, then
iconv would not be expected to return EILSEQ when a single-byte sequence was
not translatable, only when a multibyte sequence is untranslatable.

I'll file a separate bug about the documentation. The glibc manual also, as far
as I can see, does not document the actual (useful!) behaviour.

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

  parent reply	other threads:[~2023-02-19 10:15 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 [this message]
2023-02-19 10:22 ` rrt at sc3d dot org
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-lmvxqv3GH4@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).