WordPress Internationalization - You're probably doing it wrong (me too)

Here’s an excellent write-up on the dos and don’ts (especially the don’ts) of i18n. I think it’s well worth a read for any WordPress author. I personally have to constantly stop my self from placing variables in translation functions – and the fact that I can’t use a variable or constant as a domain (it must be a string literal) was surprising to me (but makes sense).

As Otto says in the article, “With any luck, you will have much slapping-of-the-head during this read, since I’m hoping to give you that same insight I had, when I finally “got it”.”

Hope it sheds some light on the nuances of i18n and l10n for those that are still a bit confused by it

Thank you Chris, great read!

EDIT : had no idea about the string literals and code no getting executed there, either…

digitalimpact said
had no idea about the string literals and code no getting executed there, either…

I know, right? Really frustrating not to be able to use variables even for the domain, but clearly important to understand

Is this what I sound like when I talk about Photoshop?!?

deiby said
Is this what I sound like when I talk about Photoshop?!?

LOL

sevenspark said
I know, right? Really frustrating not to be able to use variables even for the domain, but clearly important to understand

Oh well, no worries. SublimeText2 has got me covered

deiby said
Is this what I sound like when I talk about Photoshop?!?

I’m already intrigued by the stat in the first sentence. 37% is a lot! i18n is always been a mystery to me as far as exactly how it works (specifically with date/time formatting). Here’s hoping this article helps answer some of my questions – thanks for sharing!