From 42aebb6eb8327836b7ae50630537dd0b27a17c92 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawlVTXTWaOzAMhKML3EH8LH99Mu_TrvHhEA" Date: Sat, 11 Jan 2014 18:36:47 -0400 Subject: [PATCH] don't use utf8::valid, maybe print $file --- doc/bugs/utf8_warnings_are_meaningless.mdwn | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 doc/bugs/utf8_warnings_are_meaningless.mdwn diff --git a/doc/bugs/utf8_warnings_are_meaningless.mdwn b/doc/bugs/utf8_warnings_are_meaningless.mdwn new file mode 100644 index 000000000..7c1efa0a0 --- /dev/null +++ b/doc/bugs/utf8_warnings_are_meaningless.mdwn @@ -0,0 +1,9 @@ +Hunting down what was generating + + utf8 "\xEB" does not map to Unicode at /usr/share/perl5/IkiWiki.pm line 873, <$in> chunk 1. + +lead me to a call to `utf8::valid`, which lead to http://perldoc.perl.org/utf8.html which says this is an "INTERNAL" function: + +> Main reason for this routine is to allow Perl's testsuite to check that operations have left strings in a consistent state. You most probably want to use `utf8::is_utf8()` instead. + +Apparently the main point of the function is to emit the warning in unit tests - problem is, in the ikiwiki context, the only useful thing to warn about would be the name of the file you're trying to parse, not the name of the source code. Alternatively, since the code does continue on with the data, *not* whining about it might be an option :-) but an actionable message would be better. -- 2.44.0