Translate WordPress

Recent Updates Page 2 Toggle Comment Threads | Keyboard Shortcuts

  • مصطفي سادات 7:13 am on March 17, 2015 Permalink |
    msadat • ps.wordpress.org editor
    Tags: , ,   

    Can i please request Pashto Language to be added to all the active translations projects for WordPress such as BuddyPress, WordPress for Android etc…

    Locale: Pashto
    WP Local: ps
    GlotPress: ps

    I would like to contribute to each of these projects, currently its only added to WordPress, Rosetta and Akismet projects.

    M Sadat

  • مصطفي سادات 7:01 am on March 17, 2015 Permalink |
    msadat • ps.wordpress.org editor
    Tags: , , ,   

    I have completed the translation of the following language:
    Locale: Pashto
    WP Local: ps
    GlotPress: ps
    Web: https://ps.wordpress.org/

    Can i please get an admin access to WP Rossetta portal as the current page has too many translation errors, i have tried to contact the current admin but i haven’t got any response back. currently i do have validator privileges on that portal but that does not allow me to edit any of the contents.

    Your help in this regard would be extremely appreciated.

    M Sadat

    • Dominik Schilling (ocean90) 12:41 pm on March 18, 2015 Permalink | Log in to Reply

      It looks like @sajadsafi is still active. Which admin have you tried to contact?

      • مصطفي سادات 10:16 pm on March 18, 2015 Permalink | Log in to Reply

        @Dominik Schilling (ocean90)

        That’s the one i was also trying to contact but not getting any response.
        I need to admin or similar privileges on the Rossetta Pashto page in order to update the contents as well as correct all the current translation mistakes.

    • سجادالله صافی 9:33 pm on March 18, 2015 Permalink | Log in to Reply

      hey Mr @msadat i added you in Validators list and you know that also
      now what you want ????

      • مصطفي سادات 2:06 am on March 19, 2015 Permalink | Log in to Reply

        @sajadsafi @ocean90
        I have requested admin privileges on the Pashto Rossetta page so that i can update the page contents as well as correct all the spelling and grammatical mistakes in the translations.
        Nothing to be taken personal here, we are here to contribute and work for Pashto language, if someone is not active or not know how to work then they should allow others to take over and use their capabilities while they can and take advantage of their time.
        This is not a personal page to keep the admin privileges locked down to individual user.
        Hope you understand and take appropriate action accordingly.
        I have spent good couple of months on finishing the Core WP and Themes translation and i am currently working on Plugin translations.

    • سجادالله صافی 9:48 pm on March 19, 2015 Permalink | Log in to Reply

      wordpress doesn’t give admin privileges to any person
      i’m also a author in that site i cant help more than this i made you author of this page
      if you work on this site
      but i’m also complete 50% of this project i don’t know what you want
      and my all contents spelling and grammatical is correct

  • Japh 4:00 am on March 12, 2015 Permalink |
    japh • en-au.wordpress.org editor

    Polyglots Asia/Pacific Meeting Time Change Announcement 

    Hello Polyglots in the Asia/Pacific region!

    We’ve found that the current meeting time isn’t working very well. Only a handful of people, at best, seem to be able to attend. So we’re moving the time back 2 hours, which seems like a better fit.

    The new time is 04:00 UTC on Thursday, every week. So next week’s meeting will be at 2015-03-19T04:00:00+00:00. (This makes it within daylight hours for the vast majority of those affected.)

    If you have legitimate concerns about the new time, please comment on this post so we can all discuss it.

    Hopefully this works better for everyone!

  • Petya Raykovska 9:47 am on March 11, 2015 Permalink |
    petya • bg.wordpress.org editor  

    Agenda for the polyglots chat on March 11th, March 12th 

    The agenda for today’s Polyglots chat is quite short, anyone is welcome to suggest items for it in the comments:

    • Locale stats/updates
    • Tech stats / updates
    • Discussing a new time for the Asia / Pacific chat (I will also be staying up till that one to discuss new scheduling with the people who show up)
    • Let’s discuss who’d like to step up and help the team keep track of things, we need more people to be active in moving things forward
    • Open discussion

    The Wednesday Polyglots chat starts at 11 am UTC on Slack. The Thursday polyglots chat will be at 02am UTC.

  • Petya Raykovska 9:19 am on March 11, 2015 Permalink |
    petya • bg.wordpress.org editor

    Notes from the Polyglots chat on March 4th 

    Hey dear polyglots,

    These are the notes from the Polyglots chat on March 4th. Logs are here: https://wordpress.slack.com/archives/polyglots/p1425466807000093

    Locale stats

    Worked with @ocean90 during the last two weeks to catch up with requests from the P2 https://make.wordpress.org/polyglots/?resolved=unresolved
    Translate WordPress
    Making WordPress Speak Your Language

    We are adding locales for Algerian Arabic, Romansch, Dzongkha & Kabyle. Hopefully will be in this week.

    We had a very early update on the plans for 4.2 by the release lead this morning, @drew reached out to talk about how they plan to do the string freeze for 4.2. The release is still about 7 weeks away, maybe more, but the core team is keen for things to run smoother for polyglots this time. They’re planning a “soft freeze” at Beta 4 with everything except the About page and a hard freeze at RC1 that will hopefully include the About page strings which, as you know, are what we usually wait till the last minute for.

    The current state of translations is on the teams page: https://make.wordpress.org/polyglots/teams/, not much movement since

    Tech stats

    • @ocean90 is working on the new Rosetta roles and badges. There is some code written to collect download stats for language packs.
    • @deconf helped with the Handbook, creating the Roles and Capabilities page

    This will be changed soon when new roles and capabilities come along.

    A reminder that everyone is welcome to step up and contribute to the Polyglots handbook: https://make.wordpress.org/polyglots/handbook/. Everyone that likes to help can get access to edit, just let us know in the comments.


    Results from the poll are up:

    Poll results overview
    Poll comments and detailed responses

    We’re moving forward with this. The goal is to have something up and running and then iterate if we have to.

    3905 people will have the translators badge, 322 users will get the the translation editor badge

    Next polyglots chats are on March 11th, 11am UTC, March 12th, 02.00am UTC.


    P.S. As the polyglots meeting for Asia/Pacific hasn’t seen much activity lately, could I please ask active Polyglots in those time zones to suggest alternative times for it or just share their thoughts on how we can help to encourage more people to show up?

    Shin has obviously been busy recently and that is totally understandable as we are all doing volunteer work here and priorities often shift, so if anyone wants to step up and take over the Asia / Pacific meeting it would be really beneficial for everyone on that side of the world.

    I will also add that to the agenda for this week’s chat, but comments are welcome here too.

  • krakmh 4:56 pm on March 8, 2015 Permalink |

    We want to translate wordpress into Urdu language.

  • Petya Raykovska 5:59 pm on March 6, 2015 Permalink |
    petya • bg.wordpress.org editor
    Tags: Documentation, Security, , WhitePaper,   

    Translating the WordPress Security White Paper 

    Hey lovely people,

    The WordPress Security White Paper has been in the works for some time now, but got officially introduced recently.

    The project is open for Pull Requests for translating it on GitHub for anyone interested and already has a pull request for Portuguese.

    The white paper is an analysis and explanation of the WordPress core software development and its related security processes, as well as an examination of the inherent security built directly into the software. It will obviously be highly beneficial for every WordPress business and can be used in evaluating WordPress as a cms. It is also a “best practices guide” for developers.

    The text in the white paper (not including the WordPress logo or trademark) is licensed under CC0 1.0 Universal (CC0 1.0) Public Domain Dedication. You can copy, modify, distribute and perform the work, even for commercial purposes, all without asking permission.

    If we could join forces and help translate it into all languages WordPress is available in, it would be amazing and highly beneficial for the growing global community.

    WordPress Security White Paper | The Project on GitHub

    Have a great weekend, everyone!

  • Naoko Takano 6:28 am on March 5, 2015 Permalink |
    Nao • ja.wordpress.org editor
    Tags: ,   

    Plugin forums excluded from "view all topics" and "no replies" 

    Our forum moderator @gatespace noticed that none of the topics from our Plugins and Hacks forums are showing up under “view all topics” and “no replies” views.

    We looked around and this seems to be the case for the Spanish forums too. Our guess is that the forums with ID = 5 are excluded from those two views, since the English forums treat the Plugins forums somewhat differently.

    Could we get the plugins related topics back, so they won’t be overlooked?

  • Petya Raykovska 10:44 am on March 4, 2015 Permalink |
    petya • bg.wordpress.org editor  

    Agenda for the Polyglots chat for March 4 

    Dear Polyglots,

    Here’s the agenda for today’s Polyglots chat:

    • Locale stats
    • Tech stats
    • First update about WordPress 4.2
    • New pages in the Handbook and what’s left there
    • Badges – poll results, next steps
    • Open discussion

    This week’s Polyglots chats are on March 4, Wednesdays at 11:00 UTC and March 5, Thursdays at 2:00 UTC

    See you on Slack!


  • Petya Raykovska 10:16 am on February 25, 2015 Permalink |
    petya • bg.wordpress.org editor

    Agenda for the Polyglots chat for Feb 25 

    Happy Wednesday!

    Time for the weekly chat agenda, about an hour to the EU chat, so feel free to join us in #Polyglots on Slack for today’s discussion.

    Short agenda

    • Locale stats after the 4.1.1 release
    • Tech stats / updates
    • Theme Directory Theme is in and ready to translate
    • New kids on the block – there are more new projects added to Translate.WordPress.org that we can start to work on:
      • Debug Bar plugin
      • User switcher
      • Theme Check
  • Dominik Schilling (ocean90) 10:09 am on February 25, 2015 Permalink |
    ocean90 • de.wordpress.org editor
    Tags: , slack   

    Slack: Introducing WordPress Translate bot 

    If you haven’t heard of Slack yet you should go ahead and join the WordPress team on Slack and then look for the #Polyglots channel.

    The #Polyglots channel on Slack is where we have our weekly chats and where you can ask questions and look for help with translations. To log into Slack, all you need is your WordPress.org username and to follow the instructions here: Chat.WordPress.org

    If you are a Translation Editor (validator) for a locale, it is highly recommended that you join the channel.

    New: WordPress Translate bot

    The slack channel now has a bot “WordPress Translate” which informs about auto-generated release packages and language packs:

    A new language pack was built.

    A new language pack was built.

    A new release package was built.

    A new release package was built.

    And the bot will send notifications if new strings are available for translation:

    New strings were imported to translate.wordpress.org

    New strings were imported to translate.wordpress.org

  • Petya Raykovska 9:46 pm on February 24, 2015 Permalink |
    petya • bg.wordpress.org editor
    Tags: badges,   

    Polyglots Team Badges 

    Dear Polyglots,

    We’ve discussed Polyglots badges for a while now during weekly chats. As we want to move things forward, we need to make some decisions.


    The current suggestion is that Translation Contributors (translators) and Translation Editors (validators) get a separate badge.

    In the weeks and months to come with the expectation for more and more projects in Translate.WordPress.org, we will need to find mechanisms to onboard new Translation Contributors faster and integrate them better into the existing teams.

    If badges help this process along, I believe we should try to keep the barrier for getting a translation badge low.

    At the same time Translation Editors are dedicating a lot of time and effort to keep translations consistent, they’re actively involved in the Polyglots team and put a lot more time into validating translation suggestions and generally taking care of a locale.

    This is the reason behind the two separate badges for Translation Contributors and Translation Editors.

    Things to consider

    1. We need a simple automated principle for rewarding a contributor with a badge, manually adding badges will require resources the team doesn’t have. A lot of teams are doing badges manually now for a lack of a better option, but we have a way to reward automatically and it would be great if we could take advantage of that.

    2. Current badges don’t have an expiration date for any of the existing teams.

    What we need to decide

    1. How many approved strings should a contributor have to receive the Translation Contributor badge?

    2. Do contributor badges need to expire and what would the principle be

    Please fill out this two question poll and help us make a decision.

    Earlier today Sergey suggested we only have one badge for Polyglots for Translation Editors. If any of you is strongly in favour of this suggestion, please comment below.



    • Krzysztof Trynkiewicz (Sukces Strony) 10:18 pm on February 24, 2015 Permalink | Log in to Reply

      I’d like to share my thoughts on badges expiration.
      Badges should not expire, but users should be able to collect a new badge each year. This way, previous work is glorified, but there’s an incentive to continue working and one can judge if a contributor is in a legacy hall of fame or currently ivolved in the project.
      Also, it would be great if we could achieve levels based on # of strings translated for a particular language or even have a current list of all time and last 365 days top translators (once again: for each language separately).
      So, basically, gamification.

    • Stephen Edgar 1:47 am on February 26, 2015 Permalink | Log in to Reply

      I’m on record already that if a Translation Contributor contributes a single translation then give them a badge :)

      Currently none of the teams are adding badges in any way, only .org “admins” can add users to the BuddyPress groups, if your part of a team and want the badge that goes along with it you’ll need to hunt down an “admin” and request you be added to said group.

      My other thoughts are within the survey results and all anonymous 😛

  • Andrew Nacin 8:50 pm on February 24, 2015 Permalink |

    Thought it might be fitting to post this as today marks five years since @ocean90‘s first patch to WordPress. As has been obvious to some of you, I have stepped back from i18n in the past few months, especially after 4.1’s release and as WordCamp Europe, WordCamp SF, the community summit, and Slack have empowered so many of you. I am stretched across a lot of projects, and Dominik very willingly stepped up to take on a lot of responsibility for improving Rosetta, core language packs, and related projects. He’s a highly respected WP core developer, he’s previously helped me on a number of i18n projects, and he’s slid into this role with ease. It’s also time for the technical point of contact to be a polyglot again. :-)

    @stephdau has also been instrumental for the massive project to translate plugins and themes (including language packs, localized plugin/theme directories, and the like). Also, you may have noticed a lot of coordination across these initiatives now happens in a #meta-i18n channel on Slack.

    While I haven’t gone anywhere and I’m still helping a bit behind the scenes, please consider @ocean90 the new @nacin and the primary point of contact core/dotorg i18n and the like!

  • Petya Raykovska 1:19 pm on February 24, 2015 Permalink |
    petya • bg.wordpress.org editor

    Notes from the Polyglots chat on Wed, Feb 18th 

    • WordPress 4.1.1 is coming and you should make sure your locale is prepared.
    • Check if wp/dev, wp/dev/admin and wp/dev/admin/network are at 100%
    • Update version in readme.html – This is only for locales which have /dist directory on i18n.svn.wordpress.org
      •  If you have custom changes on i18n.svn.wordpress.org and you are using branches/4.1 to release your package you only have to change the version in readme.html.
      • If you’re using tags/4.1 you have to create a new tag for 4.1.1 first. It’s just a copy of tags/4.1 and the change to readme.html.
      • If you have tags/4.1 and branches/4.1, but no tags/4.1.1 the build will use branches/4.1.
        This will affect ar, bs_BA, cy, de_DE, de_CH, en_CA, eo, es_PE, eu, fi, fr_FR, he_IL, it_IT, nb_NO, pt_BR, pt_PT, ro_RO, sv_SE, th, and tr_TR (the list is a bit old, will check it later again.)

    Please check your own locale and adjust it per above.

    • Let’s try and come up with a solution for the broken /languages/xx pages
    • Petya will write a post and mention the validators for locales that have a short way to go to be fully translated
    • Role permissions for projects – upload Dominik’s PDF
    • Renaming of the roles: Translation Editors and Translation Contributor

    @ocean90 has suggested a way to handle permissions for translate.wordpress.org

    • Take a look at: glotpress-permissions
    • This gives a possible suggestion to https://meta.trac.wordpress.org/ticket/741 and https://meta.trac.wordpress.org/ticket/519

    As per Ze’s suggestion we will rename “translators” and “validators” to “Translation contributors” and “Translation editors”.

    Polyglots Badges:

    • Suggestion is that we have two badges for Polyglots: One for Translation Editors and one for TranslationContributors.
    • Translation Editor is everyone who has earned access to approve translation suggestions
    • Translation contributor is everyone who has ever suggested a string to a locale and had that string approved by a translation editror
    • There is a difference of opinions about how many strings a contributor needs to have had approved to get a badge.
    • Petya to create a poll so we can vote on how many approved strings a translation contributor needs to have to get the badge

    Next polyglots chats are on Wednesday, Feb 25th, 11am UTC and Thursday, Feb 26th, 2am UTC

    As always, feel free to add anything that’s missing, comment or suggest things for this week’s agenda.



    • Sergey Biryukov 1:36 pm on February 24, 2015 Permalink | Log in to Reply

      I had some more thoughts on badges after the chat :)

      If we want to mirror the WP Core approach to badges, seems like it should be a single badge for validators (editors). Occasional translation contributors are already mentioned on the About page for each release, that should work as an incentive to attract new contributors.

      The badge means a consistent long-term participation to me, and that’s what validators do.

      Could we add a “Single badge for validators/editors” option to the poll?

      • Petya Raykovska 1:43 pm on February 24, 2015 Permalink | Log in to Reply

        I don’t think we want to mirror the WP Core badges. I wouldn’t want to do that at all. I would much rather mirror the Community badge approach or the speakers badge approach. Once you are a speaker at a WordCamp, you get a badge.

        There are people on this team who have contributed translations for years without being validators. The opposite counts too.

        So if we take on the “only one badge” approach, once we give someone validator rights, they get a badge, even though they might not have translated much and their locale might stay stuck for years.

        If we go for the one badge approach for “long term contribution” we need to figure out a way to measure “long term contribution”. Any suggestions how to do that besides just give a badge to someone with a particular user role?

        • Sergey Biryukov 10:46 am on February 25, 2015 Permalink | Log in to Reply

          You’re right, the WP Core approach wouldn’t be ideal here, and the WordCamp speakers approach would fit better.

          I wasn’t familiar with the Community badge approach, so I didn’t think of it that way.

          Thanks for the clarification :)

  • jonasltu 10:01 pm on February 23, 2015 Permalink |
    jonasltu • lt.wordpress.org editor
    Tags: ,   

    I’d like to request Lithuanian WordPress Forums:

    (1) URL: https://lt.forums.wordpress.org/
    (2) Forums title: WordPress forumai
    (3) First forum title: “Problemos ir sprendimai” Description: “Klausk ir tau bus atsakyta”

    Neither @pokeraitis nor me has permission to commit, but we have #4 & #5 files from this list https://codex.wordpress.org/International_WordPress_Forums and bbPress is translated on LT locale.

    Please let me know how should we proceed further.


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