[wp-trac] Re: [WordPress Trac] #3633: Error in non-UTF8 encoding
(for example WINDOWS-1251)
WordPress Trac
wp-trac at lists.automattic.com
Mon Jan 22 21:11:57 GMT 2007
#3633: Error in non-UTF8 encoding (for example WINDOWS-1251)
-------------------------------------+--------------------------------------
Reporter: maxsite | Owner: anonymous
Type: defect | Status: new
Priority: normal | Milestone: 2.2
Component: Administration | Version: 2.1
Severity: normal | Resolution:
Keywords: UTF8, charset, encoding |
-------------------------------------+--------------------------------------
Comment (by nbachiyski):
Yeap, AJAX is the problem. It seems that different encodings just couldn't
easily live in that cruel AJAX world ;)
I am from Bulgaria (another windows-1251 country) and recently also had
the same problem with an application of mine. The solution was to decode
the incoming data - if it was valid UTF-8 to cp1251. However I do not
think in WordPress there is place for such dirty hacks :-)
Maybe migration to UTF-8 will be the best choice you can go for.
--
Ticket URL: <http://trac.wordpress.org/ticket/3633#comment:4>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list