Re: iconv: document not-fixed bugs, using POSIX terminology

[Bruno Haible]

Noah Misch wrote:
> If https://pubs.opengroup.org/onlinepubs/9699919799/functions/iconv.html used
> "identical" to mean "same byte sequence", it would be requiring an ISO-8859-1 
> =>
> UTF-8 conversion to increment the iconv() return value upon converting 0xA1 to
> 0xC2 0xA1.  Most implementations don't do that.

Yes. This proves that when this part of POSIX says "identical", they mean
"equivalent".

It's nonsense if a standard attempts to redefine terms, that are defined with a
certain meaning across mathematics and computer science, in a different way.

> > --- a/modules/iconv-h
> > +++ b/modules/iconv-h
> > @@ -46,7 +46,9 @@ endif
> >  MOSTLYCLEANFILES += iconv.h iconv.h-t
> >  
> >  Include:
> > -<iconv.h>
> > +#if HAVE_ICONV_H
> > +# include <iconv.h>
> > +#endif
> 
> Doesn't this module cause the header to exist?

No. I checked the code.

Bruno