UPDATE: I wrote my own multilingual plugin, which works way better than Polyglot. Check it out here.
After spending days on installing all kinds of pluginsand “hacking” around in the code of several plugins, I think I am finally finished. Here is the list of plugins I use:
- Akismet 2.0 – A plugin for fighting comment spam, which is working very nicely.
- Google XML Sitemaps Generator 3.0b6 – A plugin for generating a Sitemap for Search Engines.
- Polyglot 2.0 – A plugin for making WordPress multilingual.
When I first installed Polyglot on WordPress 2.0.x, some little things didn’t work. WordPress didn’t apply filters for things they should have and Polyglot didn’t add filters for those functions, so some things didn’t get translated. After updating to 2.1, I have to say that every bug I fixed a week ago (why didn’t I move to WordPress a week later?), was already fixed. But the bug fixes for Polyglot were still needed. The main reason for me hacking around in Polyglot were the Date functions. It was not using strftime, which caused me not to be able to translate full string names of week days, month or years. After getting this to work, I installed the “Google XML Sitemaps” plugin, which generates a sitemap of all my wordpress pages. But sadly, it didn’t support Polyglot, so I had to hack around in it too, although this was pretty easy compared to the Polyglot “hacking”. So if anyone else is using Polyglot and Google XML Sitemaps and want them to work together, here are my files zipped. Read more to see a list of changes made by me.
- Added support for Polyglot in Google XML Sitemaps
- Fixed Date String Output in Polyglot
For this I added 2 new arrays for strftime formats:
plus 2 functions for fixed output:
polyglot_translated_date() and polyglot_translated_time()
- Added single_cat_title filter for Polyglot
- Fixed problem with search URI and lang-pref settings
- Several bug fixes in Polyglot