Re: Nonstandard implementation problems in iconvdata

[Andreas Jaeger]

>>>>> Ben Hochstedler writes:

 > The implementation of iconv has two major differences from what seems
 > to be the standard:

 > 1. When converting from encoding A to encoding B, where there are
 >    characters in A not in B, it stops if one of those nonconvertable
 >    characters is encountered and returns the error for when there
 >    are characters input that aren't in A.

 >    Here is the correct behavior defined by the iconv.3 manpage on
 >    Solaris:
The correct behaviour is not defined by Solaris but by Standards like
Unix98 which has:

  If a sequence of input bytes does not form a valid character in the
  specified codeset, conversion stops after the previous successfully
  converted character.  If the input buffer ends with an incomplete
  character or shift sequence, conversion stops after the previous
  successfully converted bytes.

Andreas
-- 
 Andreas Jaeger
  SuSE Labs address@hidden
   private address@hidden
    http://www.suse.de/~aj