Re: ICONV.rb and other encodings (about REXML::Encoding)

Hi,

> > > By the way, I have one proposal.
> > > REXML::Encoding accords ICONV.rb priority over other encodings,
> > > for example, EUC-JP.rb, ASCII.rb and so on.
> > >
> > > If Iconv works well, this implementation is reasonable.
> > > But, in some encodings, Iconv(libiconv) raises error and
> > > REXML stops when parsing.
> > This is strange, iconv works quite well. It only raises an error
> > when
> > the encoding given is wrong... And I think iconv is well tested...
> > Are you sure the encoding of the file is really correct?

> I should have explained the problem more precisely.
Yes, thanks, it's better this way :)
 
> At least in Japanese encodings, libiconv uses useless encoding table.
> (The word, 'useless', may be inappropriate.
> But, if we encode/decode Japanese string with libiconv,
> we sometimes meet error. )
> This problem is caused by the differnce between
> CP932 and Unicode table of Microsoft and that of libiconv.
Yes, I understand. I always use kconv to convert Japanese text, never
iconv, so I never have problems ;)

> If we can't use the patch for libiconv, for example In ISP,
> it is difficult to use REXML because of libiconv error.
> 
> In order to avoid this problem, I would like to add the option.
Yes, it would be great to be able to force REXML to use a particular
conversion tool or maybe be able to supply a callback to do the
conversion.
And if the management of the EUC-JP encoding is so buggy in iconv it
may be a good idea (but a little ugly) to use by default for this
encoding an other tool...

Cheers,
Vincent Isambart