Translate WordPress

Updates from August, 2015 Toggle Comment Threads | Keyboard Shortcuts

  • Petya Raykovska 6:19 pm on August 17, 2015 Permalink |
    petya • bg.wordpress.org editor

    WordPress 4.3 string freeze and release date 

    WordPress 4.3 is scheduled for tomorrow – August 18th. Strings have been frozen for a while, last week we also got the last 14 strings in, so we’re in a hard freeze since Friday. It would be great if the remaining strings were translated and we were prepared to launch with more than 60 locales.

    Pinging the validators for the locales who have more than 90% translated. If you get a chance, please get your locales ready for the release tomorrow.

    More than 95%

    30 locales have more than 95% translated. Translators and translation editors, please head to your locales and translate the about page strings, so we can prepare the packages for the release on Aug 18th

    Locale WP Locale Version GlotPress
    Albanian Shqip sq 4.2.2 95% sq Details
    Arabic العربية ar 4.2.4 99% ar Details
    Azerbaijani Azərbaycan dili az 4.2.4 99% az Details
    Bengali বাংলা bn_BD 4.2.2 97% bn Details
    Bulgarian Български bg_BG 4.2.4 99% bg Details
    Chinese (China) 简体中文 zh_CN 4.2.2 95% zh-cn Details
    Chinese (Taiwan) 繁體中文 zh_TW 4.2.4 97% zh-tw Details
    Croatian Hrvatski hr 4.2.4 98% hr Details
    Danish Dansk da_DK 4.2.4 98% da Details
    English (New Zealand) English (New Zealand) en_NZ None 99% en-nz Details
    English (UK) English (UK) en_GB 4.2.4 99% en-gb Details
    Estonian Eesti et 4.2.4 95% et Details
    German (Switzerland) Deutsch (Schweiz) de_CH 4.2.4 95% de-ch Details
    Hungarian Magyar hu_HU 4.2.4 99% hu Details
    Icelandic Íslenska is_IS 4.2.4 96% is Details
    Korean 한국어 ko_KR 4.2.4 99% ko Details
    Lithuanian Lietuvių kalba lt_LT 4.2.2 95% lt Details
    Norwegian (Nynorsk) Norsk nynorsk nn_NO 4.2.4 99% nn Details
    Occitan Occitan oci 4.2.4 99% oci Details
    Pashto پښتو ps 4.1.2 96% ps Details
    Persian فارسی fa_IR 4.2.4 95% fa Details
    Portuguese (Brazil) Português do Brasil pt_BR 4.2.4 95% pt-br Details
    Portuguese (Portugal) Português pt_PT 4.2.4 99% pt Details
    Russian Русский ru_RU 4.2.4 95% ru Details
    Serbian Српски језик sr_RS 4.2.4 99% sr Details
    Spanish (Mexico) Español de México es_MX 4.2.4 95% es-mx Details
    Spanish (Peru) Español de Perú es_PE 4.2.2 95% es-pe Details
    Tagalog Tagalog tl 4.2.2 99% tl Details
    Turkish Türkçe tr_TR 4.2.4 99% tr Details
    Ukrainian Українська uk 4.2.4 99% uk Details

    Pinging the translation editors for the langueages mentioned above: @gaygysyz, @wordpress-tr, @krzheiyah @Kel-DC, @marcozink, @hiwhatsup, @dimadin, @lanche86, @Reyson, @Atrax, @SergeyBiryukov, @slaFFik, @jenia, @krioteh, @catiakitahara, @Gabriel Reguly, @Dianakc, @rafaelfunchal, @valeriosza, @vmassuchetto, @vanillalounge, @alvarogois, @nbar, @mani_monaj, @Gonahkar, @sajadsafi, @msadat, @meinmycell, @chriscena, @hgmb, @peterhoob, @pokeraitis, @jonasltu, @drssay, @Kaul, @martian36, @stebbiv, @egill, @samueljon, @valurthor, @djzone, @fgywp, @sooskriszta, @Blintux, @openstream, @swissspidy, @swissky, @Erko.Risthein, @UncleOwl, @petskratt, @westi, @s1m0nd, @DJPaul, @GaryJ, @tareiking, @Shevy, @culturemark, @tntc1978, @DanielJuhl, @hammerfar, @brianbrandt, @GeorgWP, @maxemil, @weblysdal, @intoxstudio, @heinohund, @mikwolbre, @Mirta, @yuraz, @Kirin_Lin, @pseric, @s9011514, @levinng, @carrielis, @bibi-wang, @Dreamcolor, @jiehanzheng, @dallaslu, @xslidian, @musiclog, @franklsf, @jimmyxu, @tareq1988, @wzislam, @badsha_eee, @muhsinmushviq, @rasheed, @alex-ye, @Besnik

    Seven locales have more than 90% translated

    Locale WP Locale Version GlotPress
    French (Canada) Français du Canada fr_CA None 94% fr-ca Details
    Hazaragi هزاره گی haz 4.1.2 92% haz Details
    Macedonian Македонски јазик mk_MK 4.1.1 92% mk Details
    Myanmar (Burmese) ဗမာစာ my_MM 4.1 92% mya Details
    Slovenian Slovenščina sl_SI 4.1.2 94% sl Details
    Uighur Uyƣurqə ug_CN 4.1.2 91% ug Details
    Vietnamese Tiếng Việt vi 4.2.1 93% vi Details

    Pinging the translation editors for the languages mentioned above:

    @rilwis, @philiparthurmoore, @tucq, @htdat, @tony.bui, @huynetbase, @Moorshidi, @Alim-Ahat, @andrejz, @Hekos, @st1FFFy, @herzcthu, @minnkyaw, @chombium, @Kuzmanov, @goce.mitevski, @jjanev86, @l10n, @server986, @tohave


    Thank you all for your help and the time you dedicate to the project. Now going to go take care of the bg_BG strings, as it’s also only 99% done.



  • 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.



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

    • 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.

    • 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.

    • 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%.

  • Krzysztof Trynkiewicz (Sukces Strony) 8:54 pm on December 15, 2014 Permalink |
    eclare • pl.wordpress.org validator  

    @nacin We still have a few strings that aren’t translatable.


    What about them for 4.1?

  • Mushviq Abdulla 5:17 pm on December 9, 2014 Permalink |
    muhsinmushviq • az.wordpress.org editor  

    Hello everyone. Please remove site https://az-tr.wordpress.org/. Because translations for this location is not conducted. Website https://az.wordpress.org/ should be renamed with Azərbaycan dili(Azerbaijani language)
      on Azərbaycan Türkcəsi (Azerbaijani Turkish).

  • Petya Raykovska 2:51 pm on December 8, 2014 Permalink |
    petya • bg.wordpress.org editor
    Tags: , ,   

    Polyglots chats Summary Dec 3rd and Dec 4th… 

    Polyglots chats Summary: Dec 3rd and Dec 4th


    We’re going to try to adopt the structure of core’s chats summaries. Here goes.


    • Tagalog has a new translator team thanks to a call for new translator on slack worked well. @krzheiyah, @kel and @druesome joined the effort
    • 41 locales are up to date
    • We have some of the new strings in GlotPress ready to translate.


    • We still don’t have a 4.x Project on GlotPress
    • No string freeze yet and no information on when it or RC1 is happening (it’s obviously late)
    • 15 locales still behind on 4.0.1. (at the time of the meeting they were 16). @netweb has created a list of locales that are packaged still with 4.0


    • Research how different teams approach communication of translations and create a recommended process for new teams (@petya will work with @vanillalounge and @coachbirgit and post on the P2)
    • Work with core to create the 4.x project on GlotPress (that’s on @ocean90 and @nacin)
    •  Think about a way to alert validators and translators that there are new strings to translate and help them with packaging (Thanks to @netweb for raising the question)
    • @petya will add instructions on creating and importing/exporting Glossaries to the Handbook (Thanks to @deconf for pointing out we actually can)

    Open discussion topics:

    • GlotPress improvements: suggest translation button, communication tools for validators and translators, Glossary
    • Language style guide and how to build them
    • Communication channels for translators and validators and different approaches to discussing translations
    • How we can help a locale that lacks translators/validators: we ask the current validators if they have anyone, then try everything we can
    Next Polyglots chats: Wed, 10th Dec, 11:00 UTC and Thu, 11st Dec, 02:00 UTC
    • Stephen Edgar 11:39 pm on December 9, 2014 Permalink | Log in to Reply

      We have 43 locales now up to date with 4.0.1 :)

      How are we looking for 4.1? Without clicking through each project and sub project (/admin, /network, /akismet et cetera) it’s difficult to get an overview… It would be great if we could extend some type of summary at https://translate.wordpress.org/languages.

      Kind of related and raised in #gotpress on Slack was this from @joostdevalk:

      “…overall stats per locale to GlotPress”

      My thinking here is rather than “overall stats per locale” we add a summary of percentage completed for the current release and the next release. For 4.1.x this would include stats from /dev, /admin, /network, /akismet, /twentythirteen, /twentyfourteen, /twentyfifteen yet for 4.0.x the stats would not include /twentyfifteen as that wasn’t an included project for the 4.0.x release if y’all get my drift.

      • Petya 9:20 am on December 10, 2014 Permalink | Log in to Reply

        I use http://wpcentral.io/internationalization/, Marko recently added percentage for core, makes it easy.

        For the rest, if need be, I do by scanning locales one by one. Can’t really afford doing proper stats for everything now, would mean way too much time.

        It would be great to have that here https://translate.wordpress.org/languages along with all the other info that’s currently at wpcentral.io and the percentage for each project that’s required for a locale to get as an option in the initial WP install.

    • Emre Erkan 3:15 pm on December 8, 2014 Permalink | Log in to Reply

      FYI tr_TR is no longer at 4.0, it’s at 4.0.1 :)

  • Birgit Olzem 5:25 pm on November 26, 2014 Permalink |
    CoachBirgit • de.wordpress.org editor
    Tags: , , translation tools   

    Discussion: Using translation tools with GlotPress? 

    Discussion: Using translation tools with GlotPress?

    In our weekly chat meeting today, we´ve discussed over a feature request, to implement Google Translator into GlotPress. A feature, that was build in in the past, but was removed after another discussion. (s. here) Sidenote: Some very ambitious validators were misusing it to get their language at 100% and it resulted in very poor translations  Since API keys are needed and if those aren’t passed it will not be displayed and not  because of misusing it.


    Upcoming concerns from chat

    • Is it useful, to let the locale editor decide, if translation tools are in use
    • it would maybe useful to get a first raw translations for new locale, but for using it needs proofreading
    • a validator for a locale should be a good native speaker, so doesn´t need a Google Translator
    • If a validator decides to misuse the tool, there’s a very little chance anyone will be able to notice unless a user speaks up.
    • Keep in mind that the Google Translate API is a paid service
    • Maybe part of solution, or just making easier for translators is to list on local site links to online tools for translating and checking spell

    Let´s discuss

    • What are your best practices as translator / validator?
    • Do you use any translation tools for raw translations?


    • Kirtan Gajjar 1:46 pm on November 27, 2014 Permalink | Log in to Reply

      Actually, i was the one who raised this request in technical chat.

      Let me explain why. First have a look at –


      I am new to this community and i am the lone translator of my language gujarati. Particularly for my locale, i find google translate very much helpful. My case is same as what @catiakitahara mentioned. My locale is almost starting from zero and currently, i am the only translator(and there’s no validator, i hope i will be some day :)). As described in the document attached above, i find it very useful in my workflow. I use it often. It is mostly correct for single words, and full sentence just needs a bit of rearrangement and proofreading.

      However notwithstanding chat we had yesterday, i’ve also considered the point that its really pain for validators to correct poorly translated strings. In my mind i have two solutions –

      1. Easy to implement and recommended

      As @steveagl mentioned

      “Letting locales validator choice with an option if have the link active or not would be a nice compromise”.

      Let the validator decide to weather or not to put a link of google translator for his locale.

      2. May be hard to implement, but offers great flexibility.

      This includes 1st feature + an additional feature

      If any validator who has activated GT link, and finds out that a particular person is misusing GT way too much, then the validator can ban the user from using GT.

    • Xavier Borderie 1:20 pm on November 27, 2014 Permalink | Log in to Reply

      I only use Google Translate to get variations for a single word to be translated. I hardly ever use it for full sentences, and even so have to proofread, rewriting and move around that translation before it feels natural.

    • Stefano Aglietti 9:59 pm on November 26, 2014 Permalink | Log in to Reply

      I know is just not fully related to translation tools, but in some way are internal tools or better internal improvement of glotpress a couple of thing i just mentioned in the chat today cause i joined really late and meeting was ending.

      An helpful tools that great integrate with glossary (i think we should discuss in the future about glossary works and how should be improved) is to have one or more editable pages by single locales in glotpress where we can define style guides to translations that are stuff that can be accommodated into the glossary. I refer to how sentences should be translated persona or impersonal, how capitalization of words and sentences have to done (ex month or day of the week in italian are ALWAYS in lowercase) etc.

      Another helpful “tools” should be short messages that we can make appear in every project even in index pages like https://translate.wordpress.org/languages/it to inform contributor about how things are going, for example whith the problem we had on glotpress on 4.0.1 release alert people that come to check if they can help, that untralsated string or just typos correction should be postponed cause there is a problem, or that a new group or project should soon change so better not spend time for nothing and other message like that. I suppose it’s something that can be easily don but should help a lot. We of it_IT fell a lot the need to have a place for translation guidelines fully integrated in glotpress cause more than 50% of invalidated suggestion from translator are about thing that need to be correct bu hand and are all related to this stuff. As I’m really waiting to have a motivation reject way to inform people why theirs translation were rejected.

    • Stefano Aglietti 9:44 pm on November 26, 2014 Permalink | Log in to Reply

      I’m with Ze about the need to have proper contexualized comments in the source code. In some cases translation tools ad GT help about some words, some sentence that sound strnage, but in lot of cases the translation is really poor. Need a lot of revision cause lot on transaltion have a sentece format in english style than in locale style. For example the “Please, …” in italian we never translate it, capitalization in sentences are lot different but google keep them ecc ecc. Letting locales validator choise with an option if have the link active or not would be a nice compromise. Google translator can be improved, but you need to submit alternative translation to it and I’m not sure the API allow this. I agree with Catiaketahara that google sometimes helps fon single labels words etc. not for full sentence. . I’m for optionally have it on request by the validators for theyr locales.

    • Catiakitahara 9:35 pm on November 26, 2014 Permalink | Log in to Reply

      I think the “validator should be a good native speaker” is quite ambiguous in this context, I guess what @coachbirgit meant was that a validator should be fluent in both languages, English and the one he’s translanting WP into.
      @vanillalounge the suggestion was to leave Google translations as an option per locale. I don’t like it too, but I can see it may be usefull for new locales starting from zero and with only one validator. It was considered because the code is already there and it’s very easy to bring it back while we find better ways to help small teams. But to tell you the truth, Google translate has improved a lot since we have the ability to improve their translations. It isn’t good for whole sentences, but it’s very helpfull in the case of labels.

      • Ze Fontainhas 9:42 pm on November 26, 2014 Permalink | Log in to Reply

        Fair enough, but I insist we do not leave the issue of properly commented and contextualized strings in the source code fall through the cracks. In my mind at least, it takes clear priority.

        • Stefano Aglietti 9:47 pm on November 26, 2014 Permalink | Log in to Reply

          Having GT as an option you can chise to show or not is something easy and with really few works. I strongly agree with you to have developers improve the contextualization and comments whne the write I18N code. The recent bad expirience with the iOS app where comments where simply unusefull should teach us something.

        • Catiakitahara 11:39 pm on November 26, 2014 Permalink | Log in to Reply

          I agree!

    • Stephen Edgar 8:48 pm on November 26, 2014 Permalink | Log in to Reply

      One of the things I noticed, maybe interpreted is a more appropriate term is that some translators have troubles understanding the original English string be it the actual English word or the English grammar.

      Using a translation tool such as offered by Bing or Google helps them understand that original string to which they are then able to edit the translation offered to their native language which they are indeed fluent in.

      So to that point of “a validator should be a good native speaker”, in a generalized view here we are actually asking validators to have a reasonable understanding of English and be a good native speaker of the locale they are translating for.

      For locales with a small team, or single translator and validator who are in this situation we should be able to do “something” to help them out, maybe integrating a translation API, maybe not, but we should be able to recommend “something” to help guide these locales and help them maintain their locale whilst they translate and recruit new contributors for their locale.

      p.s. I agree with what Ze said above, I am in no way here suggesting or recommending the translation of the English string should ever be sourced from a translator or translation API. 😊

      • Ze Fontainhas 9:24 pm on November 26, 2014 Permalink | Log in to Reply

        Yes, but

        some translators have troubles understanding the original English string be it the actual English word or the English grammar.

        The ONE thing that truly helps is not necessarily investing in being an impeccably adroit master of the English language, but much rather properly commented and contextualized strings in the source code. The issue has been raised again and again and the developers need to be made aware of this.

        That said, I do agree 100% with helping guide translators, just not through some funky, unpredictable and often puzzling API.

        • Stephen Edgar 11:06 pm on November 26, 2014 Permalink | Log in to Reply

          The ONE thing that truly helps is not necessarily investing in being an impeccably adroit master of the English language…

          …. looks up definition of adroit, for a native speaker of English I <3 Ze's writing and prose, we're all always learning new things in #Polyglots :)

          …but much rather properly commented and contextualized strings in the source code. The issue has been raised again and again and the developers need to be made aware of this.

          Yes +1

    • Ze Fontainhas 6:41 pm on November 26, 2014 Permalink | Log in to Reply

      As far as standard Portuguese is concerned, the quality of Google Translate’s suggestions is at the same level it was back in 2011, that is to say completely unusable, bordering the ridiculous. For us, the reasoning hasn’t changed, either, from 2011: it is basically a nuisance, and extra work for validators. If the majority does decide to implement it in GP, at least make it an admin-switchable option, per project or per locale.

  • DelphiKnight 1:31 pm on October 28, 2014 Permalink |
    dimitrigog • ka.wordpress.org editor  


    Today I tried to upload some files to svn.automattic.com/wordpress-i18n, but unfortunatelly my wordpress.org username and pass wasn’t accepted.

    Can you help me, please?

    P.S. I know and using translate.wordpress.org/projects for current translates, but some reasons I need to upload new and older versions of translating to the SVN.

    Thank You!


  • Chandra M 8:37 am on September 15, 2014 Permalink |
    nhuja • ne.wordpress.org editor
    Tags: flag, nepal,   

    Hi, Does anyone know who runs this page http://wpcentral.io/internationalization/ne/. If its official, I wanted to change that flag to Nepal flag. Currently, its showing another flag.

  • Nashwan Doaqan 11:02 am on August 25, 2014 Permalink |
    alex-ye • ar.wordpress.org editor

    I would like to have i18n SVN access for the Arabic(ar) repository.

  • Ze Fontainhas 3:07 pm on August 11, 2014 Permalink |
    vanillalounge • pt.wordpress.org editor  

    Trying to wrap my head around the 4.0 silence, here are a few personal thoughts. They’re not directed at anyone in particular, as I can’t judge other factors that may be impacting the issue, and are just an attempt at trying to summarize the issue (this one issue, obviously; there are others):

    • 4.0 is coming and we have, yet again, no string freeze
    • We have no Dev project in Translate with 4.0’s strings
    • It’s August. In many places around the world people are on holidays, which makes the effort to translate and validate what will most certainly be a torrent of new strings nearly impossible
    • We keep hearing about (and seeing in betas) the monumental (and very laudable) effort to focus on localisation
    • We were announced this: no one on polyglots that I know was involved in any kind of defining discussion prior to this announcement
    • As far as I can tell, no polyglot is involved in the current discussion either. Granted, this may be due to a lack of initiative to participate, but, given the above, an understandable one
    • The bare minimum would be to provide some feedback. We all understand that schedules are tight and contribution is voluntary, but a little heads-up goes a very long way.

    Summing up, what we see is our work, defined outside this group, piling up, with what seems the expectation that “oh, polyglots will translate when everything else has been taken care of”, apparently oblivious the fact that we’re responsible for providing WordPress for more than half of total downloads worldwide.

    If you feel that you have something to add, do discuss the points as you see fit, but please keep the debate civil, polite and constructive. We all (and I mean all) work hard, disrespect has no place here.

    • Mattias Tengblad 1:25 am on August 14, 2014 Permalink | Log in to Reply

      Interesting read https://irclogs.wordpress.org/chanlog.php?channel=wordpress-dev&day=2014-08-13&sort=asc#m905811

      I am somewhat concerned about the attitude displayed by some core members, but at the same time happy that others are trying to change the situation.

    • pavelevap 12:14 pm on August 12, 2014 Permalink | Log in to Reply

      Sorry, but #28571 is not active discussion. I described some problems there (with major one related to overwriting localization files) 2 months ago and several users added the same observations. This should be resolved before first beta and not several days before official release.

      And in #28577 I tried to raise the same questions as on Polyglots and other tickets, because it is the only active i18n ticket. Second comment is not ticket hijacking, I asked how to change language name for language installer and still no reply.

    • Stephen Edgar 12:12 am on August 12, 2014 Permalink | Log in to Reply

      I’m with you regarding the fact that there is no 4.0 /dev branch to translate strings yet. :(

      Not so much on the other parts. I believe @Nacin clearly laid out the goals and at the time asked “I’ll need a lot of help”. I would also say that with the vast majority of each of these goals included were links to the relevant tickets on Trac.

      I am subscribed to the i18n component on trac and receive an email for every single ticket and comment for the i18n component. I am participating and contributing to the i18n component where and when I can all the time and thus this also includes the 4.0 goals, be it adding patches (when I can), feedback or testing.

      In my opinion the place to contribute towards these “i18n 4.0 goals” is on WordPress Trac, in each individual ticket, for each bit of functionality and not have fragmented discussions here on Polyglots P2.

      • Mattias Tengblad 1:42 am on August 12, 2014 Permalink | Log in to Reply

        You are making the assumption that every translator is a developer.

        • Petya Raykovska 10:18 am on August 12, 2014 Permalink | Log in to Reply

          You don’t have to be a developer to follow trac and give feedback.

          • Ze Fontainhas 10:24 am on August 12, 2014 Permalink | Log in to Reply

            That is a whole other discussion. I’m with Mattias on this one: you probably do.

            • Stephen Edgar 4:07 am on August 13, 2014 Permalink

              @damst, @vanillalounge @petya Thanks, I think pretty much everything written in reply to my last reply are good points and should be worked on, developed, fleshed out further on how the Polyglots team wants to ‘contribute’ more than just translations to WordPress Core.

              Not all that long ago I would say the Accessibility team faced similar issues to what we are generally talking about here. Now they hold regular weekly IRC chats and post updates their P2 blog. The ‘Core’ team knows about this chat and I’ve seen @Helen swing by with specific requests during those IRC chat’s.

              So maybe this would be the obvious first steps for Polyglots, start idling in IRC more, having a weekly chat (or two for people’s time zone differences), and make ourselves more available and to more teams across the WordPress project. That can then be a starting point do discuss how the Polyglots team can best achieve it’s team goals.

            • Petya Raykovska 5:14 pm on August 12, 2014 Permalink

              Do you think we can come up with a process and change the need for people to go on trac and follow and participate in discussions?

              If these problems keep occuring perhaps we could figure out a way to interact with the core team and keep people on the Polyglots blog better informed?


              • Someone keeps an eye on trac i18n tickets (Stephen already does!) and gives a regular summery on the p2 on the developments if things need to be discussed
              • If the topic is tricky or conflicting, we schedule a chat with core team to better get what they’re thinking?
            • Mattias Tengblad 2:34 pm on August 12, 2014 Permalink

              Putting Stephens comment against Zé’s comment below.

              Stephen feel that everything should be done in trac (even the planing?)

              Zé is pointing out that trac tickets shouldn’t be used for general questions about functions being developed.

              I’m seeing contradictions in this workflow. What is this P2 for? Only access requests?

              In my mind trac should be used as it is, for the development specific parts, not the general discussions. Development specific chatter in a general translator discussion and vice verse makes things very hard to follow for each group (assuming they only have knowledge in their area).

              How many of the polyglotters are actually active on trac? Not many. To then just blindly refer to trac as many core members are doing is not constructive at all.

              Is it really that hard to setup a irc chat session between core and polyglot, for planning and reconnaissance of workflow for i18n and the language teams when things change?

              @petya of course not, but still, trac is development oriented and not everyone feels confident commenting on tickets. One should not dismiss that there are problems with this approach given that these discussions continue to occur.

            • Stephen Edgar 11:58 am on August 12, 2014 Permalink

              Ze, my original reply was a touch longer and I had originally included something similar to what I think you are alluding to here but was not happy with how I was articulating my point in this regard so I removed that section.

              Much of the i18n 4.0 goals are not just a thing for the “Polyglots” team, theoretically these would also involve the “Accessibility” and “UI” teams also and not forgetting the “Core” team.

              I agree that Trac can be a difficult place to navigate but be it code, design, functionality, testing or feedback this all needs to happen somewhere and fragmenting the discussion in multiple locations is not easy for anyone to keep on top of.

              Each feature or part thereof should be in a single location where it can be scoped, coded, tested, receive feedback and finally committed and in the WordPress world of things that place is Trac.

              Trac has become friendlier with recent improvements such as being able subscribe to a particular component or focus of interest but as you state this is a whole other discussion.

            • Ze Fontainhas 3:47 pm on August 12, 2014 Permalink

              I was originally replying to @petya, but ok. I still think you’re coming from a developer mindset, but i grant you that it is wholly subjective.

              Now, as to:

              …code, design, functionality, testing or feedback this all needs to happen somewhere and fragmenting the discussion in multiple locations is not easy for anyone to keep on top of.

              It certainly does, and Trac is certainly the place for that. What you’re not taking into account is that I’m referring to the moments prior to that: the goals were announced, not discussed, nor was there any previous hint that they might drop: they were suddenly there.

              Trac has become friendlier with recent improvements

              Indeed it has, but the issue is not one of features, but rather of population: It takes a significant psychological shift to start or participate in a discussion in Trac. It is no coincidence that practically every WordCamp has a talk or a hack day sessionon how to contribute on Trac, and not be afraid of the people there.

              Trac is a crucial component, as is moving the tickets along with constructive debate. It is not, however, a place for conceptual conversations around features.

              Developers tend to not see that distinction.

      • pavelevap 8:47 am on August 12, 2014 Permalink | Log in to Reply

        I also tried this way and made several tickets related to current localization, for example:


        So, reinstalling WordPress does not work for localized versions. Language files in wp-content/languages are automatically overwritten (yes, really, please be carefull when using Poedit because you can LOST your work in a sec), etc. Nobody interested in Trac…

        And comments:

        Nobody answered and I am not a developer.

        • Ze Fontainhas 10:23 am on August 12, 2014 Permalink | Log in to Reply

          Hold on. Only #28723 is silent. #28571 has an active discussion going on. As to the comments in #28577, they seem to simply be out of place, hijacking the thread. Fair is fair and your comment gives the wrong impression.

    • Gabriel Reguly 5:40 pm on August 11, 2014 Permalink | Log in to Reply

      Nice post Zé, but will it be effective?

      Because there are posts on other places that also got the 4.0 silence. :-(


      Maybe @helen could be sensibilized if we all politely show up at the next dev chat?

      • Andrew Nacin 3:51 am on August 14, 2014 Permalink | Log in to Reply

        I’m in charge of all i18n. There was some silence because I was busy cleaning up after the security release last week (which I spent a few weeks beforehand managing) and then there was a weekend.

    • Marko Heijnen 5:36 pm on August 11, 2014 Permalink | Log in to Reply

      We need communication between core and polyglots and not having core working on their issues and we do here only translations. The internationalisation teams should be more then that.

    • Xavier Borderie 4:59 pm on August 11, 2014 Permalink | Log in to Reply

      Thanks for this summary, Zé.

      A positive aside might be that, since the new system was announced in May as:

      • Not having per-language builds.
      • Not having language-separate “Update” buttons in the admin.
      • …in addition to being able to update the translation separately (which I have yet to witness working, but still)

      …it might be that being at 100% on D-Day is not as important for further releases (4.0 onward) as it was in the past.

      Still, knowing how all of this will work (or whether all the good stuffs announced in May are ready or not) is a must in this shortening timeframe.

      • Mattias Tengblad 5:29 pm on August 11, 2014 Permalink | Log in to Reply

        Disagree, being at 100% on release is still as important. I for one wouldn’t wont something else than 100% at release.

        • Xavier Borderie 5:58 pm on August 11, 2014 Permalink | Log in to Reply

          I agree with you 100% (ha!), I’m only stating this because not having day-0 full translation might be what the new system is being built to help us with (sorry for the weird sentence, hm).

          But really, for all we know, it could be something totally different — we haven’t had much news since the May announcements.

          • Mattias Tengblad 7:40 pm on August 11, 2014 Permalink | Log in to Reply

            Ah, ok. Get what you mean now.

          • Andrew Nacin 3:48 am on August 14, 2014 Permalink | Log in to Reply

            The system isn’t designed for being sub-100% when the release comes. While it does handle that situation, it is actually designed for these three use cases:

            1. You’ve finished translating WordPress 4.x with a week to spare. Congratulations! When it gets released, you don’t need to do a thing — if your translation is at 100%, it will automatically be packaged up for you. No more rushing to package things up.

            2. You noticed a pretty glaring typo the day after a major release. You can go ahead and fix it. The download packages and the language packs will automatically be updated (within a day or a week or a push of a button — this is up for discussion and it’s trivial to do any of these) and sites will automatically be updated to them.

            3. A security release needs to come out. You don’t need to do a thing at all. There will be no new strings, and the scripts will handle building your new 4.0.2 packages to be available for download.

            Essentially, the idea is to get you out of release management and allow you to spend your time translating and building your local communities.

            • Naoko Takano 5:59 am on August 14, 2014 Permalink

              I’m curious how packages that still require special modification are going to be handled (e.g. Japanese pkg still needs WP Multibyte Patch). Will the automated packaging process include /dist/ directory for these locales?

    • Remkus de Vries 3:16 pm on August 11, 2014 Permalink | Log in to Reply

      Having just returned from my holiday I am surprised to see we’re not one step further than three weeks ago with this … which makes me sad :(

  • Birgit Olzem 6:57 pm on June 18, 2014 Permalink |
    CoachBirgit • de.wordpress.org editor
    Tags: international sites, o2, , team blog   

    O2 for international sites. What do you think about? 

    At our first Contributor Day, at WordCamp Hamburg last monday, we have build a team to improve our germanophon community. In this procedere we´ve discussed how we can organize our team.

    One idea is to having an own P2 / O2 Make (public reading), where we can talk in german without flooding the existing make blogs here at w.org. Temporary we try to organize with a trello board. For small tasks it is a fine solution, but for general discussions to confusing.

    Here are some scenarios, that we had extracted:

    • XX.wordpress.org/make
    • make.wordpress.org/XX
    • make.wordpress.org/polyglots/XX
    • make.wordpress.org/community/XX

    What do you think? Is this an idea, you can deal with and use for your community?

    How is your workflow in your community?

    Thanks for your opinion and engagement to make the world a little better 😉

    • Caspar 2:42 pm on June 20, 2014 Permalink | Log in to Reply

      community management requires a lot more than just slapping a P2/O2 on it

      Got that. :)

    • Caspar 2:41 pm on June 20, 2014 Permalink | Log in to Reply

      @nacin Only because our Trello boards are flooded and we *really* need to create a solution within a matter of days rather than weeks:

      Would xx.wordpress.org/sth be available very soon? Or would it need to be discussed in general?

      We generally wouldn’t have a problem to use a self-hosted P2 for now if it wasn’t for the idea being so overwhelmingly intriguing that people logging into their w.org profiles could just post away in a xx.wordpress.org/sth solution.

      So, is it something we could help making available real soon? Or should we go with a self-hosted for now?

    • daveshine (David Decker) 11:07 am on June 19, 2014 Permalink | Log in to Reply

      I vote for a P2/O2 solution! It’s more native and dynamic and most “insiders” are already used to it because of the Make network on .org.

      Especially easy live comments, feeds and subscriptions make it more easy, and if there’s something more “long form” content to tell about, than the blog functionaly is also an advantage.

      Thanks, Dave :)

    • obstschale 10:31 am on June 19, 2014 Permalink | Log in to Reply

      I like xx.wordpress.org/sth. Ze’s arguments are good.

    • Andrew Nacin 11:19 pm on June 18, 2014 Permalink | Log in to Reply

      I definitely think we can do something on xx.wordpress.org (something I remember discussing previously).

      Alternatively: Let’s say your forums were bbPress 2.0 and everyone had them — would a single “meta” forum area be appropriate and sufficient?

      • Birgit Olzem 10:41 am on June 19, 2014 Permalink | Log in to Reply

        Yes, we´ve talked about this topic at Contributor Day in London last year.

        I think forums are not the best solution. For beeing consistently in organisation and communication for teams, I think we must use the infrastructure P2 / O2 Make-Blogs. New members could better get envolved with this scheme / model. They could orient oneself and easily find the way to communicate and contribute to.

        My thought goes a little bit forward: The user management for access the teams can driven by rosetta sites admins / editor resp. the locale reps. Every user with a .org profile could sign up over contact form.

        The main argument, why I think P2 / O2 is the best way: Notifications. It is much easier to get notified over a make blog, instead a topic in forums. And we can inform better about getting envolved with notes in sidebar and so on.

        All the arguments, why we use – for example – here for polyglots the same way to communicate with each other.

      • Ze Fontainhas 12:07 pm on June 19, 2014 Permalink | Log in to Reply

        Agree with P2/O2 being better than forums, for all the reasons listed by Birgit and David. That said, let’s keep in mind that make/polyglots is the home of translators and not necessarily a country/locale community. Granted, they often overlap, but not always. Speaking exclusively for pt_PT, we’d have no problem moving all discussions about translations to a .org hosted P2/O2, but would have a serious one moving the community debate there; community management requires a lot more than just slapping a P2/O2 on it, and neither does that discussion necessarily belong exclusively on make/polyglots, nor is it mature enough (yet) to implement. Baby steps.

        • daveshine (David Decker) 1:24 pm on June 19, 2014 Permalink | Log in to Reply

          As of my understanding it’s not about touching the Polyglots base here, it’s just offering the P2/O2 functionality to locale/country communities to power their blogs. Example: de.wordpress.org/blog/ would open as a P2/O2 — that would be awesome!

          This P2 here has to stay, absolutely!

          • Ze Fontainhas 1:43 pm on June 19, 2014 Permalink | Log in to Reply

            That was my point: community-operation-under-org is not defined or discussed, at this point (and keep in mind that “locale” isn’t necessarily “community”, see Belgium, Switzerland (1 community, n languages), or French (1 language, n communities). I am all for discussing it, but just not in this specific context, which has a clear, feasible and objective scope.

          • Birgit Olzem 1:39 pm on June 19, 2014 Permalink | Log in to Reply

            Sorry for objection @daveshine, don´t replace the standard blog for P2/O2!

            The blog is reserved for announcements and public articles. Not for discussion about organisation and improvements for locale communities.

            I prefer de.wordpress.org/make

            It´s a better consistence and namespacing

            „make“ in context doing great stuff for / with / in the locale community

            Organising contribution to other w.org projects für beginners in native language and so on.

        • Remkus de Vries 12:30 pm on June 19, 2014 Permalink | Log in to Reply

          Agreed 100%.

        • Torsten Landsiedel 7:44 am on June 20, 2014 Permalink | Log in to Reply

          This is not about having central place to discuss all things community, it is about adopting the idea of the make-blogs to locales. (At least for me.)

          de.wordpress.org/translation -> discussions about German translations
          de.wordpress.org/supporting -> discussions about supporting in the German forums
          de.wordpress.org/core -> discussions about German/translation related core patches
          etc. etc.

          This could be a place to prepare contributions in German and to discuss things which don’t have to flood international P2s.

          We don’t want to use the name “make” or make the make-blogs obsolete. It is just a step between, like we do now (with a wp.com blog) with translation here: http://teamwpde.wordpress.com/

          Or would this be an act of isolation again?

          • Birgit Olzem 11:11 am on June 20, 2014 Permalink | Log in to Reply

            @zodiac1978: I think, it don´t need more than one P2. The locale specific topics – in native language for german speaking – could separated with categories and colour tags.

            The big picture, why I want to discuss it here, is to make this native speaking P2s available for all people, who has a w.org login.

            I´ve talked with @samuelsidler some days ago and he meant, that we could use our community site wpde.org for this case.

            But I think, that option is likely an isolated application. We´re endeavored to desestablish this gap.

            @vanillalounge you´ve criticized this same gap in your keynote at #wchh14

            Please correct me, if my thoughts going into a wrong direction.

            I seem to remember, that at #wceu last year it was a topic, to bring the communities together. So I think, using the w.org infrastructure is the best way – because we all use the same CI / CD for the project.

            For us in Germany it is one mouseclick away to setup an own P2, but is this the best way for working together as a big worldwide community?

            The second argument. If we set up an own P2, so who is the Gatekeeper? If we use w.org infrastructure, so there can the respective user for the international sites step into this role, too. It is easier to maintain and respects the trademark policies.

            My 2cts and reflects my personal opinion. 😉

          • Ze Fontainhas 9:35 am on June 20, 2014 Permalink | Log in to Reply

            That looks like a lot of buckets :) It seems to me that discussing things like support and core patches, even if specific to a locale, could benefit all locales by being at the same place and in English, no? This may require some @samuelsidler input, so ping.

            • samuelsidler 4:21 am on July 9, 2014 Permalink

              Yeah, too many buckets. In general those things belong back on the English-speaking sites. Only locale-specific things should be on the locale sites.

    • Ze Fontainhas 9:20 pm on June 18, 2014 Permalink | Log in to Reply

      xx.wordpress.org/something is what makes sense to me, in which “something” could be either “team”, “discuss” or any variation of that. “make” already has a specific connotation I guess

    • daveshine (David Decker) 7:13 pm on June 18, 2014 Permalink | Log in to Reply

      For “speaking URLs” I like “make.wordpress.org/XX” the best, otherwise also “XX.wordpress.org/make” makes sense. The other 2 are already too long in my opinion.

  • Remkus de Vries 8:41 am on May 9, 2014 Permalink |
    DeFries • nl.wordpress.org editor • fy.wordpress.org editor
    Tags: automatic updates,   

    Hi @nacin

    I just saw the bbPress translations being updated while updating to WordPress 3.9.1 which made me very happy. When I then updated a multi-site instance to 3.9.1 (with also bbPress activated in the network) there were no updates of the bbPress language files.

    Any idea why I would have two different outcomes?

    • Marko Heijnen 7:08 pm on May 9, 2014 Permalink | Log in to Reply

      I saw the same. I also seeing the issue that it was downloading the dev version and not the 2.5.x one.

      • Stephen Edgar 10:47 am on May 10, 2014 Permalink | Log in to Reply

        Boom! This is awesome, I hadn’t noticed this and have just now been playing :)

        I had an en_US (default) multisite test setup and switched it to en_AU and I got the translations for Akismet, bbPress & BuddyPress

        So multisite worked for me and not for @DeFries

        After close inspection of the headers in the bbPress .po file I believe the translations are via GlotPress’ bbPress 2.5.x tag though @markoheijnen got the /dev translations.

        No doubt this will need more testing as running bbPress /trunk I’d expect to get the /dev translations (even if they are only partially translated )

        Massive thanks @nacin and please thank anyone else involved we are not aware of :)

        If there is a Trac ticket to track this let me know and I’ll test the daylights out of all the permutations and combinations :)

        @vanillalounge Automatic Translations Updates #FTW https://make.wordpress.org/core/2013/09/24/automatic-core-updates/

        p.s. This is one of the primary reasons I created the en_AU translations to make sure we have bbPress and BuddyPress deliver automatic translations.

        • Remkus de Vries 11:48 am on May 10, 2014 Permalink | Log in to Reply

          Indeed, major props to anyone involved in getting these updates working. REALLY happy with it and I trust these bugs will be ironed out. Someday 😉

    • Ze Fontainhas 8:47 am on May 9, 2014 Permalink | Log in to Reply

      Not sure I get it. Why would a WordPress update change bbPress’ language files? Remember that before bbPress releases a new version, you can always export those from Translate and update bbPress. Or am I seeing this wrong?

  • Kenan Dervisevic 9:47 am on April 6, 2014 Permalink |
    kenan3008 • bs.wordpress.org editor
    Tags: , profiles,   

    In case you haven’t noticed, WordPress.org profile redesign is up. People can now get badges for their contributions. Here is an example for polyglots https://profiles.wordpress.org/vanillalounge/.
    @vanillalounge I assume that you have access to the list of people currently contributing in make/polyglots. Could you please send it to someone in meta (probably Ian Dunn), so that we can get those shiny new badges? 😀 Thanks

    • Jen Mylo 10:32 pm on April 7, 2014 Permalink | Log in to Reply

      Slow down, cowboys! :)

      The “new design” is not really up. A portion of it in testing mode is up. We are not done with the design, nor with the backend code to add contributors and activities.

      • We are NOT implementing gamification. We’ll be using the icons to show affiliations with contributor teams. There’s no point system or different levels or anything like that.
      • Translators are not even in the test pool yet because we don’t have the backend done yet. I asked Ze and Yoav about how to get that info and it’s not in a state yet to be able to just pull it in, so we’re working on figuring out how to get it centralized on .org (not on a third-party site, even if Ze does run it). You see it on Ze and a couple of other people’s profile because I needed at least a couple of people to have the icon just to test the icon design. It’s all manual right now. When we finish and do an official launch of the profiles, we’ll include the roadmap and any areas where folks can help with building tools to bring in data.

      Thanks for your patience!

    • egalego 9:09 pm on April 6, 2014 Permalink | Log in to Reply

      I don’t see any badges on my profile
      and old validators , no longer active?
      Galician eg I am currently only active

    • Ian Dunn 3:09 pm on April 6, 2014 Permalink | Log in to Reply

      I think @jenmylo (or a volunteer she appointed) is the person maintaining the team lists right now, but maybe we should set it up so that team leads/reps can do it themselves?

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

      That’s probably a question for @samuelsidler or @nacin. I’m not sure from where and how the polyglots’ data is being pulled from, although if http://wpcentral.io/internationalization/ can pull it from somewhere (Rosetta, I assume) then the profile can do that too. Gentlemen?

      • samuelsidler 4:21 pm on April 6, 2014 Permalink | Log in to Reply

        A lot of the data for the badges is currently manually entered. That needs to change; it needs to be automated.

        It’s an open question which data we should use for each team. That’s something you should talk about as a team and then we (the meta team) need to work to implement that.

        Should validators get the badge? Or anyone who’s translated a string? Or?

        It’ll be a bit before an automated method is implemented, but knowing what data should be used is something that can be answered now.

        • Kenan Dervisevic 6:21 pm on April 6, 2014 Permalink | Log in to Reply

          If you are already implementing a gamification technique on profiles, I think that everyone should be credited, no matter the amount of work she/he did. How do you treat those who have reported a bug or submitted a patch, but don’t have commit access to the core? They should be properly rewarded too. Maybe we should try to separate these into different categories, and appoint different badges for both the validators and translators?

          • samuelsidler 1:24 am on April 7, 2014 Permalink | Log in to Reply

            I’m not arguing with you either way. :) I think it’s a discussion you as a team need to have and come up with whatever guidelines you want. :)

        • Gabriel Reguly 8:08 pm on April 10, 2014 Permalink | Log in to Reply

          Hi Samuel,

          I am reaching out the Brazilian translation team and will report once we hace some consensus about criteria for validators/translators.

    • OC2PS 2:12 pm on April 6, 2014 Permalink | Log in to Reply

      Hmm…I don’t see any badges on my profile https://profiles.wordpress.org/sooskriszta/ though I am a validator in the Translate project.

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

      There is a list of translators here http://wpcentral.io/internationalization/
      The code behind it is now in a patch here https://meta.trac.wordpress.org/ticket/340

      Not sure if this helps directly or maybe @markoheijnen can do a firendly dump of that data including the wp.org usernames for @iandunn

  • Eka Y Saputra 5:23 am on March 4, 2014 Permalink |
    ekajogja • id.wordpress.org editor • jv.wordpress.org editor
    Tags: , ,   

    It seems that id.wordpress.org has been abandoned. Last release was 3.5.1 (last year).
    Sent message using the contact form but it seems the admin email no longer exist, got a failure daemon.

    @Admins, pls verify if ID localization team is still there. I need to be able to do some commits on the site.


  • Mattias Tengblad 2:59 pm on January 28, 2014 Permalink |
    DaMsT • sv.wordpress.org editor
    Tags: , , , ,   

    Several projects are in need of updates 

    To summarize a number of requests that have not received the love they deserve, all related to the creation of projects in GlotPress.

    WordPress 3.8.x – The WordPress project needs a 3.8.x sub-project, should have been created when 3.8 was released, we’re @ 3.8.1 now.

    bbPress 2.5.x – Three follow up versions has been released since 2.5 (3 months old). What does /trunk give us, 2.6 dev or 2.5.x?

    BuddyPress 1.8.x, 1.9.x – The BuddyPress projects are desperately behind. We’re @ 1.9.1!

    How are we to know what the trunk projects gives us when it’s such a disarray? All these projects has been requested multiple times by different people. Do we really have to nag every time new projects need to be created?

    What happened to the discussed planning for polyglots? Are we going anywhere at all?

    Ping @vanillalounge

    • Stephen Edgar 2:49 am on March 20, 2014 Permalink | Log in to Reply

    • Mattias Tengblad 2:34 pm on March 11, 2014 Permalink | Log in to Reply

      This is becoming ridicules…

      Almost 4 months and nothing.

    • Mattias Tengblad 4:32 pm on February 1, 2014 Permalink | Log in to Reply

      Who, and why was this request marked as resolved?

      • Ze Fontainhas 4:52 pm on February 1, 2014 Permalink | Log in to Reply

        Me, given @nacin‘s feedback. You can always set it back to unresolved (which you have).

        • Mattias Tengblad 5:14 pm on February 1, 2014 Permalink | Log in to Reply

          Since how things progresses (poorly) on polyglots and given that this is NOT yet resolved, there is absolutely no reason to mark this as resolved. Once again, where is the communication?

          Also still not answered/ignored:

          What happened to the discussed planning for polyglots? Are we going anywhere at all?

          • Ze Fontainhas 6:08 pm on February 1, 2014 Permalink | Log in to Reply

            there is absolutely no reason to mark this as resolved

            Hence the fact that you can change it back to “Unresolved”

            What happened to the discussed planning for polyglots?

            Let’s schedule a chat then. I’ll start a new thread.

            Also, it would probably be a good thing if you could post a version of this post in English. It think most of us here can relate.

    • Stefano Aglietti 8:42 am on January 29, 2014 Permalink | Log in to Reply

      It’s since polyglots platform is born that quite at every release I ask to have the platform updated and every time i got the promise in future will be. Since now nothing happened, every time we are asking for branch and I REALLY can’t understand why after 3.8 string freeze the relative brache didn’t appear. It’s an hystorically habit to think to WP project more from a english centric point of view cause large parte of sites use it in english but this lack of care for polyglots it’s first an uncare for the hundreds of people that belive in WP and spend theyr time to make it available ofr his country people.

      Looks like Nacins is the one that always make the new brach (or I’m wrong?) Maybe it’s time to delegate to someone else cause he’s a lead developer and i thought he has very busy days.

      Maybe postponing for a week or two the nex release an do sone love to make the necessary automatic stuff to have the polyglot platform always up to date easily it’s not something that sound so bad.

      • Andrew Nacin 9:03 am on January 29, 2014 Permalink | Log in to Reply

        Guys, chill. Please. The “Development” branch is 3.8. It is frozen. There are no string changes being pushed to it from trunk right now. After the initial point release, the next steps are to create the new branch, do a mass export and import of the current strings to populate this branch, and re-start string harvesting. We’ve been doing this pretty much the same way for years now. Heck, I’m actually following Nikolay’s own instructions in doing so. Why this is done is for a number of reasons:

        • A lot of locales are building versions in the time between the major release and first minor release, and moving around branches can disrupt that process and make it more difficult for those translators.
        • A lot of strings sometimes quickly change early in a cycle. Not all of these are necessarily intended, and a lot of them will change very quickly. I don’t want to give you guys extra work for strings that will disappear in a week. Only after a few weeks of “alpha” does it make sense to release strings. I feel very bad about giving you extra work.
        • It gives all of you a much-needed break.

        3.8.1 was released late last week, and a lot of locales have now acted on 3.8.1, so I’ll be doing the steps I’ve described above this week. We’ll continue to do it this way until GlotPress gains any kind of cross-project string syncing or branching.

        I will update both BuddyPress and bbPress this week as well.

        In the meantime, I have renamed “Development” to “3.8.x” so everyone is clear what the source of the strings are. Sorry for the confusion there.

        • Xavier Borderie 4:30 pm on February 11, 2014 Permalink | Log in to Reply

          Hey Nacin,

          Thanks a lot for taking the time to explain this all, and make the necessary changes to the WP project!

          That being said, the BuddyPress and bbPress projects still a few versions, which confuses translator who which to work on currently-stable versions rather than on the Dev version. BP is 3 versions behing, bbP 2 versions behind.

          Thanks for doing that magic of yours :)

    • daveshine (David Decker) 12:07 am on January 29, 2014 Permalink | Log in to Reply

      I fully agree :)

      Just below your post the same topic… why not discuss there?
      (It’s quite annoying to have a lot of topics/ posts double or tripled here within a few posts – happens quite often from my feeling…)

    • Stephen Edgar 10:04 pm on January 28, 2014 Permalink | Log in to Reply

      FYI: bbPress & BuddyPress /dev branches are the /trunk branches for each of the relevant projects (currently bbPress 2.6 and BuddyPress 2.0)

    • OC2PS 3:30 pm on January 28, 2014 Permalink | Log in to Reply

      Are translations pulled from the development/trunk to branches/releases?

      bbPress is is 100% translated in Hungarian in Development, but 0% for 2.4.x

    • Remkus de Vries 3:19 pm on January 28, 2014 Permalink | Log in to Reply

      I agree. This needs to be better. I can do some of it, like @vanillalounge, but I believe @nacin has to do some foo as well..

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