From 480fbcc25f97491e6577955e104566ac2f339ebc Mon Sep 17 00:00:00 2001 From: intrigeri Date: Tue, 10 May 2011 01:07:53 +0200 Subject: [PATCH] Guessed right, but practically wrong => let's clear the mess and fix things up? --- ..._does_not_support_UTF-8_if_XS_is_installed.mdwn | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/doc/bugs/yaml_setup_file_does_not_support_UTF-8_if_XS_is_installed.mdwn b/doc/bugs/yaml_setup_file_does_not_support_UTF-8_if_XS_is_installed.mdwn index c12492c6a..e9ae1883a 100644 --- a/doc/bugs/yaml_setup_file_does_not_support_UTF-8_if_XS_is_installed.mdwn +++ b/doc/bugs/yaml_setup_file_does_not_support_UTF-8_if_XS_is_installed.mdwn @@ -84,3 +84,17 @@ preferred one? >>>>>>> avoid this failure, while resulting in parsed yaml where every >>>>>>> string was likewise not decoded unicode, which is not very useful. >>>>>>> --[[Joey]] + +>>>>>>>> You guessed right about the non-decoded bytes being passed to +>>>>>>>> YAML::XS, except this is the way it shall be done. YAML::XS +>>>>>>>> POD reads: "YAML::XS only deals with streams of utf8 octets". +>>>>>>>> Feed it with non-decoded UTF-8 bytes and it gives you +>>>>>>>> properly encoded UTF-8 Perl strings in exchange. +>>>>>>>> +>>>>>>>> Once this has been made clear, since 1. this module indeed +>>>>>>>> seems to be the future of YAML in Perl, and 2. is depended on +>>>>>>>> by other popular software such as dh-make-perl (on the 2nd +>>>>>>>> degree), I suggest using it explicitly instead of the current +>>>>>>>> "try to support every single YAML Perl module and end up +>>>>>>>> conflicting with the now recommended one" nightmare. +>>>>>>>> --[[intrigeri]] -- 2.39.5