{"id":69,"date":"2010-11-09T22:13:58","date_gmt":"2010-11-10T02:13:58","guid":{"rendered":"http:\/\/galencharlton.com\/blog\/?p=69"},"modified":"2010-11-09T22:13:58","modified_gmt":"2010-11-10T02:13:58","slug":"a-pragma-that-does-less-than-you-might-think","status":"publish","type":"post","link":"https:\/\/galencharlton.com\/blog\/2010\/11\/a-pragma-that-does-less-than-you-might-think\/","title":{"rendered":"A pragma that does less than you might think"},"content":{"rendered":"

I noticed that a patch recently submitted for Koha adds the following line to one of Koha’s Perl modules:
\n
\nuse utf8;
\n<\/code>
\nutf8<\/code> is a perfectly fine and proper Perl pragma, right? Indeed it is. The problem is that the purpose of the patch is to try to fix an issue with reading and displaying UTF-8 characters from a file. So what does use utf8;<\/code> contribute to that patch?<\/p>\n

Nothing.<\/p>\n

The only<\/em> thing that the utf8<\/a><\/code> pragma does is signal to the Perl interpreter that the Perl source code is in UTF-8. If you’re using non-ASCII characters in your source code, you’ll need the pragma. For example,
\n
\nuse utf8;
\nmy $str = \"La lluvia en Espa\u00f1a se mantiene principalmente en el llano!\";
\n<\/code>
\nor even
\n
\nuse utf8;
\nmy $str_en_ingl\u00e9s = \"The rain in Spain falls mostly on the plain!\";
\n<\/code>
\nIf what you’re actually trying to do is ensure that the script is handling UTF-8 input and output correctly, use utf8;<\/code> won’t help. This tutorial<\/a> will.<\/p>\n

Share this:<\/h3>