UTF-8 Support

∟Reference Citations in 2006

∟UTF-8 Support

'Managing Non-ASCII Character Strings with MySQL Servers' tutorial book was cited in a Plogger bug report in 2006.

The Managing Non-ASCII Character Strings with MySQL Servers tutorial book was cited in a Plogger bug report in 2006.

Subject: [Bugs] [plogger] #122: UTF-8 support
Date: Mar 15, 2006
Author: Victor
Source: http://lists.plogger.org/pipermail/bugs/2006-March/000390.html

I've realized that the UTF8 character set isn't really support in
Plogger. I'm talking about 2.1 version, but seems that version 3 is
affected too.

Although Plogger ''_install.php'' script creates the MySQL tables with
the UTF-8 character set properly, the information is not really stored
in UTF-8 as far as I know. I realized that because the RSS feed
generated with special characters (''??' and so on) didn't work
properly, and get complaints about the use of invalid characters
(''&ntilde;'' and so on). Looking in the database, I see that the
information itself isn't been stored in really UTF-8.

In my Plogger version I fixed this problem doing the next things:

'''1)''' The Admin backend XHTML is not in UTF-8. For that I added the
line

 <meta http-equiv="Content-Type" content="txt/html; charset=utf-8"/>

in the XHTML generated, and to make sure:

 header("Content-Type: text/html; charset=utf-8");

With this we're sure the XHTML generated is in UTF-8, but we can't
assure the information from the forms is been sent to the MySQL server
in UTF-8. See step # 2

'''2)''' To make sure about the last point mentioned I added the next
line:

   $rs = run_query("SET NAMES 'utf8'");

(I'm not going to explain here this command, don't worry ;), but you
can see more info here:
[https://www.herongyang.com/php/non_ascii_mysql_2.html])

So, Ok, we're storing properly the utf-8 information in the Database,
but... why the hell my XML isn't valid yet? Let's look at step # 3
...