I demand every theme to be i18n ready, seriously. While writing the sourcecode it's very easy to internationalize the theme. Putting i18n in afterwards is a huge timefactor - I did it once for Neil Mertons Web2.0* theme and it took me a whole day to test and bugfix (too bad Neil disappeared from the internet - and so did his theme).
i18n is as easy as making widget-ready sidebars. Too bad most theme authors do not care about widgets and hardcode everything inside their sidebar...
Ryan
· 11 months ago
Thanks Andrew.
I've been wondering how to do this for a while for both themes and plugins.
Stefano, www.wordpressmania.it
· 11 months ago
Totally agree! For all non-english bloggers the fact that a theme is i18n ready is definitively a needed feature! At least the premium themes need to be i18n, but very few are!
Even all the free themes listed at wordpress.org sholud be i18n ready, as WordPress is...
Simon
· 11 months ago
A big Thanks, Gracias & Danke, Andrew! Will definitely use it.
SE7EN (Nice from Thailand)
· 11 months ago
My blog is in Thai and English but I prefer my WordPress installation and theme in English
All Comments
While writing the sourcecode it's very easy to internationalize the theme. Putting i18n in afterwards is a huge timefactor - I did it once for Neil Mertons Web2.0* theme and it took me a whole day to test and bugfix (too bad Neil disappeared from the internet - and so did his theme).
i18n is as easy as making widget-ready sidebars. Too bad most theme authors do not care about widgets and hardcode everything inside their sidebar...
I've been wondering how to do this for a while for both themes and plugins.
For all non-english bloggers the fact that a theme is i18n ready is definitively a needed feature!
At least the premium themes need to be i18n, but very few are!
Even all the free themes listed at wordpress.org sholud be i18n ready, as WordPress is...