Document Number: AUSTIN/116

Title: XCU/TC1/D1 Aardvark Change Request Report 

Revision Date: 2002-06-26

Source: Andrew Josey, Chair

Action: for review

This report contains the draft dispositions of the aardvark comments
submitted against the XCU/TC1/D1  text.

Aardvark Summary Table
______________________
ERN 1 Accept as marked 

 _____________________________________________________________________________
 OBJECTION                                        Enhancement Request Number 1
 bruno@clisp.org                     Bug in XCUtc1-d1 XCU/TC1/D1/10 (rdvk#  1)
 {XCU/TC1/D1/10/OBJ}                     Mon, 27 May 2002 14:30:24 +0100 (BST)
 _____________________________________________________________________________
 Accept_____    Accept as marked below_X___     Duplicate_____     Reject_____
 Rationale for rejected or partial changes:

 A revised ERN is being submitted for TC1 D2 based on the June 20
 teleconference, which will replace this item.

 _____________________________________________________________________________
 Page: 1  Line: 183  Section: XCU/TC1/D1/10


 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.

 [Ed recommendation: Accept as marked, a revision ERN
 is being submitted for D2 based on the June 20 teleconference,
 which will replace this item]