pali

> @pali YAML::PP dump is supossed to take a data structure with Unicode characters and returns a string with Unicode characters. > load works the same the other way around....

Instead of Devel::Peek::Dump, you should look at output from: `print join ' ', map { sprintf "U+%04x", ord($_) } split //, $string` This will print sequence of ordinals stored in...

Reading output from Dump is sometimes hard as you need to know what to read: You should always look at `UTF8` part if is available and ignores other. Therefore I...

@perlpunk let me know if it is more clear for you, or you need to explain some specific part of Unicode. I will try if there are still some unclear...

> From what I see as the output from Devel::Peek::Dump and your snippet, it looks to me that both results actually return the correct string, no matter if I use...

What @2shortplanks wrote in his report is to not look at UTF8 flag. In pure perl it can be accessed by `Encode::is_utf8` or `utf8::is_utf8` functions. And on more places in...

> What would be the best description, if I take out the `upgrade`? Just say: Input must be Unicode. And output will be in Unicode. > I'm also wondering if...

In documentation is `utf8::upgrade` still mentioned, even it was removed: https://metacpan.org/pod/release/TINITA/YAML-PP-0.019/lib/YAML/PP.pm#dump_string

> So if you read from a file, you should decode it, for example with `Encode::decode_utf8($bytes)`. `Encode::decode_utf8` documentations says that this function should not be used for data exchange: https://metacpan.org/pod/Encode#decode_utf8...

Anyway, original problem about internal representation as described in this ticket seems to be already fixed. Thanks!