On Tue, Jan 30, 2001 at 10:54:39PM +0100, Tom Kaiser wrote:
[snip]
> Would anyone greatly miss any encoding which does NOT appear in the list
> below? (This is the list of encodings covered by XML::Encoding).
> Big 5, ISO-8859-2 to ISO-8859-9, x-euc-jp, x-euc-kr, x-sjis
> (Shift_JIS), windows-1250
> (plus the built-in ISO-8859-1, US_ASCII, UTF-8 and UTF-16)
>
Don't take me wrong, but that would be a large step back for sablotron.
Limiting to such a small subset of encodings, knowing possibilities of iconv
would make some sablotron users cry. At least at our place we use sablotron
just because it uses iconv for encoding conversions - we never know what
encoding we will need tomorrow (but most probably the one, supported
by iconv). I know, i know, UTF-8 and UTF-16 are encodings of the future and
someday we will not need any other encodings. But. we live at present time.
Encodings are the weakest part of almost all software on the world. Mainly
because that software either does not care about any other encodings, or it
implements "partial" solutions, which do not satisfy everybody. Having a
general encoding conversion library, which would be used by all software would
really ease up lives for both developers and users of software. And i vote
with both my hands for iconv as the library of choice.
And, could you tell more about "serious drawbacks" of iconv you have
encountered?
regards,
--
Kestutis Kupciunas (a.k.a ydum)
