> drawbacks (as far as the use with expat is concerned), and I came to > appreciate an alternative suggested by Rui - to let Sablotron do the > conversions itself, using the encoding tables coming from the > XML::Encoding (Perl) module. I will discuss the pros and > cons in more > detail if asked, but for the moment, I'd like to ask the following. > > 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) What would this mean for those of us who don't like (to use) Perl? Right now, the encoding (with Iconv) is done in the engine, which does not have much to do with Perl and I like it that way because I really don't do anything with Perl. I don't want to be forced to update Perl any time and then have problems with (unrelated) Perl programs, which I cannot debug. Or do you simply want to duplicate code found somewhere together with Perl? - Guenter
