in reply to Re^2: WriteExcel unicode question
in thread WriteExcel unicode question

$cellvalue2=Encode::decode ('UCS-2BE',$cellvalue2)

Not sure whether it will solve your problem, but I would have tried 'UCS-2LE'  (I have yet to see a big-endian Windows...)

Replies are listed 'Best First'.
Re^4: WriteExcel unicode question
by demis (Novice) on Oct 15, 2009 at 10:49 UTC
    almut, it does not. Same chinese-looking characters as with BE

      To further debug the issue, I would Dump $cellvalue2 using Devel::Peek, in order to see what the encoding actually looks like at the byte-level (see the PV output). Then compare that result against the individual encodings that would make sense in your context, taking into account that some mis-decoding or double encoding may already have happened at some other place in the processing chain...