[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: what shall we do about iconv?
- To: linux-utf8@xxxxxxxxxxxx
- Subject: Re: what shall we do about iconv?
- From: Edmund GRIMLEY EVANS <edmundo@xxxxxxxx>
- Date: Tue, 2 May 2000 14:32:02 +0100
- In-reply-to: <20000328142208.I22523@daisy.vocalis.com>; from edmundo@rano.org on Tue, Mar 28, 2000 at 02:22:08PM +0100
- References: <20000328112038.D22523@daisy.vocalis.com> <20000328142208.I22523@daisy.vocalis.com>
- Reply-to: linux-utf8@xxxxxxxxxxxx
- Sender: owner-linux-utf8@xxxxxxxxxxxx
- User-agent: Mutt/1.1.11i
About a month ago I wrote here that "there seems to be no sensible way
of implementing a function that converts data while reading it from a
stream and knows at the end how may non-reversible conversions
occurred". I tried contacting the Open Group about this, and I
received some replies from Andrew Josey.
The Group thinks that the specification is clear enough: iconv()
should return -1 whenever one of the conditions EILSEQ, E2BIG, EINVAL
or EBADF occurs. Application code is already reliant on this
behaviour, so it cannot be changed. Apparently the problem I pointed
out is real, but it would have to be solved using an alternate API
instead of iconv. I don't know whether anyone is likely to take any
concrete steps towards defining such an API, but I feel happier now
that I know what the situation is.
Just thought I'd register this for the archives ...
Edmund
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/