Comments on: Internationalization: You’re probably doing it wrong

By: php-gettext: Múltiplos idiomas em um sistema PHP - Devin

php-gettext: Múltiplos idiomas em um sistema PHP - Devin — Wed, 22 May 2013 11:11:27 +0000

[…] Internationalization: You’re probably doing it wrong […]

By: Vane

Vane — Tue, 23 Apr 2013 14:39:00 +0000

Very nicely structured article, I enjoyed reading it a lot! From my experience, I would like to recommend some tools that would help the internalization process a lot. This: https://poeditor.com/ is a very nice localization online software that offers a few nice features such as setting a reference language for translations or using automatic translation from google or bing. For wordpress it has an extra plugin which you can download from the wordpress plugin list, which allows you to work directly from your blog.

By: WordPress Theme Development Best Practices - Fränk Klein

WordPress Theme Development Best Practices - Fränk Klein — Tue, 26 Mar 2013 13:12:38 +0000

[...] addition to this, Otto has written two very in-depth articles about the pitfalls of i18n as well as an overview of the lesser known translation [...]

By: Otto

Otto — Sun, 24 Mar 2013 12:36:15 +0000

Okay, you’re correct. Those elements are indeed read by core and used for the translation of the header parts of the plugin/theme. That behavior was added in 3.4, and so I’ve never really seen or used it.

However, they are not required elements by any means and translation of the rest of the plugin works perfectly fine without them. The only need for them is for translating those header elements. If you do not desire to translate those, then these two extra headers are wholly unnecessary.

By: krembo99

krembo99 — Sun, 24 Mar 2013 03:28:45 +0000

As much as I recognize you as a high authority on all matters “wordpress” (and i really do..) , I found this otherwise (maybe wrongly).
In my experiments , core does read it , and in fact , in has some influence on the $domains global in i10n, or at least on the ORDER in which the plugin / theme domain is being read.
Also, without those – the DESCRIPTION of the plugin, the name , or any other thing in the DocBlocks , can not be translated (by core).
I will be happy to send you some code to verify this .

By: Otto

Otto — Thu, 21 Mar 2013 13:01:30 +0000

I see these a fair amount, but they’re not standard by any means. Nothing in the core reads or uses these fields. Nothing on the WordPress.org website reads or uses them either. It doesn’t matter whether you add them or not.

By: krembo99

krembo99 — Thu, 21 Mar 2013 06:21:22 +0000

While explaining how to do it right, maybe you should add that it would be much beneficial if people add the two extra rows to the docblocks in a plugin or theme :
* Text Domain: my-domain
* Domain Path: /lang

By: Doug

Doug — Fri, 16 Nov 2012 17:53:51 +0000

Thanks for the quick reply. I’ll look into rephrase or as you suggest may have to break the law to accomodate the client preferred copy.

By: anastis

anastis — Fri, 16 Nov 2012 17:21:21 +0000

Thanks for your response.

Indeed, “Post” without _x() isn’t a good example, but you got my point.

I never thought of what would happen if the dependency of the translations changed, so yeah, your answer makes sense and covers me completely.

Cheers!

By: Otto

Otto — Fri, 16 Nov 2012 17:06:10 +0000

1) A theme/plugin should only contain its own strings, and one domain. Sharing domains across multiple-things leads to confusion. What happens when there is a conflict? You’ll run into versioning issues. Strings change over time. Things like that.

3) No, because of the same issue. What happens when WordPress changes strings? Tying your plugin/theme’s translations to the core translations isn’t the best idea. Yes, it’s duplicated work, but it’s not all that bad. Better to keep them separate because different things can be different sometimes.

Also, your example of “Post” isn’t a good one. What does “Post” mean? It’s uncertain whether you’re using it as a noun or a verb, even. Confusion like that can come from using the wrong core string as well.