Translate WordPress

Recent Updates Toggle Comment Threads | Keyboard Shortcuts

Naoko Takano 6:28 am on March 5, 2015 Permalink | Log in to leave a Comment
Nao • ja.wordpress.org editor
Tags: bug ( 20 ), forums ( 79 )
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?
Reply Cancel reply

You must be logged in to post a comment.
Petya Raykovska 10:44 am on March 4, 2015 Permalink | Log in to leave a Comment
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 | Log in to leave a Comment
petya • bg.wordpress.org editor
Tags: weekly meeting agenda ( 14 )
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
- Polyglots badges poll: http://petyaraykovska.polldaddy.com/s/polyglots-badges-survey
- Open discussion
Dominik Schilling (ocean90) 10:09 am on February 25, 2015 Permalink | Log in to leave a Comment
ocean90 • de.wordpress.org editor
Tags: announcement ( 28 ), 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 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

Nick Weisser, Stephen Edgar, Birgit Olzem, and 1 other are discussing. Toggle Comments
- Petya Raykovska 10:34 am on February 25, 2015 Permalink | Log in to Reply
  
  I love this so much Thanks a lot @ocean90! Would still be really cool to have notifications in GlotPress though.
- Birgit Olzem 10:58 am on February 25, 2015 Permalink | Log in to Reply
  
  Wow, that´s awesome
  
  Many thanks!
- Stephen Edgar 1:16 am on February 26, 2015 Permalink | Log in to Reply
  
  This is way cool, thanks @ocean90
- Nick Weisser 11:18 am on February 28, 2015 Permalink | Log in to Reply
  
  Awesome!
Petya Raykovska 9:46 pm on February 24, 2015 Permalink | Log in to leave a Comment
petya • bg.wordpress.org editor
Tags: badges, polyglots ( 11 )

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.

Overview

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.

Cheers!

Petya

Stephen Edgar, Dominik Schilling (ocean90), Mattias Tengblad, and 1 other are discussing. Toggle Comments
- 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.
  - Mattias Tengblad 9:14 am on February 25, 2015 Permalink | Log in to Reply
    
    Or maybe making it a bit simpler by having two sets o badges, one for active contributors and one for inactive (something like not active for the last year).
    
    IMO, game like point system is overkill.
  - Dominik Schilling (ocean90) 9:25 am on February 25, 2015 Permalink | Log in to Reply
    
    Gamification is something we definitively don’t want.
- 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
  - Stephen Edgar 1:56 am on February 26, 2015 Permalink | Log in to Reply
    
    Oh, ignore the “none of the teams” above, indeed some are automated
    See https://wordpress.slack.com/archives/polyglots/p1424863973001336
Andrew Nacin 8:50 pm on February 24, 2015 Permalink | Log in to leave a Comment
nacin
Tags: announcement ( 28 )

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!

Kazama, pavelevap, Caspar, and 3 others are discussing. Toggle Comments
- Krzysztof Trynkiewicz (Sukces Strony) 10:01 pm on February 24, 2015 Permalink | Log in to Reply
  
  Thanks for your involvement, Andrew!
- Stephane Daury (stephdau) 11:14 pm on February 24, 2015 Permalink | Log in to Reply
  
  Three cheers for @ocean90! It’s a pleasure to work with you, when I get to.
- Birgit Olzem 6:05 am on February 25, 2015 Permalink | Log in to Reply
  
  Hey Andy, nice to hear from you, you´re still alive I welcome the decision to pass on the scepter to @ocean90.
  
  The i18n / #polyglots project got a hughe shift in the last year. Many thanks to your contributions and engagement.
  
  Cheers to @stephdau and @ocean90
- Caspar 7:21 am on February 25, 2015 Permalink | Log in to Reply
  
  @nacin Thanks for all the dedicated help with i18n!
  @ocean90 Now we need to talk…
- pavelevap 9:42 am on February 25, 2015 Permalink | Log in to Reply
  
  I will miss you @nacin! OK, it is time to start bothering @ocean90!
- Kazama 4:22 pm on February 25, 2015 Permalink | Log in to Reply
  
  thank you @nacin, you always work like you didn’t sleep. we will miss you. Congrats to @ocean90
Petya Raykovska 1:19 pm on February 24, 2015 Permalink | Log in to leave a Comment
petya • bg.wordpress.org editor
Tags: weekly meeting notes ( 9 )
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.

Cheers,

Petya
Sergey Biryukov and Petya Raykovska are discussing. Toggle Comments
- 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 | Log in to leave a Comment
jonasltu • lt.wordpress.org editor
Tags: forums ( 78 ), request ( 708 )

Hi,
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.

Thanks!

Stephen Edgar is discussing. Toggle Comments
- Stephen Edgar 10:34 pm on February 23, 2015 Permalink | Log in to Reply
  
  New forums creation is on hold right now, see the attached link, and yes that is just over two years old now, we are getting close and I’ll have some more news on this in this weeks weekly chat
  
  See https://make.wordpress.org/polyglots/2013/01/18/hi-could-you-include-galician-language-into-rosetta/#comment-108003
svd02 4:18 pm on February 23, 2015 Permalink | Log in to leave a Comment
svd02
Tags: requests ( 4 )

I already translated more than 400 items for marathi language. I think nobody is there to do further action from wordpress as a moderator. shall i become moderator.

Petya Raykovska, svd02, and Dominik Schilling (ocean90) are discussing. Toggle Comments
- Dominik Schilling (ocean90) 5:58 pm on February 23, 2015 Permalink | Log in to Reply
  
  Hello @svd02,
  
  have you already tried to contact one of the validators? See https://make.wordpress.org/polyglots/teams/?locale=mr for an overview. There is also a contact form: https://mr.wordpress.org/contact/
- svd02 6:27 am on February 24, 2015 Permalink | Log in to Reply
  
  translated strings now goes upto 600. i send message to developerpaddy. waiting for reply. hope our moderator will show enthusiasum.
  - Petya Raykovska 10:26 am on February 25, 2015 Permalink | Log in to Reply
    
    Hello @svd02,
    
    Thank you for your efforts for Marathi.
    
    Every WordPress language is maintained on a volunteer basis by people who raised their hand to help. It helps to have a little patience with validators, as they are donating their time in the same way you are.
    
    The process for becoming a validator for an existing language currently involves you trying to contact the validators using the Contact form on the local site (for you that would be https://mr.wordpress.org/).
    
    If you get no answer, we can try to contact them and discuss their availability and the option for a new validator to join the team.
    
    Marathi has four validators – @yossarianc, @developerpaddy, @vinod-dalvi and @jaays.
    
    They should get notifications from the mention above and hopefully can help with either checking and approving the translations you suggested or adding you as a validator for Marathi.
    
    If none of them shows up here, I will contact them via email.
    
    Once again thank you for your time and effort, please be patient and use this blog to communicate the issue.
    
    Kind regards,
    Petya
Wacław Jacek 3:47 pm on February 22, 2015 Permalink | Log in to leave a Comment
waclawjacek • pl.wordpress.org editor

Hey, please update https://make.wordpress.org/polyglots/handbook/translating/packaging-localized-wordpress/#release%c2%a0revisions with the revision number for 4.1.1

Wacław Jacek and Dominik Schilling (ocean90) are discussing. Toggle Comments
- Dominik Schilling (ocean90) 4:02 pm on February 22, 2015 Permalink | Log in to Reply
  
  Done.
  - Wacław Jacek 4:24 pm on February 22, 2015 Permalink | Log in to Reply
    
    Thanks!
Kirtan Gajjar 4:39 am on February 19, 2015 Permalink | Log in to leave a Comment
kirtan95 • gu.wordpress.org validator
Tags: bug ( 19 )

There is an issue of multiple strings at – https://translate.wordpress.org/projects/wp/dev/cc

check out “Gujarati” language. It shows a total of 503 translations instead of 487.

During translation, i observed that when i did some particular thing, it just made two original strings. I thought it would be a temporary bug, but in actual it created two different strings. Any idea why?

Also, check this one out – http://postimg.org/image/d09749vcl/

Kirtan Gajjar, Dominik Schilling (ocean90), Chevindu, and 1 other are discussing. Toggle Comments
- Kazama 6:23 am on February 19, 2015 Permalink | Log in to Reply
  
  the status of most strings are “waiting” if you are validator of that language, you need to approve it to change the status.
  - Kirtan Gajjar 9:00 am on February 19, 2015 Permalink | Log in to Reply
    
    I don’t think you got my point. You can see that there are multiple original strings, so that total strings are even more than original.
    - Kazama 10:14 am on February 19, 2015 Permalink | Log in to Reply
      
      since the status is not “approved” that strings still can be translated. One string may be translated by two or three person. That’s the reason why there are more strings than original amount.
- Chevindu 6:16 am on February 20, 2015 Permalink | Log in to Reply
  
  I came across the same situation. I thought it’s usual and I copy-pasted the translation.
- Dominik Schilling (ocean90) 12:22 pm on February 20, 2015 Permalink | Log in to Reply
  
  @kirtan95
  Not sure about your math, but I can see this: 32 translated, 0 fuzzy, 455 untranslated and 470 waiting string.
  32 + 455 is 487, so you don’t have more original strings as other languages. The 470 waiting string can indeed include mulitple suggestions for one string. You as a validator have to decide which one is correct.
  - Kirtan Gajjar 1:21 pm on February 20, 2015 Permalink | Log in to Reply
    
    Oh! Sorry, my bad, i just added 32 with 470 “waiting” strings. I got it, and maybe i accidently suggested multiple translation of same string. Thanks for the clarification
Kirtan Gajjar 4:23 am on February 19, 2015 Permalink | Log in to leave a Comment
kirtan95 • gu.wordpress.org validator
Tags: Help ( 8 )

I recently have been added as a validator. Can i update the rosetta site ? or post on blog ?

Kirtan Gajjar and Alin Marcu are discussing. Toggle Comments
- Alin Marcu 6:07 am on February 19, 2015 Permalink | Log in to Reply
  
  Validators can approve strings in GlotPress but don’t receive additional privileges on Rosetta. In Rosetta a validator is the equivalent of a standard WordPress subscriber.
- Kirtan Gajjar 8:52 am on February 19, 2015 Permalink | Log in to Reply
  
  Oh! Okay.
Dominik Schilling (ocean90) 10:49 am on February 18, 2015 Permalink | Log in to leave a Comment
ocean90 • de.wordpress.org editor
Tags: 4.1 ( 4 ), announcement ( 28 )
Prepare your locale for 4.1.1 – Update: WordPress 4.1.1 has been released
Edit: WordPress 4.1.1 has been released. Packages are currently build every ~~hour~~ 6 hours.

WordPress 4.1.1 will be released in the next 24 hours. In order to benefit from the automated release process it could be possible that you have to prepare your locale first.

Translations must be at 100%

(This includes wp/dev, wp/dev/admin and wp/dev/admin/network.)
Currently 39 locales are at 100%, 10 locales are at 99%. Most of them don’t have translated the two new strings in 4.1.1, see String changes in WordPress 4.1.1. Please check also for existing waiting strings and clear them out, otherwise the build will be skipped.
(Also do not forget about the default themes and Akismet project.)

Update version in readme.html

(For these locales: 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.)
- 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 trunk/ or tags/4.1 and the version 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.
If you have any questions just comment here or ping me @ocean90 on Slack #polyglots.
Dominik Schilling (ocean90), Gwgan, Hugh, and 10 others are discussing. Toggle Comments
- Rami Yushuvaev 11:00 am on February 18, 2015 Permalink | Log in to Reply
  
  In hebrew (he_IL), I removed the wordpress version number from the README.TXT file. This way i don’t need to update the file in each new vesion.
  - Dominik Schilling (ocean90) 11:13 am on February 18, 2015 Permalink | Log in to Reply
    
    Works too, but then you should use branches/4.1 instead of tags/4.1 like you have currently.
  - Dominik Schilling (ocean90) 1:53 pm on February 22, 2015 Permalink | Log in to Reply
    
    @ramiy Would you like to change that?
- petskratt 11:03 am on February 18, 2015 Permalink | Log in to Reply
  
  Could it be possible to bring release requirement down for `et` and publish without `wp/dev/admin/network` ?
  
  As nobody seems interested in network version here it is bound to be dragging behind in future… which has currently resulted in also the main translation lagging behind couple of releases (and `et` has never reached the official multilingual installer if I’m correct).
  - Dominik Schilling (ocean90) 11:14 am on February 18, 2015 Permalink | Log in to Reply
    
    I can create a language pack for you, yes. But you still have to build a release package by yourself.
- Stefano Aglietti 11:08 am on February 18, 2015 Permalink | Log in to Reply
  
  it_IT ready for relase
- Nick Weisser 12:12 pm on February 18, 2015 Permalink | Log in to Reply
  
  de_CH ready for release, too.
- Birgit Olzem 12:19 pm on February 18, 2015 Permalink | Log in to Reply
  
  de_DE ready to go
- Petya Raykovska 3:36 pm on February 18, 2015 Permalink | Log in to Reply
  
  bg_BG is done too, had one waiting string in Admin.
- Mattias Tengblad 7:37 pm on February 18, 2015 Permalink | Log in to Reply
  
  sv_SE ready
- Rafa Poveda 9:42 pm on February 18, 2015 Permalink | Log in to Reply
  
  es_ES ready
- Victor J. Quesada 11:56 pm on February 18, 2015 Permalink | Log in to Reply
  
  gl_ES ready
  - Dominik Schilling (ocean90) 12:08 am on February 19, 2015 Permalink | Log in to Reply
    
    gl_ES can’t benefit of an autogenerated release package because there is no tags/4.1.1 and branches/4.1 includes a custom wp-admin/setup-config.php file (which is not needed?).
- Kazama 6:24 am on February 19, 2015 Permalink | Log in to Reply
  
  th was released
- Gwgan 2:00 pm on February 19, 2015 Permalink | Log in to Reply
  
  WordPress 4.1.1 cy has appeared on my WordPress websites but not as a download available at cy.wordpress.org. Do I need to take further action or will this appear within a short while?
  Thanks
  - Dominik Schilling (ocean90) 2:05 pm on February 19, 2015 Permalink | Log in to Reply
    
    You have to take further action, please read the “Update version in readme.html” section. tags/4.1.1 does not exists for cy.
    - Gwgan 12:58 pm on February 22, 2015 Permalink | Log in to Reply
      
      Is there an optimum set-up we should aim for? it_IT and de_DE have the following set-up:
      
      tags/new 4.1.1 folder/dist/readme.html, wp-config-sample.php
      trunk/dist/readme.html, wp-config-sample.php
      
      Is this what we’re aiming at? Thanks.
      - Dominik Schilling (ocean90) 1:04 pm on February 22, 2015 Permalink | Log in to Reply
        
        If you have translated both files, yes, that would be the right setup.
- Hugh 8:52 am on February 22, 2015 Permalink | Log in to Reply
  
  New here, Question: is there a way to get a feed of some kind of the locales that WP supports? I mean this is a shifting number/set, as various versions of WP evolve. So, I am wondering if there is a feed for the ones at 100%.
  - Dominik Schilling (ocean90) 1:02 pm on February 22, 2015 Permalink | Log in to Reply
    
    See the table on https://make.wordpress.org/polyglots/teams/.
Petya Raykovska 10:25 am on February 18, 2015 Permalink | Log in to leave a Comment
petya • bg.wordpress.org editor
Tags: polyglots meeting ( 14 ), weekly meeting agenda ( 13 )
Agenda for the Polyglots chats on Wed, 18 Feb & Thu, 19 Feb,
Dear Polyglots,

This week’s polyglots chats will be on Wed, 18 Feb, 11:00 UTC and Thu, 19 Feb, 02:00 UTC on the #Polyglots channel on Slack

Short agenda:
- Release date for 4.1.1 and how to make autorelease work by @ocean90
- Locale stats
- Tech stats
- Suggestion for more granular permissions for translate.wordpress.org
- Suggestion for Polyglots badges
- Spread the love: Speaking at local WordPress events about the importance of i18n & l10n
- Marko started a project dedicated to rebuilding the GlotPress Theme. Contributors needed.
- Open discussion
Cheers!
Petya
Yacine2953 10:16 pm on February 13, 2015 Permalink | Log in to leave a Comment
Yacine2953 • kab.wordpress.org editor
Tags: request ( 707 )

Hi! My name is Yacine
I would like to Request a New Locale (Kabyle).
Locale : kab,
Language native name :Taqbaylit,
Sub-domain : kab,
Site Title : Taqbaylit,
Site Description : WordPress s teqbaylit,
Admin Username : yacine2953,
Admin Email address : yacine2953-wp@yahoo.fr

Petya Raykovska is discussing. Toggle Comments
- Petya Raykovska 9:36 am on February 18, 2015 Permalink | Log in to Reply
  
  Hello @Yacine2953,
  
  Thank you for your request. Sorry for the late reply. Could you try and help us with defining the plural forms for Kabyle?
  
  Could you look at this document and see if there’s a language with the same plural form structure?
  
  Thanks in advance!
  Petya

	Nick Weisser on Slack: Introducing WordPress T…
	Stephen Edgar on Polyglots Team Badges
	Stephen Edgar on Polyglots Team Badges
	Stephen Edgar on Slack: Introducing WordPress T…
	Kazama on Thought it might be fitting to…

Translate WordPress

Don’t see your language?

Weekly Meetings

Posting here

Recent Updates Toggle Comment Threads | Keyboard Shortcuts

Naoko Takano 6:28 am on March 5, 2015 Permalink | Log in to leave a Comment Nao • ja.wordpress.org editor Tags: bug ( 20 ), forums ( 79 )

Reply Cancel reply

Petya Raykovska 10:44 am on March 4, 2015 Permalink | Log in to leave a Comment petya • bg.wordpress.org editor

Petya Raykovska 10:16 am on February 25, 2015 Permalink | Log in to leave a Comment petya • bg.wordpress.org editor Tags: weekly meeting agenda ( 14 )

Short agenda

Dominik Schilling (ocean90) 10:09 am on February 25, 2015 Permalink | Log in to leave a Comment ocean90 • de.wordpress.org editor Tags: announcement ( 28 ), slack

New: WordPress Translate bot

Petya Raykovska 10:34 am on February 25, 2015 Permalink | Log in to Reply

Birgit Olzem 10:58 am on February 25, 2015 Permalink | Log in to Reply

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

Nick Weisser 11:18 am on February 28, 2015 Permalink | Log in to Reply

Petya Raykovska 9:46 pm on February 24, 2015 Permalink | Log in to leave a Comment petya • bg.wordpress.org editor Tags: badges, polyglots ( 11 )

Overview

Things to consider

What we need to decide

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

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

Mattias Tengblad 9:14 am on February 25, 2015 Permalink | Log in to Reply

Dominik Schilling (ocean90) 9:25 am on February 25, 2015 Permalink | Log in to Reply

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

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

Andrew Nacin 8:50 pm on February 24, 2015 Permalink | Log in to leave a Comment nacin Tags: announcement ( 28 )

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

Stephane Daury (stephdau) 11:14 pm on February 24, 2015 Permalink | Log in to Reply

Birgit Olzem 6:05 am on February 25, 2015 Permalink | Log in to Reply

Caspar 7:21 am on February 25, 2015 Permalink | Log in to Reply

pavelevap 9:42 am on February 25, 2015 Permalink | Log in to Reply

Kazama 4:22 pm on February 25, 2015 Permalink | Log in to Reply

Petya Raykovska 1:19 pm on February 24, 2015 Permalink | Log in to leave a Comment petya • bg.wordpress.org editor Tags: weekly meeting notes ( 9 )

Polyglots Badges:

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

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

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

jonasltu 10:01 pm on February 23, 2015 Permalink | Log in to leave a Comment jonasltu • lt.wordpress.org editor Tags: forums ( 78 ), request ( 708 )

Stephen Edgar 10:34 pm on February 23, 2015 Permalink | Log in to Reply

svd02 4:18 pm on February 23, 2015 Permalink | Log in to leave a Comment svd02 Tags: requests ( 4 )

Dominik Schilling (ocean90) 5:58 pm on February 23, 2015 Permalink | Log in to Reply

svd02 6:27 am on February 24, 2015 Permalink | Log in to Reply

Petya Raykovska 10:26 am on February 25, 2015 Permalink | Log in to Reply

Wacław Jacek 3:47 pm on February 22, 2015 Permalink | Log in to leave a Comment waclawjacek • pl.wordpress.org editor

Dominik Schilling (ocean90) 4:02 pm on February 22, 2015 Permalink | Log in to Reply

Wacław Jacek 4:24 pm on February 22, 2015 Permalink | Log in to Reply

Kirtan Gajjar 4:39 am on February 19, 2015 Permalink | Log in to leave a Comment kirtan95 • gu.wordpress.org validator Tags: bug ( 19 )

Kazama 6:23 am on February 19, 2015 Permalink | Log in to Reply

Kirtan Gajjar 9:00 am on February 19, 2015 Permalink | Log in to Reply

Kazama 10:14 am on February 19, 2015 Permalink | Log in to Reply

Chevindu 6:16 am on February 20, 2015 Permalink | Log in to Reply

Dominik Schilling (ocean90) 12:22 pm on February 20, 2015 Permalink | Log in to Reply

Kirtan Gajjar 1:21 pm on February 20, 2015 Permalink | Log in to Reply

Kirtan Gajjar 4:23 am on February 19, 2015 Permalink | Log in to leave a Comment kirtan95 • gu.wordpress.org validator Tags: Help ( 8 )

Alin Marcu 6:07 am on February 19, 2015 Permalink | Log in to Reply

Kirtan Gajjar 8:52 am on February 19, 2015 Permalink | Log in to Reply

Dominik Schilling (ocean90) 10:49 am on February 18, 2015 Permalink | Log in to leave a Comment ocean90 • de.wordpress.org editor Tags: 4.1 ( 4 ), announcement ( 28 )

Translations must be at 100%

Update version in readme.html

Rami Yushuvaev 11:00 am on February 18, 2015 Permalink | Log in to Reply

Dominik Schilling (ocean90) 11:13 am on February 18, 2015 Permalink | Log in to Reply

Dominik Schilling (ocean90) 1:53 pm on February 22, 2015 Permalink | Log in to Reply

petskratt 11:03 am on February 18, 2015 Permalink | Log in to Reply

Dominik Schilling (ocean90) 11:14 am on February 18, 2015 Permalink | Log in to Reply

Stefano Aglietti 11:08 am on February 18, 2015 Permalink | Log in to Reply

Nick Weisser 12:12 pm on February 18, 2015 Permalink | Log in to Reply

Birgit Olzem 12:19 pm on February 18, 2015 Permalink | Log in to Reply

Petya Raykovska 3:36 pm on February 18, 2015 Permalink | Log in to Reply

Mattias Tengblad 7:37 pm on February 18, 2015 Permalink | Log in to Reply

Rafa Poveda 9:42 pm on February 18, 2015 Permalink | Log in to Reply

Victor J. Quesada 11:56 pm on February 18, 2015 Permalink | Log in to Reply

Dominik Schilling (ocean90) 12:08 am on February 19, 2015 Permalink | Log in to Reply

Kazama 6:24 am on February 19, 2015 Permalink | Log in to Reply

Gwgan 2:00 pm on February 19, 2015 Permalink | Log in to Reply

Dominik Schilling (ocean90) 2:05 pm on February 19, 2015 Permalink | Log in to Reply

Gwgan 12:58 pm on February 22, 2015 Permalink | Log in to Reply

Dominik Schilling (ocean90) 1:04 pm on February 22, 2015 Permalink | Log in to Reply

Hugh 8:52 am on February 22, 2015 Permalink | Log in to Reply

Dominik Schilling (ocean90) 1:02 pm on February 22, 2015 Permalink | Log in to Reply

Naoko Takano 6:28 am on March 5, 2015 Permalink | Log in to leave a Comment
Nao • ja.wordpress.org editor
Tags: bug ( 20 ), forums ( 79 )

Petya Raykovska 10:44 am on March 4, 2015 Permalink | Log in to leave a Comment
petya • bg.wordpress.org editor

Petya Raykovska 10:16 am on February 25, 2015 Permalink | Log in to leave a Comment
petya • bg.wordpress.org editor
Tags: weekly meeting agenda ( 14 )

Dominik Schilling (ocean90) 10:09 am on February 25, 2015 Permalink | Log in to leave a Comment
ocean90 • de.wordpress.org editor
Tags: announcement ( 28 ), slack

Petya Raykovska 9:46 pm on February 24, 2015 Permalink | Log in to leave a Comment
petya • bg.wordpress.org editor
Tags: badges, polyglots ( 11 )

Andrew Nacin 8:50 pm on February 24, 2015 Permalink | Log in to leave a Comment
nacin
Tags: announcement ( 28 )

Petya Raykovska 1:19 pm on February 24, 2015 Permalink | Log in to leave a Comment
petya • bg.wordpress.org editor
Tags: weekly meeting notes ( 9 )

jonasltu 10:01 pm on February 23, 2015 Permalink | Log in to leave a Comment
jonasltu • lt.wordpress.org editor
Tags: forums ( 78 ), request ( 708 )

svd02 4:18 pm on February 23, 2015 Permalink | Log in to leave a Comment
svd02
Tags: requests ( 4 )

Wacław Jacek 3:47 pm on February 22, 2015 Permalink | Log in to leave a Comment
waclawjacek • pl.wordpress.org editor

Kirtan Gajjar 4:39 am on February 19, 2015 Permalink | Log in to leave a Comment
kirtan95 • gu.wordpress.org validator
Tags: bug ( 19 )

Kirtan Gajjar 4:23 am on February 19, 2015 Permalink | Log in to leave a Comment
kirtan95 • gu.wordpress.org validator
Tags: Help ( 8 )

Dominik Schilling (ocean90) 10:49 am on February 18, 2015 Permalink | Log in to leave a Comment
ocean90 • de.wordpress.org editor
Tags: 4.1 ( 4 ), announcement ( 28 )

Petya Raykovska 10:25 am on February 18, 2015 Permalink | Log in to leave a Comment
petya • bg.wordpress.org editor
Tags: polyglots meeting ( 14 ), weekly meeting agenda ( 13 )

Yacine2953 10:16 pm on February 13, 2015 Permalink | Log in to leave a Comment
Yacine2953 • kab.wordpress.org editor
Tags: request ( 707 )