From a8d7cdc841684615471dbbe0fbb5769950d0fd3e Mon Sep 17 00:00:00 2001 From: Michael Orlitzky Date: Tue, 7 Jul 2026 10:35:38 -0400 Subject: [PATCH] README.rst: add bug references where they are available --- README.rst | 24 +++++++++++++++++------- 1 file changed, 17 insertions(+), 7 deletions(-) diff --git a/README.rst b/README.rst index 91bfd62..81d6685 100644 --- a/README.rst +++ b/README.rst @@ -28,24 +28,34 @@ glibc ----- * iconv_open() accepts any indicator suffix, such as ``//INVALID``. -* iconv() returns EILSEQ when it ignores invalid input. + (This becomes illegal in the case of ``//NON_IDENTICAL_DISCARD``, + which is specified to do something.) Non-conformance by implementation ================================ -Perhaps illegal, if my reading of POSIX 2024 is correct. But keep in -mind that most of these implementations predate (this part of) POSIX. +Probably illegal, if my reading of POSIX 2024 is correct. glibc ----- +* iconv() with ``//IGNORE`` returns EILSEQ when it hits invalid input, + but POSIX says "This shall not be treated as an error." This is is + closely related to `glibc bug 13541 + `_. + * With no indicator suffixes, iconv() returns EILSEQ for valid but - untranslatable sequences. This is documented in both glibc's - documentation (charset.texi) and in the Linux man-pages iconv(3) - page. + untranslatable sequences. This is `glibc bug 14008 + `_ and `glibc + bug 31641 + `_. It is + however documented in both glibc's documentation (charset.texi) and + in the Linux man-pages iconv(3) page. * With ``//IGNORE``, untranslatable sequences still cause EILSEQ. This - contradicts glibc's own documentation. + contradicts glibc's own documentation, and is closely related to + `glibc bug 13541 + `_. * iconv_open() accepts ``//NON_IDENTICAL_DISCARD`` but iconv() does not implement it. -- 2.53.0