diff options
author | Joey Hess <joey@kitenet.net> | 2011-04-15 14:03:10 -0400 |
---|---|---|
committer | Joey Hess <joey@kitenet.net> | 2011-04-15 14:03:10 -0400 |
commit | 1da44cfe54343d1f5fa3b79ea12ea013c90ce4b8 (patch) | |
tree | 09f3a4470c61f9a4bd7ee47d9ee80fa255badf59 | |
parent | 5c863d3eb574e82904b8e3f11f781bb7344bb923 (diff) | |
download | ikiwiki-1da44cfe54343d1f5fa3b79ea12ea013c90ce4b8.tar ikiwiki-1da44cfe54343d1f5fa3b79ea12ea013c90ce4b8.tar.gz |
response
-rw-r--r-- | doc/bugs/yaml_setup_file_does_not_support_UTF-8_if_XS_is_installed.mdwn | 6 |
1 files changed, 6 insertions, 0 deletions
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 a0dad177b..da8f494ff 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 @@ -32,3 +32,9 @@ preferred one? > Upgrading YAML::XS ([[!debpkg libyaml-libyaml-perl]]) to current sid > version (0.34-1) fixes this bug for me. --[[intrigeri]] + +>> libyaml-syck-perl's description mentions that the module is now +>> deprecated. (I had to do some ugly workaround to make unicode work with +>> Syck earlier.) So it appears the new YAML::Xs is the +>> way to go longterm, and presumably YAML::Any will start depending on it +>> in due course? --[[Joey]] |