Re^2: UTF8 with YAML or JSON

[SBECK]

The 'use utf8' pragma is actually included in my module (though I omitted it from the simple code I posted here). However, I've played with it quite a bit and never got the results I wanted either.

In the code posted here, the variable $in DOES contain UTF8 characters, but when you pass it to Load (which is obviously outside the scope of anything in this script) it gets converted. For that reason, though technically correct, I don't think that adding the pragma here will have any impact. If I'm wrong though, I'm certainly open to correction. I"m definitely not a UTF8 expert.

[zwon]

never got the results I wanted either

So do you actually want \x{c4}\x{83} as YAML::Syck returns to you, or you want \x{103}?

[SBECK]

I want the characters included in the data structure to be EXACTLY what I included in the text that got parsed. So, if I send in a string which contains a scalar of UTF8 values, then I should see UTF8 values in the data structure. YAML::Syck does this. YAML/YAML::XS/JSON/JSON::XS all take the scalars with UTF8 values in them and produce data structures containin perl encodings.

[zwon]

I should see UTF8 values ... YAML::Syck does this

I don't see this from your example. YAML::Syck returns you two latin1 characters instead of a single \x{103} that the file contains, which is exactly the opposite to what you are saying you want. YAML::XS expects UTF-8 octets on input, and it checks that it is correct UTF-8, and it returns you UTF-8 characters. I have impression that you don't realise what you are getting from the modules, maybe you should use Dump from the Devel::Peek to inspect values instead of Dumper, also if you add

use open ":utf8";
use open ":std";

to your script, it will be clear to you, that YAML::Syck doesn't return ă, but ă.