- Language variants: we can officially install language variants (formal, informal) from core: https://twitter.com/glueckpress/status/620866636384309249
- All TE of locales with language variants, please write a request on make/polyglots for the option to be added for your locale. Requests should include a slug (like `formal`), the english and native name of a variant.
- Let’s document the different language variant usecases we have now, @alvarogois, @dimadin @gluekpress, could you describe your particular usecase and how you have handled things prior to this?
- A quick reminder you can translate 4.3 strings in the development project now. The teams page shows the progress of locales on the 4.3 dev branch. This, as mentioned last week, will also give you the opportunity to test translations if you have the beta tester plugin running in your install
- Themes and Plugins are coming to the repo (https://make.wordpress.org/polyglots/2015/07/14/translating-themes-and-plugins/), minimal requirements for TE to be added as per project validators:
- Description including projects and locales they’re taking care of
- Slack name (unless limited by a technical issue)
- Other means of communication – email, twitter or other social account
Plugins and themes who do not want dotorg translations (language packs from translate.wordpress.org) can “opt-out.” The way for them to use their own translations, instead of ones from translate.wordpress.org is to… do nothing. Or, to keep doing what they’re currently doing. Translations that are shipped with themes/plugins take priority to language packs. WordPress will use them first and not download the language pack.
- We’d love the accessibility team’s input on these requirements – Taco to pint Rian for her opinion
- The process for plugin/theme authors to request external validators for their plugins/themes to be added is described in https://make.wordpress.org/polyglots/handbook/rosetta/theme-plugin-directories/#requesting-new-translation-editors
- Handbook updates: In august Petya will organise a handbook sprint for all handbook pages that have been reported to have issues. To help this process along, you can either report issues (slack or make/polyglots blog) or if you want to get involved more, request to be added as an editor to the handbook. The translation sprint will have tasks outlined for everyone who wants to join in to claim and work on.
- Polyglots team volunteers – with a lot more people joining the polyglots community, we need all the help we can get to help people with locale requests, questions, new validators orientation, documentation. If you’d be interested in helping out with any of the tasks below, please raise your hand in the comments:
- Answering people’s requests on the polyglots P2
- Doing locale research for new locale requests – includes checking the request on the p2 and communicating with the person requesting the new locale, ensuring the ISO-3 codes are correct, adding information about how many people speak the language, double-checking plural forms, creating a ticket on the GlotPress track with all the information needed to add a new locale. (You will be trained by Petya)
- Monitoring feature requests/bug reports from polyglots and filing those as issues on the meta track