Translate WordPress

Updates from August, 2015 Toggle Comment Threads | Keyboard Shortcuts

  • Dominik Schilling (ocean90) 9:06 pm on August 18, 2015 Permalink |
    ocean90 • de.wordpress.org editor
    Tags: , ,   

    WordPress 4.3 has been released.

    The results of the intial build:

    • 35 release packages for 4.3 were built: he_IL, el, is_IS, it_IT, de_DE_formal, de_DE, en_GB, en_NZ, eo, fi, fr_FR, lt_LT, nb_NO, sv_SE, es_MX, th, cy, tr_TR, es_ES, sk_SK, nn_NO, pt_PT, ro_RO, en_CA, ko_KR, ar, bs_BA, hy, bg_BG, eu, pt_BR, en_AU, nl_NL, sq, and da_DK
    • 45 language packs for 4.3 were updated: hu_HU, he_IL, el, is_IS, id_ID, ja, it_IT, de_DE_formal, de_DE, en_GB, en_NZ, eo, fi, gl_ES, fr_FR, lt_LT, nb_NO, sv_SE, es_MX, th, cy, tr_TR, es_ES, sk_SK, nn_NO, pl_PL, pt_PT, sr_RS, ro_RO, en_CA, ko_KR, ca, ar, zh_TW, bs_BA, hy, bg_BG, eu, pt_BR, hr, en_AU, bn_BD, nl_NL, sq, and da_DK

    Thanks to all of the contributors who provided translations for WordPress 4.3 and subtitles for the release video! You rock! 🎉

  • Petya Raykovska 12:04 pm on May 20, 2015 Permalink |
    petya • bg.wordpress.org editor

    Notes from the Polyglots chat on May 20th 

    Locale stats:

    46 locales are up to date.

    5 locales are 100% translated but not yet released for 4.2.2:

    Localized Plugins and Themes directories are here

    @dd32 posted earlier today about Plugin and Theme repositories made available on local sites.

    • Theme Directory is available at /themes
    • The Plugins directory is also available at /plugins/
    • Both already have existing projects on translate.wordpress.org available for localizing
    • Deploy  after translation should be requested the same you would do all other rosetta translations.
    • @chantal: Is there any timeframe when it will be possible to translate plugins/themes thru GlotPress?
    • @dd32: No hard timeline, most of the groundwork is there for plugins and it’s just waiting for the floodgates to open after more testing, me or @ocean90 will be working on the Themes-in-Glotpress in the next few weeks I expect, not sure how long it’ll take to get that finalised but now that these directories are localised, we kind of want to finish the job

    Also from @dd32 about what plugins are going to be available for translations first:
    “The “official” plugins in https://translate.wordpress.org/projects/wp-plugins is the start-list, we’ll expand from there, but no definite what we’ll include first. I suspect we’d start with the most popular ones and work the way down the list, biggest impact first. We might also do some smaller plugins first to get the feeling for the process, work out any bugs.. so no, not sure yet”

    Localizing Documentation

    • There was a brief discussion around localizing the plugin and theme handbooks and different approaches to that.
    • @dd32: “We’d love to have translations of resources such as that. I personally don’t know of any effort to get that working yet though”
    • The best solution would allow Translation Editors to easily get notified on changes in the documentation so that those could be applied to localised versions. This means there has to be a direct relation between the original documentation and all the local versions.
    • According to @ocean90 GlotPress is not the way to go for Documentation
    • @zodiac1978 shared a possible solution wp.com uses: “I am doing this for the support pages for wordpress.com. They use a plugin which send you an email for every change (with a revision diff view of the changes). Then we have to manually add these changes to our localised post/page. This could be one way. But much work …”
    • Petya to post a separate post on the P2 to discuss this with more people and bring it to the attention of the metai18n team.

    Polyglots at #wceu

    • A lot of us will be at WordCamp Europe in Seville – raise your hand if you’re one.
    • Let’s discuss a more formal gathering with an agenda for Contributor day, June 28
    • Let’s discuss organising a global translation sprint around WordCamp Europe’s contributor day including polyglots who’re not in Seville
    • Petya to post a separate discussion topic on make/polyglots about this

    If anyone has anything to add to the notes, feel free to drop it in the comments.

    Thanks everyone!


  • Petya Raykovska 7:30 am on April 22, 2015 Permalink |
    petya • bg.wordpress.org editor  

    Translation reminder: 4.2 will be released on Thursday 

    Dear Polyglots,

    The upcoming release of WordPress will become available on Thursday. This is a reminder for the translation editors of locales that are at more than 90%. Let’s try to translate the new strings for the release before Thursday.

    Please remember that for the language pack to be automatically built, you need to have the following projects at 100%:

    Even though they’re not required for an automatic release, it’s nice to have  Twenty Fifteen and Akismet at 100% too as they come packaged with WordPress.


    Thank you in advance for your work, let’s make 4.2 the most up-to-date release in terms of languages available.



    • Besnik 9:13 am on April 22, 2015 Permalink | Log in to Reply

      Thank you for the reminder!
      It seems that https://translate.wordpress.org/projects/wp/dev is not quite informative. I’ve considered sq was at 100% complete. I think we need a way to automatically get reports of this kind for one’s locale as soon as new strings are added. Especially now with the new policy of building only locales at 100%. One could miss the release only for a couple of dumb strings just because he didn’t know they were added in the middle of the night. Remember also that many translators are not taking care only of WordPress, to be able to check any change every half an hour.

      • Petya Raykovska 11:11 am on April 23, 2015 Permalink | Log in to Reply

        Hey hey. The only notifications for new strings we have currently are on Slack. I agree notifications would help a lot and they are on the map for GlotPress, but haven’t been implemented yet and there’s no date for when they will be available.

        In the mean time the only thing I can guarantee is that I will be reminding translation editors before releases to make sure we don’t skip automatic builds of locales that are above 90%.

    • DjZoNe 11:04 am on April 22, 2015 Permalink | Log in to Reply

      Thanks for that reminder, altough hu_HU is not 99%, it’s 100% in every section, with no untranslated strings, but GlotPress shows 2 untranslated ones, which I cannot find.

    • Gabriel Reguly 2:47 pm on April 22, 2015 Permalink | Log in to Reply

      Try https://translate.wordpress.org/languages/hu-hu to find the 2 missing ones.

    • Gabriel Reguly 2:48 pm on April 22, 2015 Permalink | Log in to Reply

  • PSManiac 6:33 pm on October 25, 2014 Permalink |

    Hi, Can You tell me who validate the Polish translations? I’m interested spacially for BuddyPress translation. Can I apply if there is no one?

  • Tomasz Ostrowski 6:57 pm on September 25, 2014 Permalink |
    Tags: , ,   

    I’d like to ask you to allow me to validate translations for Polish buddypress. There are 817 waiting strings and only 34% approved translated. I think nobody is working on this translation.

  • OC2PS 10:53 am on April 22, 2012 Permalink |
    Tags: Approval, Translated, , ,   

    How exactly does http://translate.wordpress.org work?

    I notice that people have contributed a lot, and yet, the translation are not available.

    e.g. At https://translate.wordpress.org/projects/bbpress/plugin there are plenty of items listed as “Waiting”. e.g. Polish, Romanian, French and Czech have 0% translation completed, but almost 100% strings in “waiting”.

    Similarly, at https://translate.wordpress.org/projects/buddypress/dev Danish, Romanian, and Czech have almost 0% translation completed, but almost 100% strings in “waiting”.

    This has been the status for many months (I am not exaggerating in the least). So how do we move strings from “waiting” to “translated”?

    • oc2ps 10:55 am on April 22, 2012 Permalink | Log in to Reply

      Please add me as a validator for bbPress and BuddyPress

    • M. 11:03 am on April 22, 2012 Permalink | Log in to Reply

      That’s why I’ve resigned to contribute in translation program, because my validator for Polish isn’t accepting and checking translations for months…

      • OC2PS 11:15 am on April 22, 2012 Permalink | Log in to Reply

        Sorry to hear that. Shouldn’t be this way. Perhaps we can have a community validation program instead of having to rely on individual validators who may be pressed for time…

        • M. 11:18 am on April 22, 2012 Permalink | Log in to Reply

          Maybe. But I have also mentioned this here and heard only that I should talk about this on community forums and with validator himself. But validator doesn’t want to cooperate, and there’s even no exact community to talk abot. So existing validator desn’t want to transfer his permissions to me (or someone other) and administrators of this site doesn’t want to nominate new one. And we are stuck! I have made a lot of translation last year and it’s still waiting for approval. I’m participating in many translation programs, but this one is the most dissapointing…

    • Stas Sușcov 12:19 pm on April 22, 2012 Permalink | Log in to Reply

      While you might have some points here, I believe you are wrong (at least in the case of Romanian team).
      What you might be looking at are projects that were created from older po files and left this way right after the import. It doesn’t mean that there are people doing it at all!

      Usually those translations can’t be validated without an in detail review. And usually that happens because the translation team simply has no enough time to do that.

      In future, please do not make a general thing about something like this. Reading this I felt like people that should do validations, are ignoring contributions, which is not. It’s more a problem of time and priorities (what and when should be ready, rather than, all and anytime should be ready).

      • M. 12:26 pm on April 22, 2012 Permalink | Log in to Reply

        And what if Polish team is me and validator who desn’t have time for half a year now?

        • de ce? 3:49 pm on April 22, 2012 Permalink | Log in to Reply

          You can always ask for validator rights :-)

          • M. 3:59 pm on April 22, 2012 Permalink | Log in to Reply

            I was! But they Ze told me that we that thay have an Validator for Polish now and that I should contact with him. I’m in the black hole…

            • 4:31 pm on April 22, 2012 Permalink

              Ok, this needs a reply from @waclawjacek. Come to think of it, a reply has been pending for a while…

            • M. 4:32 pm on April 22, 2012 Permalink


            • epawel 5:21 am on July 5, 2012 Permalink

              any updates in this subject? I’m very intrested in translation of BuddyPress. I can see almost 900 terms waiting but nothing is availble. I need these translation in big international project if they will not be aprooved by validator I’ll be forced to translate everything from begining myself. Could you help please?

            • epawel 12:34 pm on July 5, 2012 Permalink

              Is there any way to contact Validator for Polish – is it @waclawjacek ? Thanks in advance for any response

    • pavelevap 1:00 pm on April 22, 2012 Permalink | Log in to Reply

      Hi, I am one of Czech validators and main problem is quality of waiting translations. Zero rate of approval is mainly due to basic problems with terminology, respecting basic WP translations, etc. Many users add translation and do not see context of translated strings on live site. And then validator can test waiting projects, export current suggested translation, try it on live site and can see that it is better in English than with this translation for most of users. But every user can download and use current (also waiting) translation and use it on its own site. But usually these translations are not as good as going officially public.

      What should you do to become validator and improve it? Translate several strings and contact current validators. They will check quality of your suggested translations, you can talk about problems and then they can give you validator access. As I know, there is no ignorance for community work, but validators usually prefer quality and if suggested translations are not very good, there is usually not much time for them to make it better and go through large projects like bbPress and modify every suggested string. But we welcome every experienced user that will be interested in improving current status. But cooperation and community work is not “give me validator rights and I will approve it and make it better”. You should suggest many strings with high quality and then contact current validator team to show them your good work. I am sure that there will be very positive response…

      Yes, this situation is not the best solution, but I am not sure if there is any better. It is similar to WP core development. There are many ideas and many more patches, but only the best can go in.

      • pabenes 8:24 am on April 23, 2012 Permalink | Log in to Reply

        Hi, thanks for posting this – this helped me to understand translating much better. But I don’t know how to download those waiting strings – I would like to test bbpress Czech translation on my site, but I didn’t manage to download waiting translations. Thanks in advance for your reply and thanks for your work.

        • 8:39 am on April 23, 2012 Permalink | Log in to Reply

          You can download strings (filtered whichever way you like) by using the links at the botton of each screen:

          Don’t forget to download both formats, .po and .mo

          • OC2PS 8:44 am on April 23, 2012 Permalink | Log in to Reply

            Are you sure? I think only “translated” parts are downloaded, not the “waiting” strings.

            • 8:46 am on April 23, 2012 Permalink

              “Waiting” is not a concept in .po files, so no, those aren’t downloaded specifically.

            • 9:12 am on April 23, 2012 Permalink

              Correction, exporting “waiting” strings, will give you a .po with translations.

            • OC2PS 8:48 am on April 23, 2012 Permalink

              My bad! Actually, what I should have said was, with the Export all, only “translated are downloaded”. But if you set the filter/search to “waiting approval” and then export dropdown to “matching filter”, then you can download the “waiting” strings only…but for pabenes’s purpose, he wants to get a combination of approved, and “waiting”…

            • pabenes 8:50 am on April 23, 2012 Permalink

              Yes, that’s how i managed to download those waitings – luckily in this case, there are just nonaproved :)

    • de ce? 3:55 pm on April 22, 2012 Permalink | Log in to Reply

      About the Romanian projets:
      We are behind with a couple of launches, so the main project (multisite is still incomplete) has the highest priority. The side projects will always have a lower priority. An I second what Stas said above: buddypress and bbpress translations need a detailed review, but we’re working on it.

    • M. 4:00 pm on April 22, 2012 Permalink | Log in to Reply

      I have submitted Polish translations to mobile apps, dashboard, buddy press, etc… and they’re still waiting, and waiting… and wordpress looks worse and worse in Polish…

    • OC2PS 7:05 am on April 23, 2012 Permalink | Log in to Reply

      @pavelelap, @de ce
      I understand there is always the issue of time, resources and priorities, and that’s why I suggested a community-validation scheme, as opposed to waiting for individual validators. Don’t take it personally – it’s nothing against you…all I am saying that validators are also humans and have competing demands on their time. So instead of making one validator slog, how about simply allowing the community to vote on different translations. If you have just one translation available for the string, then once it hits a certain number of votes, it is moved to translated. If there are multiple translations, then the string with the most vote wins – or maybe in case of multiple translations, where the votes are fairly evenly split, the validators are called into action. This would greatly reduce the workload of validators, increase the speed, and efficiency of translation deployments without losing much by way of quality. Sure, there might be times where you might see vote spam and bad quality translations getting in…but as Matt (Mullenweg) himself says, usage is like oxygen for ideas…if the bad translations go out, the WP user community is large enough that these will be quickly caught and stamped out, a bit like in the case of Wikipedia…

      • M. 7:09 am on April 23, 2012 Permalink | Log in to Reply

        What about this great tool: http://crowdin.net/ ?

        • 9:05 am on April 23, 2012 Permalink | Log in to Reply

          Seriously? Not GPL, proprietary license, can’t contribute to the code…

          • M. 9:20 am on April 23, 2012 Permalink | Log in to Reply

            but they have free acces for open source projects

            • 9:27 am on April 23, 2012 Permalink

              Keep in mind that translate.wordpress.org is not mandatory for translating, just for building, releasing and distributing packages. If you want to use Crowdin, knock yourself out, as long as it’s clear that your “endpoint” before building needs to be translate.wordpress.org.

          • OC2PS 9:23 am on April 23, 2012 Permalink | Log in to Reply

            It’s not necessary to use the tool itself. Perhaps GlotPress could adopt some of the principles. e.g. using translations across projects.

            So if WP, BP, bbP, Rossetta all have “Add New”, then when translating/validating BP in Hungarian, I have the option of using the same translation as WP if I want to. That’s brilliant!

            • Andrew Nacin 5:13 pm on April 23, 2012 Permalink

              Your example highlights exactly the main problem with regards to shared translations. What does “Add New” mean? In core, we use gettext contexts, so “Add New” with regards to a post, or a media item, or a link, or a plugin, are all different strings.

              But for a plugin for Fruits, the context of “Add New” is pretty clear — add a new fruit. No gettext context is necessary. But if we reach into shared memory and find “Add New” from some other project and it isn’t the right tense/agreement/whatever for the Fruits plugin, then we have failed.

              That’s not to say we shouldn’t do this, or that we’re not going to do this. I have been doing some research into translation memory implementations to see how feasible it is. But even then, strings would still be “fuzzy” or “suggested” by default. We would not make them all “current”.

            • OC2PS 5:43 pm on April 23, 2012 Permalink

              I agree. Translation is always complex.

              I think that ideally for a translator, the context shown should be not the gettext context but the live context, i.e. a snippet of the page where the string appears, with the string itself highlighted. Sounds like a massive project and probably not feasible.

              What I said above is basically comparison of English text stored in the string. If there is identical English text across projects then in one project of that is translated and in the other it is untranslated and a translator goes to that string to translate, then he is served “suggestions” which *might* save him some time and effort.

            • OC2PS 5:47 pm on April 23, 2012 Permalink

              P.S. In the spirit of “not here”: https://glotpress.trac.wordpress.org/ticket/194

      • OC2PS 8:50 am on April 23, 2012 Permalink | Log in to Reply

        Also, another option: let any translations for untranslated strings be approved by default. Validators only come into play when people find a string is wrong and submit alternate translations.

        • M. 8:54 am on April 23, 2012 Permalink | Log in to Reply

          That’s the way it works in other systems (WebTranslateIt, Pootle)

          • OC2PS 9:06 am on April 23, 2012 Permalink | Log in to Reply

            Not to mention Wikipedia 😉

            • 9:07 am on April 23, 2012 Permalink

              Do we really want to have a “discussion” page for every single string?

            • OC2PS 9:11 am on April 23, 2012 Permalink

              😀 Maybe not. But a comment string to provide context would be nice.

              But back to your point a bit more seriously, no we don’t have to have a discussion page for every single string. But it would be good to have a discussion area on .org sites where any contentious items can be discussed on a message board.

            • OC2PS 9:11 am on April 23, 2012 Permalink

              …if need be

            • Stas Sușcov 9:36 am on April 23, 2012 Permalink

              Creating a mailing list seems more natural and I encourage you to consider that as an option instead of forcing people use new tools.

            • 9:37 am on April 23, 2012 Permalink

              We have a pt_PT specific P2 for discussing translations, with a glossary page. It works quite well.

        • 9:04 am on April 23, 2012 Permalink | Log in to Reply

          I strongly (and subjectively, ok) disagree with this. It might be doable for less popular projects, but there are just too many people eager to “fix” things and bork a consistent translation. Revising 1000s of strings every time is simply not feasible. Maybe an option per language, although I can guarantee that for pt_PT, the behaviour will always be “waiting” by default.

          • OC2PS 9:09 am on April 23, 2012 Permalink | Log in to Reply

            I understand your reluctance. But if you parse my words again, here’s what I said: If there is an untranslated string, then the first translation provided for it is approved automatically. However, if people find that a string is wrong, and 1000s of people decide to submit fixes, well, that’s when the validators come into play. That’s when the validators check and compare and allow or refuse. This way you get stuff out of the gate quickly, and even if 1000s of people submit their own versions for a string that’s already ok, it doesn’t matter because an ok string is already out there, and validators can have a look or ignore those “fixes” based on their own time commitments and priorities.

            • 9:11 am on April 23, 2012 Permalink

              I did, but you need to walk on the validator’s shoes for a bit; you are considering a universe of a few untranslated strings, say a few hundred. This process for a few thousand is a nightmare.

            • OC2PS 9:20 am on April 23, 2012 Permalink

              No, I’m not. In fact, it is worse for everybody right now, including for validators. At the moment, validators have to go and individually approve every single string that is submitted. What a nightmare for the validator, what a demoralizing wait for translators, and of course a disappointing disfunction for polyglot users of the software.

              In a scheme where all “new” strings submitted are automatically approved, validators become an “optout” or positive filter, as opposed to an “optin” or negative filter.

              Now let’s say 1000s of folks submit 1000s of “fixes” for each of the 1000s of strings. How is that different from today? How will it increase work for moderators? If anything, it would reduce work for them because they have to look a fewer (probably contentious) strings. Maybe it won’t change their workload if there are discussions around these strings and that extra work would balance out the gains from fewer strings…I don’t know…maybe you can scrap the discussions…or maybe try it and scrap it if it doesn’t work….

              But now look at it from the perspective of the translators and users. The first translator, who puts in the work and effort to translate the software is rewarded as his translations are deployed and he can immediately use the software in his/her language.

              From the perspective of the users, they get multiple languages for the software much faster, making them happier.

              From the project perspective, it can increase the usage of the software in non-English and multilingual regions.

            • 9:31 am on April 23, 2012 Permalink

              Maybe. I’m still not convinced, but the obvious way to settle this is to create a ticket and ask other validators for feedback/opinion. I don’t get to decide by myself.

            • OC2PS 10:05 am on April 23, 2012 Permalink

            • de ce? 12:00 pm on April 23, 2012 Permalink

              I can’t agree. Basically, instead of looking into the waiting list, as a validator in a system like this I will be also looking into the translated strings, just to make sure everithing is in good shape and consistent.

            • OC2PS 12:04 pm on April 23, 2012 Permalink

              That’s a fatal flaw in your thinking. You are looking at it as your sole responsibility to make sure everything is correct. However, in the suggested model, the responsibility is dispersed. You don’t have to look at anything to make sure its correct. When people receive the translations, they will know if it’s correct or not, and if it’s not then they will submit alternatives…so you will only need to look at the alternatives….in other words, you won’t have to worry about and waste time on going through the 80% translations that are correct. You will only have to look at the wrong ones, for which alternatives have already been submitted.

            • 1:04 pm on April 23, 2012 Permalink

              Please moderate you words. There is no ‘flaw’ that I can see, just different opinions. That said, this discussion should be happening on the ticket, anyway.

            • 1:08 pm on April 23, 2012 Permalink

              Also on http://blog.glotpress.org, but certainly not here

            • OC2PS 1:18 pm on April 23, 2012 Permalink

              @de ce?

              If that was offensive, I offer an unqualified apology.

          • M. 9:12 am on April 23, 2012 Permalink | Log in to Reply

            Ze, this english-polish mix rather is not looking good…

        • pavelevap 11:13 am on April 23, 2012 Permalink | Log in to Reply

          I also disagree. Distributing wrong translation is nightmare. Personaly, I hate wrong translation because I usually do not understand it. I do not know what plugin settings really mean because translated strings do not make sense. I tested several translations of different plugins and usually it is a mess. Sorry. I use localized version of WordPress and after every update I have to delete localization files distributed with one plugin (large project) because there are wrong words on backend and also frontend thanks to wrong translation. So, in many cases, no translation is much more better solution.

          But on the other side there could be some kind of option for validators to allow distributing also waiting translations to users. I disagree with marking them as translated in GlotPress – it would be a real mess for validators. But we can let these strings as waiting and validators could mark specific project to distribute also waiting strings (or do it automatically for projects where there are more than 80 % waiting strings). And we will see… What do you think about it?

          • OC2PS 12:06 pm on April 23, 2012 Permalink | Log in to Reply

            I think it should be at the discretion of the project owners, not at the discretion of individual language validators.

            • pavelevap 3:02 pm on April 23, 2012 Permalink

              Yes, project owners also could make this choice, but they do not know anything about quality of waiting translation.

            • OC2PS 3:04 pm on April 23, 2012 Permalink

              Doesn’t matter. It’s a strategic decision about how they want translation to work for their project, and whether they are willing to sacrifice a degree of potential quality to gain an increase in speed to market.

        • Mattias Tengblad 1:53 pm on April 23, 2012 Permalink | Log in to Reply

          I agree with Zé and pavelevap here. Would be a nightmare where things already works.

          • OC2PS 1:55 pm on April 23, 2012 Permalink | Log in to Reply

            “Things already work” is quite debatable, looking at OP and the comments of M. and UncleSam

            • 3:08 pm on April 23, 2012 Permalink

              Possibly debatable, but not here. Please use the ticket or the GlotPress blog.

            • Mattias Tengblad 3:24 pm on April 23, 2012 Permalink

              Please read what I wrote once more.

    • OC2PS 7:07 am on April 23, 2012 Permalink | Log in to Reply

      P.S. I missed @Stas Suscov in previous message, though I intended to address him as well.

    • UncleSam 8:49 am on April 23, 2012 Permalink | Log in to Reply

      Same thing with the Russian translation. I took part in translating, did it to the end, checking the context each time. None of mine and others are approved.

      Still, I am ready to use what is done already, though I don’t see a clear-cut instruction how to do it

  • Manveru1986 4:26 pm on January 14, 2012 Permalink |
    Tags: ,   

    Hey, I am very dissapointed in cooperation with @waclawjacek. I have translated a lot of strings, but he still tells me that have more important things to do (wchich of course is acceptable), but some of them are waiting for acceptation for about two months. I’ve made translation of WP for Android several weeks before its release, but translated strings are still waiting for @waclawjacek‘s acceptance. If there are any administators please, help to make wp available in Polish, because now it’s hard to do, and because of @waclawjacek I’ve lost my motivation.

    • 11:04 am on January 17, 2012 Permalink | Log in to Reply

      Is this really the best venue to discuss this? No one here can intervene in internal team discussions, and I’d take the discussion to a more local place (such as pl.forums.wordpress.org) before pointing fingers here.

  • Michał Żuk 5:08 pm on January 10, 2012 Permalink |
    Tags: , ,   

    Please add me as a validator for the projects: (All projects) WordPress, bbPress, BuddyPress, WordPress for Android/BlackBerry/iOS/Widows Phone, WordPress Plugins, Rosetta.
    I also ask for access to the svn and the administration of a pl.wordpress.org.
    Polish translation for a long time is not updated and I would like to organize it all.

  • meloniq 12:53 pm on December 29, 2011 Permalink |
    Tags: , ,   

    Hi everyone,
    Polish translation and its local edition on pl.wordpress.org didnt appear long time, so I prepared it last days, and wanted to share with others… and if its possible to be used for building Polish pack…

    Available to download in this one post: http://blog.meloniq.net/2011/12/29/spolszczenie-wordpress-3-3/
    Feel free to contact me.

  • Manveru1986 9:21 pm on September 25, 2011 Permalink |
    Tags: , ,   

    Hey, I am renewing my request to be validator for Polish wordpress translation projects.

  • Ze Fontainhas 3:52 pm on August 10, 2011 Permalink |
    vanillalounge • pt.wordpress.org editor
    Tags: , ,   

    @waclawjacek I received a deploy request for pl_PL, but just the .po files in the repo aren’t enough, I also need the corresponding .mo’s. Thanks.

    • Wacław J. 12:36 pm on August 11, 2011 Permalink | Log in to Reply

      I see, sorry. Nikolay must’ve been doing the compilation himself in the past. I’ll compile them from now on. Thanks!

  • Manveru1986 8:55 am on July 30, 2011 Permalink |
    Tags: , ,   

    Hi, hey, hello!
    How can I become a validator? I see that some strings I’ve translated long ago are still not accepted! I would like to help more than only “suggest”

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
Skip to toolbar