Notes from the Polyglots chat on July 15th

  • All TE of localesLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in with language variants, please write a request on make/polyglots for the option to be added for your localeLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in 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 stringsString A string is a translatable part of the software. A translation consists of a multitude of localized 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 betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. tester pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the Plugin Directory or can be cost-based plugin from a third-party running in your install
  • Themes and Plugins are coming to the repoWordPress Localization Repository The WordPress Localization Repository at is a Subversion repository where official WordPress translations are maintained. See Working with the Translation Repository for details. (, minimal requirements for TE to be added as per project validators:
    • Description including projects and locales they’re taking care of
    • SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at name (unless limited by a technical issue)
    • Other means of communication – email, twitter or other social account 
    • GravatarGravatar Is an acronym for Globally Recognized Avatar. It is the avatar system managed by, and used within the WordPress software.
  • Plugins and themes who do not want dotorg translations (language packs from can “opt-out.” The way for them to use their own translations, instead of ones from 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 accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). ( 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
  • 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 teamPolyglots Team Polyglots Team is a group of multilingual translators who work on translating plugins, themes, documentation, and front-facing marketing copy. 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 P2p2 "p2" is the name of the theme that blogs at use (and o2 is the accompanying plugin). When asked to post something "on the p2" by a member of the Polyglots team, that usually means you're asked to post on the team blog
    • 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 GlotPressGlotPress GlotPress is the translation management software that powers More information is available at 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 metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. track




#weekly-meeting-notes, #weekly-meetings