2015-03-07 22:19, Dave Rolsky via RT skrev:
Show quoted text> <URL:
https://rt.cpan.org/Ticket/Display.html?id=102552 >
>
> On Sat Mar 07 06:43:54 2015, christian@solvare.se wrote:
>> After some further digging it seems that all choices of encoding are
>> left to SOAP::Lite, so this is not your bug?
>
> I honestly have no idea. SOAP::Lite is such a big and complex code base, I've tried to avoid looking at it. I haven't noticed any problems like you just mentioned but maybe I just missed the warnings.
That I can understand, but it seems it is not a bug but a failure on my
part to read the docs... [1], namely, I need to do
$content = SOAP::Data->type(string => $content);
to make $content be encoded as a string and not base64 (as the base64
encoding is done by MIME::Base64 which only support ASCII input).
I'm sorry for the noise, but perhaps it may help someone else in the
future...
For the record, HTML::Entities may also be used:
$content = decode_entities($content);
$content = encode_entities($content, '^\n\x20-\x25\x27-\x7e');
[1]
http://cookbook.soaplite.com/#internationalization%20and%20encoding
, at 2. use UTF-8 encoding
