Ready to get started?Download WordPress

Translate WordPress

Updates from September, 2014 Toggle Comment Threads | Keyboard Shortcuts

  • Chris Trynkiewicz 6:32 pm on September 13, 2014 Permalink | Log in to leave a Comment
    Tags: ,   

    We have a situation for pl_PL (Polish). It seems that for a couple of hours (around 1:30 to 3:30 GMT 12. Sept.) the translation files were messed up. If WP auto-downloaded them during this time, the main translation admin-pl_PL.po (and .mo) would have a few hundred bytes instead of kB. The admin-pl_PL.po was not possible to open. Also, the multisite translation files for 4.0 weren’t downloaded. It was a mess, resulting in half of the admin panel defaulting to English.

    After those 2 hours, the translation files seemed to refresh and WP installs that made updates later on were fine. The ones that dl-d the bugged files did not update them, however.

    We need someone ( @nacin @ocean90 ) to push an update. Probably just changing the update date in http://api.wordpress.org/translations/core/1.0/?version=4.0 should work.

    The maintainer of the pl_PL translation will confirm this below.

    • Andrew Nacin 9:44 pm on September 13, 2014 Permalink | Log in to Reply

      Is there a reason why a proper 4.0 package was never built for pl_PL? http://pl.wordpress.org/

      • eotob 10:51 pm on September 13, 2014 Permalink | Log in to Reply

        No, just the lack of time from the only maintainer. This is in regard to the auto-update which at this point is pulling stuff from GlotPress itself.
        Another case is, why did this occur in the first place, but less important.

      • eotob 11:03 pm on September 13, 2014 Permalink | Log in to Reply

        Okay, I see that an update has been pushed which fixed the problem. You can mark it as resolved. Thanks.

        Here is the COMPLETE content of admin-pl_PL.po if you’re into digging into it or for future reference, if the problem occurs again:

        1. Translation of Administration in Polish
        2. This file is distributed under the same license as the Administration package.

        msgid “”
        msgstr “”
        “PO-Revision-Date: 2014-09-11 20:16:43+0000\n”
        “MIME-Version: 1.0\n”
        “Content-Type: text/plain; charset=UTF-8\n”
        “Content-Transfer-Encoding: 8bit\n”
        “Plural-Forms: nplurals=3; plural=(n==1 ? 0 : n%10>=2 && n%10<=4 && (n%100=20) ? 1 : 2);\n”
        “X-Generator: GlotPress/0.1\n”
        “Project-Id-Version: Administration\n”

      • Wacław Jacek 11:44 pm on September 13, 2014 Permalink | Log in to Reply

        I wanted to release it earlier today but I wanted to make sure it would interfere with this issue in any way.

  • Sithu Thwin 8:30 am on September 5, 2014 Permalink | Log in to leave a Comment
    herzcthu • mya.wordpress.org editor
    Tags: , , , , ,   

    @nacin Is it possible to embed language specific fonts in core or in language pack?
    Most of the major OS included Myanmar(Burmese) script fonts now.(e.g Windows 8 and later version, OSX Lion and later, many Linux OS) But implementation is different between vendors and not reliable. No mobile OS support Myanmar script. I wish google web fonts for Burmese included in WordPress package. Currently google has early access fonts for Myanmar script. Here is the link http://www.google.com/fonts/earlyaccess
    And another thing is adding functionality for proper word breaking. https://github.com/andjc/jquery.mymr/ is a jquery library to use for Burmese Scripts wordbreaking, list markers etc. It is developed by one of Mozilla developers. Will it be possible to include in my_MM language pack?

    • Dominik Schilling (ocean90) 9:37 am on September 5, 2014 Permalink | Log in to Reply

      It’s not possible, yet. Currently a language pack contains only the translation files.

      But indeed, we want to improve the procedure to support this and various other localisation fixes, like the multibyte patch for the JA locale.

    • Andrew Nacin 9:53 pm on September 13, 2014 Permalink | Log in to Reply

      We can however include it directly in core. Similar to #19950. Could you create a ticket?

  • Andrew Nacin 4:19 pm on September 4, 2014 Permalink | Log in to leave a Comment
    Tags: , , ,   

    Instructions for 4.0, which will be released in the next 15-30 minutes:

    • The need to create a localized build through the Rosetta form is unchanged for 4.0. This will go away very soon, but we couldn’t get all the ducks in a row to make this go away for 4.0. I’m trying for 4.0.1. Thank you so much for your patience as we work to make the experience painless for all of you.
    • As usual, you will build your release off the 4.0 tag, which will exist soon. Since you’re building off of 4.0, you don’t need the revision number (HEAD is fine), but it’s 29485.
    • CHECK YOUR BUILD FIRST. Especially $wp_version in wp-includes/version.php.
    • If you have WPLANG defined in wp-config-sample.php, the build will be rejected. If you don’t translate this file and this file is thus an exact copy of the core file, you may delete it. Only mess with trunk / 4.0, not dist directories from 3.9 or earlier.
    • Thanks to your feedback, the language chooser will not show for a localized build. For the regular build, it will show. These languages are via the API at http://api.wordpress.org/translations/core/1.0/?version=4.0 and reflect any translations that are 100% for all three projects (wp/dev, wp/dev/admin, wp/dev/admin/network). Percent completion is checked periodically and language packs are then built.
    • (This is mainly for @pavelevap…) If you are not at 100% for all three projects, you may ask for me to manually trigger an incomplete language pack, for the purposes of being available in the language chooser. I’d rather not, though — this is API-driven and we can always get the language in there once you finish your translation.
    • Do not forget to 100% translate Akismet. There were no string changes in the default themes.

    If you have any questions, please leave a comment, and @ocean90 or I will address them. If there is an urgent issue, please ping me in #wordpress-polyglots or #wordpress-dev.

  • Andrew Nacin 11:34 pm on September 3, 2014 Permalink | Log in to leave a Comment
    Tags: , ,   

    You have about 14 hours to complete your translations for WordPress 4.0.

    I’ve added one last string, “Release Lead,” for use on the credits page. If you were at 100% for 4.0, don’t worry, you have a language pack built already, but it’d be nice if you could translate this.

    Please ensure you are 100% for wp/dev, wp/dev/admin, and wp/dev/admin/network. Currently 19 languages have done this (minus the new string).

    pl_PL, he_IL, my_MM, and eu (Basque) are all at 100% for wp/dev but are not at 100% for the administration projects. Another 30 languages are at 90% or higher for wp/dev — so close!

    WPLANG should be removed from wp-config-sample.php. If you have a custom wp-config-sample.php file in your SVN trunk/dist directory, please update it. See how German did it here.

    If you are translating via SVN please make sure you are importing each of your PO files into translate.wordpress.org, for language packs.

    More launch day instructions to follow. Thanks for your patience. If you have any specific questions you’d like me to answer, please include them below so I can be sure to cover them in my instructions.

  • Sithu Thwin 4:31 pm on September 3, 2014 Permalink | Log in to leave a Comment
    herzcthu • mya.wordpress.org editor
    Tags: , ,   

    I have few questions as a language validator
    1. Do I still need to make deploy request from rosetta ?
    2. How is the plan going with bbPress plugin instead separate install?
    3. How WordPress api work for 4.0? Is it automatic or manual? ( Because my language not listed in installation screen even if I’ve completed all translation.)
    4. How can I change locale site title? ( I would like to change from “ြမန်မာ | Burmese” to “မြန်မာ | Burmese” )

  • Stefano Aglietti 1:45 pm on September 3, 2014 Permalink | Log in to leave a Comment
    SteveAgl • it.wordpress.org editor  

    So we are 24 hour from the new release and no news about what have to be done or not, the files in SVN should be updated? package should be made? what about the origina idea to have everything in some way under glotpress? I undertsand devs are in rush for bugs tickets etc but one more time people that give theyr time to make WP in tons of languages are left alone with no info till the last minute or after it

    • Michael Beil 5:17 pm on September 3, 2014 Permalink | Log in to Reply

      It might help to read this post in core and this post in polyglots from @nacin. And here’s a recent post from @nacin regarding 4.0 RC1 and how translation is going.

      The following is taken from @glueckpress on this post.

      Have you read up on WordPress language packs in general? Also @otto42’s prep-work post might be worth reading. Quote:

      Eventually, WordPress.org will have a way to allow plugin/theme authors to upload translation files. Or, it will have a way to allow users to submit their translations to them via translate.wordpress.org. […] The auto-update system will automatically download these MO files into the /wp-content/languages directory. There will be plugins and themes subdirectories under that to hold these files.

      • Stefano Aglietti 7:29 am on September 4, 2014 Permalink | Log in to Reply

        I always read every news here and around codex web etc about language wpitaly.it translate and validate WP since 2005 we are one of the earlier translation team for WP. The Nacin post (the old one) have left some thing undefinied and open and after all this there wans’t any news about. Proposal ideas ecc are nice and ok, but ho much of the planned stuff where done? readmefile are still tobe updated manually and commit on SVN ecc. Anyway we are few hour far from the release, it’s a major release so people is used to not jump on it immediatly for update and new installa without testing etc so if the locale packages will be incomlete or have problems it’s not a drama. 4.0 adoption take longer than a maintenance release for compatibility test on existing sites, we will see.

  • Andrew Nacin 12:25 pm on August 27, 2014 Permalink | Log in to leave a Comment
    Tags: , ,   

    WordPress 4.0 RC is out.

    In a few hours I’ll be building new language packs for RC1 for any locale at 100% for the wp/dev project and all sub-projects (this includes the network admin). Each day as translations are completed, packs will be created or updated. We’ll work out some kinks over the next few days and hopefully have everything in order come September. Expect to hear more from me in the coming days and weeks as we begin a new journey. :-)

    @helen is targeting September 3 for release. The about page is done, help tabs are updated, and strings are frozen. You have one week to get everything in order, so good luck and happy translating!

  • Nashwan Doaqan 11:02 am on August 25, 2014 Permalink | Log in to leave a Comment
    alex-ye • ar.wordpress.org editor

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

  • Kazama 7:22 am on August 21, 2014 Permalink | Log in to leave a Comment
    kazama • th.wordpress.org editor  

    Just saw http://translate.wordpress.org/languages. I really love it, this is what I really want. :P

  • Andrew Nacin 4:00 am on August 14, 2014 Permalink | Log in to leave a Comment
    Tags: , ,   

    I’ve finally fixed a very broken translate.wordpress.org and pushed 4.0 to http://translate.wordpress.org/projects/wp/dev. There are ~85 new strings, which you can now begin translating. (It should probably go pretty quickly.)

    It’s safe to consider this a “string freeze” — with the exception of the about page, which will be finalized over the weekend.

  • Ze Fontainhas 3:07 pm on August 11, 2014 Permalink | Log in to leave a Comment
    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.

    • 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 :(

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

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

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

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

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

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

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

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

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

    • 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 9:57 am on August 7, 2014 Permalink | Log in to leave a Comment
    pavelevap • cs.wordpress.org editor  

    How will WordPress 4.0 language installation work? I probably did not understand it fully, so I am asking:

    1) Localized version will be ready several days after release of WordPress 4.0. Which language pack will receive new users in the meantime? Older (and complete) 3.9 language version?

    2) There will be any button, that localization is complete or there will be many different translations? I do not want to allow not finished localization for distribution.

    3) When I change some strings in GlotPress, all users will be automatically updated (every day)?

    There are only 2 week to WordPress 4.0 release and there is no discussion with translators how it should work. And also no detail information :-(

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


      Two weeks before a major release and this is not clear at all.

    • Stefano Aglietti 2:58 pm on August 7, 2014 Permalink | Log in to Reply

      +1 Nacin should start to give us info ASAP in Europe lot of people is on vacation this period translators too… and some planning is necessary!

    • Michael Beil 5:52 pm on August 7, 2014 Permalink | Log in to Reply

      I don’t know if y’all saw this, but there’s a whole discussion that @nacin posted that is dated May 21, 2014 going on over here: http://make.wordpress.org/polyglots/2014/05/22/internationalization-goals-for-wordpress-4-0

      This is connected to http://make.wordpress.org/core/2014/05/21/internationalization-goals-for-4-0/

    • pavelevap 7:17 pm on August 10, 2014 Permalink | Log in to Reply

      Problem is not only translation, but we should also try releasing and testing beta versions, discussing best workflow etc. Now there will be some process defined by developers and we will have to hurry to finish translation and not to discuss many other important things related to automatic language packs.

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

      1) Localized version will be ready several days after release of WordPress 4.0. Which language pack will receive new users in the meantime? Older (and complete) 3.9 language version?

      Some of this isn’t completely worked out yet — versions are a real pain to get “right” from both technical and UX standpoints. Essentially, yes, new users will receive the 3.9 version until the 4.0 is complete.

      2) There will be any button, that localization is complete or there will be many different translations? I do not want to allow not finished localization for distribution.

      If a language is 100% before release, then it will be immediately packaged upon core release. That’s all that needs to be done. Once 100% is hit post-release, a scheduled task will package these up. It will likely run once per day, except on or around release days when it’ll run as languages rush to finish up. This is all easily adjustable based on how things are written.

      3) When I change some strings in GlotPress, all users will be automatically updated (every day)?

      Yes, users will be automatically updated. Whether that’s every day, every week, or with the push of a button is up for discussion. I expect there will be a lot of tweaking in the coming months.

      • pavelevap 9:05 am on August 14, 2014 Permalink | Log in to Reply

        Thank you!

        Ad 2) OK and it is related to all subprojects? We have 100% for frontend, around 90% for backend (takes longer to translate all long help sentences) and a very little for multisite admin (10 %). So in this case there will be only frontend file distributed? It will be regression because there will be missing 90% of backend? And another use-case: I need to distribute language for 4.0 when it is 97% complete (new features translated, but About page with long sentences not yet). How can I do it? We really need a “button” to tell “Start distributing” to script. No need for building packages, but some human work is needed here…

        Ad 3) And what is checked from technical point of view? Date of latest string change in GlotPress? Comparing with date of latest language pack updates?

        • Andrew Nacin 5:23 am on August 15, 2014 Permalink | Log in to Reply

          2) As of right now, it needs to be 100% for all sub-projects (frontend, admin, network admin). But I suspect we’ll add a button. Thanks for the feedback.

          3) Yes, the date in the PO file headers are used and compared with the latest string change in GlotPress (across all sub-projects).

          • pavelevap 6:36 am on August 15, 2014 Permalink | Log in to Reply

            ad 2) Thank you, button would be really helpfull. Instead of packaging the whole localized version, there could be a simple checkbox for every MAJOR version (minor can work automatically). It is still great improvement for translators, only one checkbox per project (for WordPress it should combine all subprojetcs), no problem with handling minor versions, etc. Translators could check when they think it is done and distribution can start.

            ad 3) Nice, it would be fine to distribute typos corrections automatically. But when user change .po file (and modify it), then this date will be newer than GlotPress?

          • Kenan Dervisevic 10:43 am on August 15, 2014 Permalink | Log in to Reply

            @nacin What about readme and wp-config? How will that be handled?

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

    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 ;-)

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

    • 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

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

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

          Agreed 100%.

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

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

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

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

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

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

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

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

    • 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 :)

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

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

  • Naoko Takano 2:25 am on June 2, 2014 Permalink | Log in to leave a Comment
    Nao • ja.wordpress.org editor
    Tags: ,   

    Our forum volunteers noticed that the “hot topic” section of the Japanese forum top page is now filled with spammy tags.

    From bb-admin, I can see a bunch of posts from bozo users with such tags. The posts themselves are no longer appearing, but looks like the hot topic section is ignoring the bozo status.

    The same issue with other local forums, e.g. http://de.forums.wordpress.org and http://nl.forums.wordpress.org

  • Samuel Sidler 12:15 pm on May 25, 2014 Permalink | Log in to leave a Comment

    There’s been a lot of things happening recently. Here’s a quick recap:

    Your feedback on all of these posts is incredibly important. If you have thoughts on any of these topics, leave it on the respective post. Thanks for reading!

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