On Tue, Sep 04, 2007 at 10:16:59AM +0300, Nikolay Bachiyski wrote: > > Does anybody these days really need encoding different than utf-8? If > one really does, converting the po file and recompiling the mo seems > the best solution.
The character set option is one of the best ones in WordPress. Don't give anyone any ideas about removing it, or something! :) My blog is using iso-8859-1, and it is also embedding WordPress, which is rather unusual, it seems. But I'm so glad that I can do both. My original blog data was in iso-8859-1. However, there are other data sources used on my site as well, such as ID3 tag data (in mp3 files) and Exif data (in jpg files), which is kept in iso-8859-1. Also, the file names in the file system use iso-8859-1 encoding. That's a lot of data to convert, with much worse support for multibyte character encodings as opposed to single byte characters. (A single byte with all its 8 bits in actual use is already quite well supported these days.) Without being able to embed WordPress, maintaining a uniform look through the site would cause much more work. Making everyhing into WordPress plugins might not even be possible, as some parts of the site are written in Perl rather than PHP. Best regards, + Kimmo -- <A HREF="http://kimmo.suominen.com/";>Kimmo Suominen</A> _______________________________________________ wp-polyglots mailing list [email protected] http://lists.automattic.com/mailman/listinfo/wp-polyglots
