Beefy Boxes and Bandwidth Generously Provided by pair Networks
Welcome to the Monastery

Re^3: UTF8 with YAML or JSON

by zwon (Abbot)
on Jun 29, 2012 at 17:59 UTC ( #979162=note: print w/replies, xml ) Need Help??

in reply to Re^2: UTF8 with YAML or JSON
in thread UTF8 with YAML or JSON

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}?

Replies are listed 'Best First'.
Re^4: UTF8 with YAML or JSON
by SBECK (Hermit) on Jun 29, 2012 at 18:06 UTC

    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.

      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 ă.

        Unfortunately, what you're seeing in my post isn't exactly what I'm seeing in real life. When using the <code> markup in my post, it changed the UTF8 character, and I couldn't figure out how to make the markup show exactly what I wanted it to show (i.e. what I'm seeing in the script and debugger). That has unfortunately served to confuse the question.

        Regardless of what's showing up in my post, my script contains actual UTF8 characters, and when I use the debugger to show exactly what is in the data structure after the Load function, YAML::Syck shows the exact same UTF8 characters that are contained in the __DATA__ section. All others modules produce strings containing perl encodings.

        Hope that clarifies things a bit.

        EDIT: I need to retract my above statement. I'm still trying to understand perl and unicode (which I definitely don't have a great understanding of). Although the posting markup issue is there, the comments you make are correct, and I was wrongly interpreting things. What I've been calling the "correct" behavior does indeed involve a string of length two (instead of one), so I've got to look into this in more detail to determine exactly what it is that I'm seeing and what I WANT to see.

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://979162]
[harishnv]: hey

How do I use this? | Other CB clients
Other Users?
Others cooling their heels in the Monastery: (6)
As of 2018-02-18 11:00 GMT
Find Nodes?
    Voting Booth?
    When it is dark outside I am happiest to see ...

    Results (253 votes). Check out past polls.