Attention Interested in functions, hooks, classes, or methods? Check out the new WordPress Code Reference!

Talk:Localizing WordPress

Watchout for javascript!! I just translated in French some strings that appear in a javascript context and using an apostrophe would prevent the javascript code from executing. I suppose that the apostrophe should be escaped in some way (possibly by using '). I chose to use "’" (unicode x2019) instead. Someone with some knowledge of gettext and javascript should add a corresponding entry for this. Chtito 14:42, 2 Jan 2006 (GMT)

I strongly disagree with the merge proposal! The Localization page is for any average non-English speaking user (and hopefully will have soon several translations), while the Translating WordPress is for those willing to contribute AND are knowledgeable enough to make a translation. The "target audience" of the two pages (articles) is totally different.

(late signature) - oops, that was me

Moshu 16:57, 19 Dec 2004 (GMT)

I agree. This page's techy content will totally scare off any newbie seeing it. I would therefore _not_ merge it. :) -User TigerDE2 23:51, 18 Dec 2004 (GMT)

I figure this page is small enough, and the Localization page is small enough, that this page can easily be inserted into the Making a Translation section on Localization. I don't think, given the placement of the section on that page, that users will be intimidated by it. But failing that, if you really think it deserves its own page, it should at least: (a) be merged with Localizing WordPress, and (b) use the correct terminology: "Localizing WordPress".

(Moshu, remember to identify yourself when you leave a comment: ~~~~.)

morganiq 08:45, 19 Dec 2004 (GMT)

I also agree with Moshu: Don't merge! Average non-English native speakers will already have to struggle through a lot of English to get their blogs running. They definitely shouldn't be led to a page about how to translate. Plus, we shouldn't be afraid of short pages. They have more chances of being read entirely anyway. (See the numerous questions in the forums that come from someone not having thoroughly read some page of doc.) -- serendipity 10:01, 19 Dec 2004 (GMT)

Okay, I must protest the removal of the {{merge}} tag. Am I the only one who thinks keeping this separate from Localizing WordPress is ridiculous?

morganiq 03:47, 22 Dec 2004 (GMT)

Alright, so we need two seperate pages:

  1. A page with all the technical details about gettext in general and WordPress i18n and l10n in particular
  2. A page with a "how to use a po or mo file to localize your copy of wordpress".

Can we agree on that and work towards that?

Carthik 07:10, 22 Dec 2004 (GMT)

Exactly, this is what I had in mind. One for international end-users on how to get a localization, and one for translators on how to create a localization. Both Localizing WordPress and Translating WordPress fall into the latter category.

morganiq 10:07, 22 Dec 2004 (GMT)

I don't know who did it - and I am not even interested to find out, since I'm getting less and less interested in contributing anything... but you guys successfully messed up the two very different stuff: now we have 2 articles with titles like WordPress Localization and Localizing WordPress, and it seems nobody cares that one is for translators (see the comment above) and the other is for international end-users. Is there anybody out there who can give me a reasonable explanation why the word translation has been removed from the title of the article that deals with TRANSLATION and replaced with another one (localization/localizing) from an already existing article just to confuse the readers?

Moshu 19:22, 31 Dec 2004 (GMT)

Oh dear, Now we have
  1. Localization and WordPress_Localization (both the same/redirects)
  2. Translating_WordPress and Localizing_WordPress (both the same/redirects)
  3. Localizing WordPress

I understand your frustration, much of which I feel, too. Maybe we should have two pages (and no more), one called "Using a Translation" and "Creating a Translation" - to remove any confusion. Codex is still in a pre-natal stage, so it is better to get these things down straight now, before it becomes well-entrenched in search engines and peoples' minds. We should be able to resolve this soon. Sorry for the confusion. Carthik 19:41, 31 Dec 2004 (GMT)

Despite the redirect muck, I still think they should be called "WordPress Localization" (for end-users) and "Localizing WordPress" (for translators). We should really do some serious redirect maintenance by making sure all pages are updated with the correct links and deleting the redirect pages. It would clear up Special:Allpages something drastic.

morganiq 01:55, 1 Jan 2005 (GMT)

@ Moshu,

I hear your frustration. It's a bit of the nature of a wiki I think to go through stuff like this. Please hang in there with us and we'll get it figured out and make it work as a team. I appreciate your work and the work of everyone else very much. Codex has improved greatly in a very short time, and it's all due to you folks!

--NuclearMoose 02:26, 1 Jan 2005 (GMT)



Can anyone please explain what "BOMs" (Byte Order Markers) are? Thanks! :)

-- User TigerDE2 20:13, 4 Mar 2005 (UTC)

Check out Wikipedia's article: Byte Order Mark. User A-giâu 06:57, 24 Mar 2005 (UTC)


morganiq 02:34, 5 Mar 2005 (UTC)

Importance of not hard-coding strings

Please, emphasize the importance of not hard-coding bits of English, especially where the lang files already specify the translation string. e.g. in passing arguments, use __('string_to_translate') not 'string_to_translate'. This will save ten-thousand users from having to dig into each template file hunting down the troublemakers and searching in the .PO file for a suitable equivalent (assuming they even know how!). Failing this, many average users will simply re-hardcode themes in their own language. That might be okay in some cases, but imagine having a theme switcher and a dozen half-hardcoded themes that have won prizes based on visual design but aren't so great when you switch languages. User A-giâu 07:04, 24 Mar 2005 (UTC)

Different title and Installation messages?

Perhaps calling the localization page something like "Install your own language" or something like that would be usefull to non-English speakers.

Another problem I am experiencing is that all of my installation messages revert to the English wereas the rest of the messages seem fine? What could be the problem? --User Renier Maritz 13:36, 7 Apr 2005 (UTC)

Renaming the page would be nice, but would break links. I will look into this, however and try to make the title clearer. Please ask a question regarding the installation messages being in English at the wp-polyglots mailing list
Carthik ‹ ℂ › Talk 14:36, 7 Apr 2005 (UTC)

Localization and feeds

Well I'm not sure this is the best place where to write this, but it has to do with Localization implementation and Wordpress so I'm writing anyway... There's a concept trouble with localized feeds in WP: it asks for get_the_time (or get_post_time in 1.5.1) when filling the pubDate element of RSS and the like. Well this leads to trouble with some newsreaders (bloglines just to say one) that cannot recognize formats different from numerical (as in 2005-05-14T12:00:05+0000) or English. I suggest modifying the RSS and Atom template in future releases. No idea what to do in the meanwhile though. I wrote more on the subject (also with the code fix) here: http://www.codewitch.org/archives/2005/05/wordpress_local.html

For issues regarding localization of WordPress, like this, please post your message on the http://codex.wordpress.org/Mailing_lists#Polyglots mailing list which handles all these issues. Thank you. Lorelle 14:08, 14 May 2005 (UTC)
I sent a mail to the wp-polyglots mailing list, for your convenience. You can follow up on it there. Also, you could open a bug report at http://mosquito.wordpress.org
Carthik ‹ ℂ › Talk 18:13, 14 May 2005 (UTC)
Thx guys, heading over there. Bru

translating with poEdit

If anybody have an English translation for this link it will be very usefull:


After 5 or 6 mounth my translation of WP (pt_BR) is done with poEdit .. its a lot of work to configure ando that link is the only one who bring-me ligth !

Other thing is the "\n\r" code : poEdit have problems with that code ... in this link they recomend replace "\r\n" to "\n" ... why not replece in all code of WP for translators ? ...and the themes have almost times ALL tags not for translation. e.g: "example text" __('example text')


--Villas 16:01, 30 Jun 2005 (UTC)