Bug in XCUtc1-d1 XCU/TC1/D1/10

[yyyyy@xxxxxxxxx]

        Bug report from : Bruno Haible , GNU

(Note that the reply-to line automatically redirects 
to yyyyyyyyyyyyyy@xxxxxxxxxxxxx for further discussion on bug reports)

@ page 1 line 183 section XCU/TC1/D1/10 objection {XCU/TC1/D1/10/OBJ}

Problem:

The description of the iconv -c option mentions two kinds of
conversion problems:
  - byte sequences that are not valid members of the fromcode,
  - characters that have no corresponding value in tocode.

It would be inconsistent for the iconv utility if option -c
would cause the program to continue after conversion problems
of the first kind but not after conversion problems of the
second kind, and if no other iconv option would allow to
handle conversion problems of the second kind.

The rationale says "Inconsistency with the iconv() function."
It is true that the iconv() function makes a distinction between
the conversion problems of the first kind (which lead to EILSEQ)
and conversion problems of the second kind (which lead to an
implementation defined conversion). The problem is in the iconv()
function; it is this function's specification which should be
changed.

Also, please note that there is no requirement that the iconv
utility program must be implementable with the standard iconv()
function; it could also use an internal function which, in
addition to iconv(), offers independent control of the handling
of the conversion problems of the first and second kind.


Action:

Do not apply change number XCU/TC1/D1/10.