post-page

Localizing a WordPress Plugin Using poEdit

34
responses
heading
heading
heading
34
Responses

 

Comments

  1. gidibao (10 comments.) says:

    Ronald – great post!!!

    Thank you

  2. GaMerZ (24 comments.) says:

    I got a tutorial up quite some time also.
    http://forums.lesterchan.net/i.....108.0.html

  3. Tim (1 comments.) says:

    Nice tutorial. As you already said, the same can be done with wordress themes. I have a tutorial for themes here: Localizing WordPress Themes

  4. Ronald Huereca (39 comments.) says:

    gidibao,
    Thank you. Glad you found it useful.

    GaMerZ, Tim,
    I added you onto the end of the post as related reading. Thanks for pointing those links out. Most of what I could find regarding localization was unanswered support questions.

  5. John (2 comments.) says:

    Nice work Ronald! You might also be interested in Localizing a WordPress Theme or Plugin and Translating WordPress into another language.

  6. Can Erten (1 comments.) says:

    or you can use PO file integrator, if you have some localisation problems with your server.
    What it does it generates the localised code in the source code

  7. Ronald Huereca (39 comments.) says:

    Thanks for the links John. Hopefully there is now enough information here to answer most questions regarding localizing WordPress plugins and themes.

  8. Jamie Fehr (1 comments.) says:

    It’s worth noting that the .mo for a THEME translation won’t have the text domain as part of the file name. You should just save it as ar.mo for example.

  9. Gregg says:

    NEED help getting multiple languages working. Will PAY! urgent timing.

  10. Martti says:

    Hey Ronald,

    this is by far the best guide to localize WordPress and to use poEdit. Thank you!

    Still, I am having trouble localizing Carrington Mobile. That is: a plugin and a theme. I managed to translate Carrington Mobile theme and plugin. At least almost. There are still some words here and there which didn’t appear on the poEdit.

    For example:
    about, more ?, Return to the Mobile Edition, Categories: Uncategorized
    are still untranslated. Any suggestions?

    It appears there are two project names: “carrington” and “carrington-mobile”. So, I should make two sets of .po and .mo files. Am I missing something? Where should I put the different files or should I somehow merge them? And how is this possible?

    http://wordpress.org/extend/pl.....e-edition/
    http://wordpress.org/extend/th.....ton-mobile

  11. rudolf (1 comments.) says:

    Hi, any chance somebody still looks into this post and these comments??
    I have one silly question regarding the PATHS
    If i have PoEdit in the usual Programs folder of Windows, and start it and get to the settings where i have to put in the paths it doesn’t just work with a dot as path, seems anyway impossible if i have the actual plugin lets say in
    C:\MyFiles\DukaPress2.2\translate
    so, what exactly do i have to do for PoEdit to go and fetch everything,if i use the above path as the default path i at least don’t get an error message anymore, but it doesn’t fetch anything either.
    Also, the support of PoEdit itself said that i could use multiple paths if i have plugin files in more than 1 directory / folder, but i have no clue where or how to set those in either, tried to put them all into default path, seperated by comma like keywords in an html meta – did not work, i am kind of completely lost on how this program fetches the stuff out of all those PHP files (that are all setup for transaltions).

    Any help??

    P.S. this
    Notify me of followup comments via e-mail
    where did you get this from, part of the Theme you are using or a special plugin for comments??? (love it!)

  12. Steve says:

    Hello, I want to handle 3 languages in my wordpress instalation, in your tutorial you only show for 2 languages, how can I connect the translations of the 3 languages, for example english, spanish and italian, how I know what is the translation from english to spanish, spanish to italian and so on !!

    I’ll appreciate your help, thanks.

    • Rudolf (1 comments.) says:

      It’s been a while since i did my own localizations, but if i understand you right you probably did not understand how PoEdit works.
      You only need to know how the translation from one language into one other works!!
      Let’s say you have an original in English.
      You make the translation first into Spanish and save the spanish files as
      es_ES.mo (or es_ES.po) – done.
      Than you take once again the original English and set up PoEdit (as described above) for the next language (that is the important difference), so that you then have it to translate everything into your next language of choice, say Italian and in the end you save as it_IT.mo or it_IT.po
      and so on, sorry simplified explanation, there are a few twists and tricks along the way i can not recall anymore, but that is the essential


Tweetbacks

  1. elarequi (Eduardo Larequi) (2 comments.) says:

    @onio72 y en http://tinyurl.com/cfqfbw (vale también para los temas).


Trackbacks/Pingbacks

  1. […] Weblog Tools Collection » Blog Archive » Localizing a WordPress Plugin Using poEdit (tags: wordpress plugins tutorial localizing) […]

  2. […] Localizing a WordPress Plugin Using poEdit – ??? ???? ???? ????? ????? ?????? ????????. […]

  3. […] Localizing a WordPress Plugin Using poEdit (tags: wordpress) […]

  4. […] ????? ??????????? ????? ???????? – Localizing a WordPress Plugin Using poEdit […]

  5. […] ????? Localizing a WordPress Plugin Using poEdit?????????????? […]

  6. […] is a gettext editor. It is available for all OSs. See this tutorial for a […]

  7. […] Hoe je plugins kan vertalen met poEdit. […]

  8. […] Localizing a WordPress Plugin Using poEdit […]

  9. […] ????? Localizing a WordPress Plugin Using poEdit?????????????? […]

  10. […] Localizing a WordPress Plugin Using poEdit Denne artikel beskriver hvordan man kan oversætte plugins ved hjælp af værktøjet poEdit. Læs artiklen og kom i gang med at lave danske oversættelser af dine yndlings plugins. […]

  11. […] Here is a list of things to keep in mind when you’re localizing your plugin, compiled from what I’ve observed plugin authors not often doing. (See John Godley’s blog entry for a thorough discussion of localizing details and Ronald Huereca’s good guide to creating the .po files WordPress uses for translating). […]

  12. […] you want to help translate and internationalize WordPress Plugins, read the article by Weblog Tools Collection on “Localizing a WordPress Plugin Using poEdit”, with tips for helping WordPress Plugin authors to make their WordPress Plugin international, […]

  13. […] If you would like to read this tutorial in english, please visit Weblogtoolscollection. […]

  14. […] the help of Ronald Huereca, I learn how to use poEdit to localize wordpress component. What a great tool in translating, as easy as anyone knows how to […]

  15. […] poedit – it’s cross-platform and works well. I won’t get into too much detail – here is an excellent tutorial – just replace ‘__’ with ‘_’. btw, the Irish for “Pages” is […]

  16. […] of the hurdles I ran into in creating my own error manager was error localization. The WP_Error class makes localizing error messages extremely […]

  17. Project M says:

    […] his help, the bugs reported in the translation thread for my themes, and a great article about localization from Weblog Tools Collection, I’ve managed to start understanding this idea. I’m now […]

  18. […] you need to read the best article there is around on localization from Weblog Tools Collection. I won’t bother going into the details of this process since the […]

  19. […] Localizing a WordPress Plugin Using poEdit « Weblog Tools Collection […]

  20. […] a plugin or theme is relatively straightforward, but JavaScript presents its own difficulties since we can’t easily call the PHP functions […]

Obviously Powered by WordPress. © 2003-2013

page counter
css.php