We want to translate wordpress into Urdu language.
Recent Updates Page 2 Toggle Comment Threads | Keyboard Shortcuts
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.
Have a great weekend, everyone!
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.
- Plugins and Hacks: https://ja.forums.wordpress.org/forum/5
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?
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
See you on Slack!
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.
- 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
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:
And the bot will send notifications if new strings are available for translation:
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.
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.
- 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
- 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”.
- 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
As always, feel free to add anything that’s missing, comment or suggest things for this week’s agenda.
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.
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.
Hey, please update https://make.wordpress.org/polyglots/handbook/translating/packaging-localized-wordpress/#release%c2%a0revisions with the revision number for 4.1.1
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/
I recently have been added as a validator. Can i update the rosetta site ? or post on blog ?
Edit: WordPress 4.1.1 has been released. Packages are currently build every
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%
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.1to release your package you only have to change the version in
- If you’re using
tags/4.1you have to create a new tag for 4.1.1 first. It’s just a copy of
tags/4.1and the version change to
- If you have
branches/4.1, but no
tags/4.1.1the build will use
- If you have custom changes on i18n.svn.wordpress.org and you are using