Opened 21 years ago
Closed 21 years ago
#479 closed defect (bug) (fixed)
problems with non ascii chars in 1.3
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Milestone: | Priority: | normal | |
| Severity: | trivial | Version: | |
| Component: | Administration | Keywords: | |
| Focuses: | Cc: |
Description
I'm using pretty current software on my developing workstation
PHP 5.0.2 and MySQL 4.1.7 and apache 2.0.52 and was having big difficulties entering non ascii chars into post and pages. Basically the post would get cut off at the non ascii char. The thing that got me was that phpMyAdmin was working fine. After much searching and frustration. I found out that the browser was delivering the wp content in non utf-8 where as the it was delivering the phpmyadmin content in utf-8.
Change History (5)
Note: See
TracTickets for help on using
tickets.
Hi,
I just noticed that the fix doesn't work quite as expected.
MySQL expects the charset as utf8 where as in the blog it'S defined as
utf-8.
So maybe a translation hash is neccesary or something similar.
It might also be an idea to create a method set_character_set in wpdb
which hides all the nitty gritty stuff.
Let me know if you want me to finish this off.
Regards