From 6c684723a5736e60480af2ba488c36512414bdf4 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawnUf7CP8-uZK-EhzDR22LIZlcyI2Q0eLnw" Date: Tue, 10 May 2011 08:40:01 -0400 Subject: [PATCH 1/2] --- doc/sandbox.mdwn | 3 +++ 1 file changed, 3 insertions(+) diff --git a/doc/sandbox.mdwn b/doc/sandbox.mdwn index a5d686908..9ade25292 100644 --- a/doc/sandbox.mdwn +++ b/doc/sandbox.mdwn @@ -93,3 +93,6 @@ This is super cool Joey! Testing a change! Testing multilanguage support via utf-8: Ελληνικά. 日本語。 + +Testing Haiku +[[!haiku hint="argument"]] From 480fbcc25f97491e6577955e104566ac2f339ebc Mon Sep 17 00:00:00 2001 From: intrigeri Date: Tue, 10 May 2011 01:07:53 +0200 Subject: [PATCH 2/2] 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]]