When dealing with UTF-8, you usually end up having to exhaustively track and verify the format of your text at each layer. With Perl, you will also often have to worry about whether strings are considered "utf8" or not by Perl.

When things are working properly, you shouldn't have to worry about Perl's "utf8" flag for strings. And the p5p community (the authors of Perl) tends to cater toward the "things working properly" case and so just being able to tell what format the string is really in and whether the "utf8" flag is on keeps getting trickier.

One of the easiest tools to aid such investigations, in my experience, is Devel::Peek. It will nicely dump the byte format of a string, whether the "utf8" flag is on, and, if it is on, the UTF-8 char format of the string.

So you might want to update your code to something like: 

#!/usr/bin/perl -w
use strict;
use warnings;
use Encode;
use DBI;
use feature 'unicode_strings';
use Devel::Peek     qw< Dump >;
binmode(STDOUT, ":utf8");
my $db      = "...";
my $user    = "...";
my $pw      = '...';
my $host    = "...";
my $options = {RaiseError => 1, AutoCommit => 1, mysql_enable_utf8 => 
+1};

my $dbh = DBI->connect("DBI:mysql:$db:$host", $user, "$pw", $options) 
+|| die "Could not connect to database!";
my $sql = 'select post_id, post_text from phpbb_posts where post_id = 
+24358';
my $sth = $dbh->prepare($sql);
$sth->execute() or die "Error: $DBI::errstr";
my ($id, $text) = $sth->fetchrow_array;

print "id: $id text: $text";
Dump( $text );
$text =~ s/&#9500;â&#9516;ñ/ä/g;
$text =~ s/&#9500;â&#9516;Â/ö/g;
$text =~ s/&#9500;â&#9532;©/ß/g;
$text =~ s/&#9500;â&#9516;&#9565;/ü/g;

print "\nid: $id text: $text";
Dump( $text );

[download]

You should also do some tests where you put a specific UTF-8 string into your DB and then pull it back out, using Dump() on both what you sent in and what you got back.

You may need to fiddle with more MySQL-specific options or even update DBD::mysql, or, if you are using something very old, upgrade Perl itself. You might even find that DBD::mysql misuses Perl's "utf8" flag for strings so you may end up testing taking a proper UTF-8 string but telling Perl that it is a string of bytes ("utf8" off) before sending it off to MySQL. Or find that MySQL is giving back to you such a string.

- tye        

In reply to Re: Convert special characters in UTF8 (layers) by tye
in thread Convert special characters in UTF8 by Digioso

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.