Just a small refining. Tom has suggested to solve Sablotron internal
encoding transformations using charset tables (either in text or binary
form) from XML::Encoding. Nobody speaks on calling a perl code from
Sablotron. We are looking for a general and uniform way how to handle
encoding inside Sablotron (if we don't want to be fully dependent of iconv).
Petr
Steve Tinney wrote:
> Mark Bartel wrote:
>
>> I second this sentiment, that going away from iconv would seem a very large
>> step back, and I'd also like to know more about the problems of which you
>> speak.
>
>
> I don't follow fully whether the proposed change will compromise
> Sablotron's effectiveness as a standalone processor; i.e., will it make
> Sab too tightly wedded to Perl?
>
> If so, that would be a bad thing, I think. Sablotron is slick enough to
> use in a pipeline as just one more processing phase, and it should keep
> all the standalone functionality it can.
>
> Steve
--
Petr Cimprich
Ginger Alliance Ltd.
www.gingerall.com