On 2012-07-04 10:18, Harald Oehlmann wrote:
Am 04.07.2012 10:12, schrieb Georgios Petasis:
Στις 4/7/2012 11:02, ο/η Massimo Manghi έγραψε:
It doesn't matter, it seems that the following works:
set xmldata [upload data xml]
set xmldata [encoding convertfrom utf-8 $xmldata]
The problem was that I failed to change the stdout encoding to utf-8
in
my rivet string.
Adding "fconfigure stdout -encoding utf-8" ate the very top of my
script, solved all problems.
(I return everything in utf-8 and set the utf-8 encoding in all
return
types).
may this be considered as a bug ?
Or should we have a magic or command to set the encoding of stdin to
the
delivered encoding ?
it's definitely a missing feature. It would be nice and probably
correct to have a command that returns the encoding value when present
in the multipart message. Having barely the channel set to the correct
encoding leaves you without a clue on what enconding is actually used to
represent the data, unless we state that everything is internally
represented in rivet as,say, UTF-8 and implicitly converted to it.
-- Massimo
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
