46 locales are up to date.
5 locales are 100% translated but not yet released for 4.2.2:
- ID is still at 4.1.1, @ekajogja can we help you in any way to release 4.2.2?
- Welsh, Polish, Catalan and Chinese are still at 4.2 or 4.2.1 – @gwgan, @jimmyxu, @xavivars, @waclawjacek, @eclare Can we help in any way to release to 4.2.2?
Localized Plugins and Themes directories are here
@dd32 posted earlier today about Plugin and Theme repositories made available on local sites.
- Theme Directory is available at /themes
- The Plugins directory is also available at /plugins/
- Both already have existing projects on translate.wordpress.org available for localizing
- Deploy after translation should be requested the same you would do all other rosetta translations.
- @chantal: Is there any timeframe when it will be possible to translate plugins/themes thru GlotPress?
- @dd32: No hard timeline, most of the groundwork is there for plugins and it’s just waiting for the floodgates to open after more testing, me or @ocean90 will be working on the Themes-in-Glotpress in the next few weeks I expect, not sure how long it’ll take to get that finalised but now that these directories are localised, we kind of want to finish the job
Also from @dd32 about what plugins are going to be available for translations first:
“The “official” plugins in https://translate.wordpress.org/projects/wp-plugins is the start-list, we’ll expand from there, but no definite what we’ll include first. I suspect we’d start with the most popular ones and work the way down the list, biggest impact first. We might also do some smaller plugins first to get the feeling for the process, work out any bugs.. so no, not sure yet”
- There was a brief discussion around localizing the plugin and theme handbooks and different approaches to that.
- @dd32: “We’d love to have translations of resources such as that. I personally don’t know of any effort to get that working yet though”
- The best solution would allow Translation Editors to easily get notified on changes in the documentation so that those could be applied to localised versions. This means there has to be a direct relation between the original documentation and all the local versions.
- According to @ocean90 GlotPress is not the way to go for Documentation
- @zodiac1978 shared a possible solution wp.com uses: “I am doing this for the support pages for wordpress.com. They use a plugin which send you an email for every change (with a revision diff view of the changes). Then we have to manually add these changes to our localised post/page. This could be one way. But much work …”
- Petya to post a separate post on the P2 to discuss this with more people and bring it to the attention of the metai18n team.
Polyglots at #wceu
- A lot of us will be at WordCamp Europe in Seville – raise your hand if you’re one.
- Let’s discuss a more formal gathering with an agenda for Contributor day, June 28
- Let’s discuss organising a global translation sprint around WordCamp Europe’s contributor day including polyglots who’re not in Seville
- Petya to post a separate discussion topic on make/polyglots about this
If anyone has anything to add to the notes, feel free to drop it in the comments.