[wp-hackers] Character Encoding Hell (and filtering /n to <p>)
andre at pixelplexus.co.za
Tue Jan 8 16:43:50 GMT 2008
Dunno if this will help. I've had reports of similar issues with
aStickyPostOrderER from a user using it on a Hebrew language blog where
category names would turn up with those evilly acusing question marks.
The user the then reported that he'd fixed it by adding:
`mysql_query(”SET NAMES ‘utf8′”);`
before every original mysql_query call.
I've not had a chance to look at it yet, perhaps someone more clued up
can enlighten us on what's the cause and best practices etc...?
Alex Andrews wrote:
> Currently programming a plugin and can't for the life of me work out
> the reason my foreign characters aren't displaying right.
> In my header I have the following <meta http-equiv="content-type"
> content="text/html; charset=UTF-8" /> . The capital e accute
> characters turn out as ? , not rendering correctly at all.
> In the MySQL database, the collation is set to utf8_unicode_ci on all
> of the table and all of the fields for the plugin. Now that is...I
> just changed these over use phpmyadmin from latin1_swedish_ci to
> utf8_unicode_ci because I thought this would mean my É characters
> would turn out correctly. This didn't solve the problem at all.
> I have numerous functions that take cells from the database and sticks
> them in bits of the plugin output. However, it never works, until I
> use Safari to change the text encoding to Western (ISO Latin 1). The
> page re-renders then it shows the characters right.
> I don't know what to do and I am considering hurling computers out of windows...
> More simple question, very much secondary: what filter other than
> wp_textualize convert new lines and various spacings into HTML, adding
> p and br tags - as is done with all posts...
> Any help would be hugely, hugely appreciated.
> Thanks a lot
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
More information about the wp-hackers