Ready to get started?Download WordPress

Translate WordPress

Tagged: glotpress Toggle Comment Threads | Keyboard Shortcuts

  • Stephen Edgar 10:59 am on April 23, 2014 Permalink | Log in to leave a Comment
    netweb • en-au.wordpress.org editor
    Tags: glotpress,   

    As there are currently three separate discussions regarding GlotPress enhancements I’ll post this here as it probably should have been posted already.


    Arian Allenson M. Valdez (@secretmapper) — Working on GlotPress UI and profiles with Yoav Farhi (@yoavf) and Marko Heijnen (@markoheijnen) as mentors

    Secretmapper will post updates to http://blog.glotpress.org/

    Now is probably be a great time to get more involved and help shape the direction of GlotPress


  • Gary Jones 10:22 am on April 23, 2014 Permalink | Log in to leave a Comment
    GaryJ • en-gb.wordpress.org validator
    Tags: glotpress,   

    Something that would really help the English variants is to have a feature that can copy all of the original strings for untranslated as the translated string, and leaves them as Waiting status.

    Being able to check and bulk accept these strings (fixing variations where necessary) would be considerably quicker than going through each string one by one to click on Copy original and accepting.

    ~95%+ of strings are going to be identical anyway between US English and British, Canadian and Australian etc. English, so I think it’s sensible to go with the assumption that strings match, and change where necessary, than assume the US English is going to be wrong (as with all other non-English variant languages).

    • Peter Westwood 10:31 am on April 23, 2014 Permalink | Log in to Reply

      I sort of disagree :)

      I think it would be better to extend GlotPress (and possibly WordPress) to better support the hierarchical relationship between different variants of a language.

      There are similar issues when you try and use GlotPress to have translations of both formal and informal versions of another language other than English and it would I think be better if we could document the relationship between languages and then share the translations better.

      The only reason we are doing this copying and accepting is a hack to make it easier to find new strings to confirm for translation or not.

      I think Wikipedia has a solution they use to solve this that it would be worth investigating.

      • Gary Jones 10:38 am on April 23, 2014 Permalink | Log in to Reply

        I’m new to this so I’m only saying what I perceive on a practical level. I’m open and more than happy to see something more generic and functional if it involves significantly fewer “click, , ” for those 95% unchanged strings.

    • Stephen Edgar 10:49 am on April 23, 2014 Permalink | Log in to Reply

      I think this is part of the idea behind the Glossary and being able to share that Glossary between projects per https://glotpress.trac.wordpress.org/ticket/97#comment:64

      No doubt only between single locale projects for starters and then maybe something to allow the sharing between locales down the road.

    • Marko Heijnen 11:11 am on April 23, 2014 Permalink | Log in to Reply

      This should not be implemented because it’s an exception and not a rule. Also you can also only translate the strings that are needed and skip the rest.

      • Gary Jones 1:20 pm on April 23, 2014 Permalink | Log in to Reply

        From a technical standpoint, you’re probably right, but it’s much easier to see that a language is now 99% complete (because some new strings have been added late in the cycle) when it was previously 100% complete, than having to look through 95% of strings again in case new ones happen to contain a spelling that needs to be changed. Being able to mark off those that don’t need changing (i.e. by just copying the original) is pragmatically more convenient for accuracy purposes.

        If I didn’t make it clear, my intent would be to only have this feature enabled for English variants, but then as Peter said, variants in other languages may be based on a certain base translation with only a few changes needed.

        • Ze Fontainhas 2:22 pm on April 23, 2014 Permalink | Log in to Reply

          The reasoning is valid for any language that belongs to a macro language, really, not to mention the ones which can additionally have “non-regional” variants, such as formal and informal, and so on.

          Even if a language does not belong to a macro language group, it could still be the case that the difference from one variant to the next is small enough for a copy feature to make sense.

          tl:dr I’m not sure it’s an actual, bona-fide, exception.

    • Ze Fontainhas 6:34 pm on April 23, 2014 Permalink | Log in to Reply

      Marking as “not request”. Also, this debate should move to the GlotPress blog

  • Emre Erkan 10:11 am on April 23, 2014 Permalink | Log in to leave a Comment
    wordpress-tr • tr.wordpress.org editor
    Tags: , glotpress,   

    First of all, thanks for glossary. It’s a life saving functionality.

    I’m currently validating lots of project and trying to maintain order between them. Glossary is a very helpful tool to accomplish this but it’s project specific. Is there a way to use a common glossary for selected projects or for all of them?

    Please don’t say import/export. It’s not functional when you try to keep all glossaries from all projects updated. For example when translating or validating a project, you see a term which needs to be put in glossary. You can’t add it to just that project if it’s a very general term. You have to put it to all glossaries. Yoı choose a projects glossary as primary glossary and update it, export it and import it every project you’re validating.

    Possible solutions;

    • A single glossary for all projects
    • Import functionality betweeen glossaries
    • Inheritance (When you create a glossary you choose a parent and with this it contains all the terms of parent glossary)

    TL;DR -> title ^ ^

  • Emre Erkan 9:44 am on April 23, 2014 Permalink | Log in to leave a Comment
    wordpress-tr • tr.wordpress.org editor
    Tags: glotpress,   

    Is it possible to make GlotPress dashboard a little bit more useful? Like showing active projects and their statuses to validator like this: http://imgur.com/Bh2Kg1x

    It’s hard to track all the projects. I have to check every project to see if there is new or waiting translations. Just WordPress Core has 6 active projects (3 themes, WordPress, Administration and Network). There is mobile projects, plugins etc. It’ll be a handy feature if implemented.

  • Xavier Borderie 2:17 pm on April 17, 2014 Permalink | Log in to leave a Comment
    xibe • fr.wordpress.org editor
    Tags: glotpress   

    Version 3.9-fr_FR shipped with a set a bad strings (slippery fingers, honest mistake, but still). I compiled a new archive with the corrected strings, but how can I make sure the translation files are getting pushed to users who have already upgraded to 3.9?

    • Gabriel Reguly 2:32 pm on April 17, 2014 Permalink | Log in to Reply

      Been there, done that….

      We made a post telling people that the package was rebuilt and people needed to update again.

      The ones who were about to complain, did the update.

      What happened to the silent others still remains unknonw to us :-)

    • luciole135 6:42 pm on April 17, 2014 Permalink | Log in to Reply

      Unfortunately this does not fix the bug in the thousands separator

    • luciole135 9:16 pm on April 19, 2014 Permalink | Log in to Reply

      Since Saturday, April 19, 2014, the bug is fixed while yesterday, the same files had a bug.
      This is not to understand anything. What have you changed?
      Finally, the better!

      • Xavier Borderie 9:11 am on April 22, 2014 Permalink | Log in to Reply

        I changed the translation file to replace the non-breaking space with simple space character (” “).
        I would have removed the spacing altogether, but GlotPress does not allow empty translations.

  • Slava UA 9:21 am on March 9, 2014 Permalink | Log in to leave a Comment
    slaFFik • ru.wordpress.org validator
    Tags: , glotpress   

    Noticed a bug (?) while editing translation of BuddyPress here http://translate.wordpress.org/projects/buddypress/dev/ru/default

    Not all untranslated strings are showed. How did I found that:
    1) went through all untranslated strings,
    2) exported the po file of everything ru_RU
    3) opened in Poedit and noticed that some strings appeared to be untranslated, although they are not listed under Untranslated filter in GlotPress.
    4) translated them in Poedit and imported into GlotPress
    5) got the message that 16 new strings were translated.

    So in general – untranslated strings were not showing under Untranslated filter in Glotpress.

    • Sergey Biryukov 10:41 am on March 10, 2014 Permalink | Log in to Reply

      Hmm, I currently see 40 untranslated strings there. When I export the .po file and open it in Poedit, I see the same 40 untranslated strings (out of 1397).

    • Slava UA 10:46 am on March 10, 2014 Permalink | Log in to Reply

      Perhaps because I have already fixed that :) Those 40 should stay there. When I was operating – thos 16 were not in glotpress.
      It was easy to track, as they all are short strings (like Notifications %s), while those 40 are quite long strings.

  • Marko Heijnen 11:21 pm on March 4, 2014 Permalink | Log in to leave a Comment
    Tags: glotpress   

    If some of you know I’m working on GlotPress and since it’s getting more activity I would love to setup a biweekly meeting. If you would love to help out by sharing ideas or maybe contributing back then please leave a message at http://blog.glotpress.org/2014/02/28/since-we-gain-a-bit-more-activity-lately/.

  • babouselim 6:57 pm on February 2, 2014 Permalink | Log in to leave a Comment
    Tags: , glotpress, , , validate   

    I just translated 125 terms to Arabic for GlotPress Development. please validate http://translate.wordpress.org/projects/glotpress/dev/ar/default

  • Xavier Borderie 7:46 pm on January 24, 2014 Permalink | Log in to leave a Comment
    xibe • fr.wordpress.org editor
    Tags: , glotpress   

    There is still not 3.8 project for WP in GlotPress. When correcting a typo in 3.8.x, should I use 3.7 or Trunk?

    • Kenan Dervisevic 12:20 am on January 26, 2014 Permalink | Log in to Reply

      Use dev (trunk). 3.8.x in Rosetta is actually dev from GlotPress.

    • daveshine (David Decker) 3:45 pm on January 27, 2014 Permalink | Log in to Reply

      I agreen this is a bit confusing right now…!

      In my opinion this is not a good workflow and confusing for any international dev/ webmaster/ translator/ contributor.

      I would expect to now have WordPress 3.8.x project as like 3.7.x — also the development version (Trunk) should have already switched to the 3.9.x codebase so to say Trac/ Trunk.

      That would make it much more clearer.

      I thought it was already synced but monitoring the GlotPress the last few weeks I see it’s not…

  • Philip Arthur Moore 2:40 pm on December 12, 2013 Permalink | Log in to leave a Comment
    philiparthurmoore • vi.wordpress.org editor
    Tags: glotpress, , ,   

    Hi there. I have a few questions and issues that we’re trying to sort out over at vi.wordpress.org and

    1. On sites like http://ja.wordpress.org and http://es.wordpress.org there are welcome sections that I cannot figure out how to add into the Vietnamese site. There are only two users on the site right now, and we’re both Editors, and I’m not sure how page templates and/or front page content is set. Can you point me to some information on this?
    2. Do you have a list of validators for Vietnamese, or is there somewhere I can see it? The validators for the language at the moment should be me (philiparthurmoore), Tran Ngoc Tuan Anh (fitwp), and Buy Huy Thang (gsmeanspro). I thought I could control this from within the vi.wordpress.org Dashboard under Users, but it doesn’t seem to be related.
    3. We’re planning on creating a P2 for Vietnamese translators to chat with each other. Is there anything in place on the .org side of things to facilitate this directly on the .org site for Vietnamese or should I instead just set up a P2 elsewhere? I’m fine with either solution.

    Thanks in advance!

    • Ze Fontainhas 3:03 pm on December 12, 2013 Permalink | Log in to Reply

      1. You should have a page with the slug ‘/txt-welcome’ (default template), that’s the one. You can create it, if it isn’t there.
      2. http://wpcentral.io allegedly has a complete list of validators. Other than that I can check, but not right now, as I need to proxy to .org to do that.
      3. It’ll have to be outside .org, for the moment
  • daveshine (David Decker) 2:21 pm on December 11, 2013 Permalink | Log in to leave a Comment
    Tags: glotpress, string count   

    Any news on the string count issue from last year’s thread: http://make.wordpress.org/polyglots/2012/05/29/i-am-using-poedit-for-testing-localization-and/#comment-13497 — The issue is still there for the main .pot file (for example de_DE.po). GlotPress here http://translate.wordpress.org/projects/wp/dev says there are 1782 strings, but when I do a .po file export for any language from there my .po file always only has 1759 strings.

    Still no reason why this is and what’s causing it? In last year’s comment thread @sergeybiryukov mentioned a list of different strings. What are those different strings this time for 3.8

    Thanks for any help with that, really has me going nuts these days…! Also pinging @nacin and @nbachiyski for any ideas. THANKS!

  • Emmanuel Simond 8:09 am on December 5, 2013 Permalink | Log in to leave a Comment
    Tags: , glotpress   

    J’ai passé un bon moment à revoir, corriger, uniformiser et améliorer la consistance de la traduction de bbPress
    Mais je ne sais pas comment valider les modifications?

    Je connais bien d’autres systèmes de traduction tels que Transifex avec lequel j’ai traduit en français Disqus, pUpload et Elgg.org, mais GlotPress? comment obtenir les droits de relecteur?

    Merci à toute la communauté

    • Stephen Edgar 12:16 pm on December 5, 2013 Permalink | Log in to Reply

      Your should contact your local French translation team via http://fr.wordpress.org/contact/


    • Marko Heijnen 12:19 pm on December 5, 2013 Permalink | Log in to Reply

      This blog is English only since most of the people here don’t speak French.

    • pixolin 12:23 pm on December 5, 2013 Permalink | Log in to Reply

      This translates as …
      I spent a good time to review, correct, standardize and improve the consistency of the translation of bbPress, but I do not know how to validate the changes?

      I know many other translation systems such as Transifex with which I translated into French Disqus, pUpload and Elgg.org but GlotPress? how to get permission to proofread?

      Thank you to the entire community

      Dear Emmanuel,

      as far as I know the Polyglot group consists of a bunch of more experienced users that have been given status as Validators. They check translation proposals and acknowledge when they feel the translation to fit the needs. Don’t ask me though how they get elected as Validators. I haven’t found any information on that before. (With which I don’t want to question the selection process – I just don’t know myself how it works.)


    • emanwebdev 2:03 pm on December 5, 2013 Permalink | Log in to Reply

      Hola!, Muchas gracias por su respuesta!

      Sorry, I saw a big “Welcome, polyglots!” upon landing on this page this morning, et voilà ;)

      Anyway, special thanks fly to pixolin, a real polyglot, who managed to find a way to understand an extremly seldom language spoken by forum intruders only :)))

      Well, go ahead, your time is precious; then the key is:
      “They check translation proposals and acknowledge when they feel the translation to fit the needs.”

      So, the little eman shouln’t worry; don’t worry, be happy, theses hours are not lost,
      A Validator will put his hat, a wonderful pair of magnifying glass, and double-check what’s been douvle-checked ;)

      Life’s good, and for sure we all are heading to a better world

      Bonne journée à tous, et amusez-vous bien!


    • Xavier Borderie 2:12 pm on December 5, 2013 Permalink | Log in to Reply

      Bonjour Emmanuel,

      Parles-tu d’améliorer la cohérence de la traduction dev sur translate ?
      Je viens de valider les 137 chaînes en attente, dont les 40 tiennes. Merci beaucoup !

      • Xavier Borderie 2:13 pm on December 5, 2013 Permalink | Log in to Reply

        En passant, j’ai fait de nombreuses corrections ici et là dans tes propositions : typographie, pluriels, cohérence (“We’re all abuzz” traduit en “” à un endroit et en “” à un autre), anglicismes, oublis, etc. Il faudra un jour revoir ensemble plus profondément la traduction de bbPress.

        Et il faudra moi que je rédige ce guide de la traduction FR que j’ai en tête depuis si longtemps :)

        Bonne journée !

        • Ze Fontainhas 2:18 pm on December 5, 2013 Permalink | Log in to Reply

          Xavier, m’enfin… In English, please

        • emanwebdev 3:51 pm on December 5, 2013 Permalink | Log in to Reply

          Salut Xavier

          Joli CV!!!! Super parcours, chapeau bas!
          T’es un veinard toi, le job trop sympa!

          bon, pour revenir à tes remarques ci-dessus:
          Oui, plein d’incohérence, mais ça, imho, c’est
          typique à WP, tout son historique est là…

          > traduit en “” à un endroit et en “” à un autre

          oui, et c’est pénible tous ces » ces ' et autres…
          ça rend le tout illisible au possible…
          encore des raisons historiques, car aujourd’hui,
          plus besoin de ça pour faire des jolis accents é è ï ò
          WP est en UTF-8 et tout va bien.

          Y moyen de tout remplacer automatiquement, mais
          après, comment rà importer ça dans http://translate.wordpress.org/ ?

      • emanwebdev 3:44 pm on December 5, 2013 Permalink | Log in to Reply

        BuddyPress en fait

        Oui, quelques chaînes sur bbPress, mais je voulais parler de BuddyPress

        Fondamentalement, quand on trouve des chaînes pas encore traduites dans
        une version précédente, ça sert encore à qqn de les traduire?

        Et la branche dev, elle est DEJA fusionnée avec son ascendante I suppose,
        donc on peut se lancer sur les chaînes non traduites

        • Ze Fontainhas 4:09 pm on December 5, 2013 Permalink | Log in to Reply

          Vous vous foutez de moi, tous les deux, ou quoi?

          If you want to discuss French translations, please use your own sites/forums/P2s/whatever. This site is for discussions that are relevant to all polyglots and in English.

  • Mente Binaria 8:29 am on November 28, 2013 Permalink | Log in to leave a Comment
    Tags: glotpress,   

    I have been asked by Min Wei to translate a project on Glotpress, but i can’t log in. Can you please help? Thanks.

  • Mattias Tengblad 4:10 pm on September 4, 2013 Permalink | Log in to leave a Comment
    DaMsT • sv.wordpress.org editor
    Tags: development, future, glotpress, organizing,   

    At times I don’t think things work to good here @ polyglots. Very much feels disorganized and poorly thought through, which then confuses us who translate and create local packages. Especially since we went from SVN to GlotPress.


    Can we please have a new Development (trunk) project @ glotpress

    When 3.6 was released someone renamed the current dev project to 3.6.x without creating any new dev project. If we are to move to GlotPress and phase out SVN, things has to work better.

    I’ve pointed this out several times, but unfortunately nothing has changed. When we use SVN, we can, in a sense manage tags/branches ourselves, something we can’t do with GlotPress. We are instead dependent on someone taking care of the projects. When 20 days goes by with no response to your request you lose the will to even try.

    I even tried to contact the core team via IRC, the third attempt nacin replied, quite vague:

    I’ve seen the thread. There will be a 3.7 project once it makes sense.

    Firstly, if a request is read, leave a message, I do not have Jedi mind powers. Secondly, when it makes sense to whom? Sorry, but It feels like everyone does as they themselves find fit at the time, not a good way to get things organized…

    There are already new strings for 3.7. Some of us want to work at our own pace and not get all strings at once. Suppose also that a language team wants to review parts of the translations for the upcoming version without involving sub versions aka have access to a development version. Shouldn’t it be possible (just like core)? We should be able to have the ability to organize and plan within our team, without technical limitations. Right now GlotPress is such limitation, at least as long as you have to chase people to get answers to questions/requests that we should be able to ask right here.

    This is exactly what I said would happen when discussions about GlotPress came up. GlotPress was and is not ready for this type of project. I think GlotPress can be really good and I will say nothing about evolution that occurs with GlotPress (some are doing a really good job with the updates of the software). GlotPress should be a plugin that the teams could operate ourselves on the local sites. It would solve a lot of problems, it would be ready when a local site is set up, and we would be able to manage all projects and users within the teams, in one place.

    You may think I’m just ranting, let it be so. When it comes to projects and computers, I am extremely organized, sometimes maybe too organized (if you can be?).

    Polyglots, the use of GlotPress and creation of packages need to be reviewed and organized!

    • Andrew Nacin 4:21 pm on September 4, 2013 Permalink | Log in to Reply

      This has nothing to do with GlotPress or its abilities.

      Rather, please accept that WordPress core is in a holding pattern. This is in part because of a number of changes to how WordPress is being developed. (As you may note, the POT files haven’t been updated, either.) WordPress 3.6.1 will be out soon, after which I will ensure there is a 3.7 project again. There have been very few string changes so far in 3.7. You’ll have at least a month to get through them.

      • Mattias Tengblad 8:31 am on September 27, 2013 Permalink | Log in to Reply

        @nacin any updates on this? I can see that you posted preliminary release dates on core. Dates that would put us as language teams in a pretty bad position. Just as core, we don’t want to rush things.

        I hope the string freeze is not ignored for 3.7, especially considering that the time frame is shortened anyway. Unless we’re talking about like 4-5 strings that are updated/added.

    • Marko Heijnen 4:37 pm on September 4, 2013 Permalink | Log in to Reply

      I can understand the main point that Mattias is making. If a trunk project will not be created then it should be posted on this P2. The changes that are now made now are not known to most of the people and there isn’t much to find about what will be changed.

    • Mattias Tengblad 4:51 pm on September 4, 2013 Permalink | Log in to Reply

      @nacin I’m pretty annoyed at how some things work here, but it is not directed against any particular person. You might accidentally have ended up in the line of fire. Harassing you (if that is how you feel) was not my intention.

      For the future, posting the information you just posted in an answer on my original post would make sense and explain a lot. When you don’t get a response in 20 days, it feels like you are being ignored.

      Last, It is kind of disappointing that you do not see the points I am trying to raise.

  • Mattias Tengblad 5:51 am on August 14, 2013 Permalink | Log in to leave a Comment
    DaMsT • sv.wordpress.org editor
    Tags: glotpress, , ,   

    Can we please have a new Development (trunk) project @ glotpress

compose new post
next post/next comment
previous post/previous comment
show/hide comments
go to top
go to login
show/hide help
shift + esc