Notes from the Polyglots chat on July 22

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 https://make.wordpress.org/polyglots/teams/ stats

Releases: 151 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 https://make.wordpress.org/polyglots/teams/. 55 locales up to date. 3 locales behind by minor versions. 7 locales behind by one major version. 15locales behind more than one major version. 56 locales have a site but never released. 15 locales don᾿t have a site.

Translations: 151 locales. 10 locales at 100%. 44 locales have more than 95%. 7 locales have more than 90%. 21 locales have more than 50%. 55 locales have less than 50%.

We have several new locales and new translation editorsTranslation Editor Translation editors can approve translations for projects. The GTE (General Translation Editor) and LM (Locale Manager) roles can add new users with the "Project Translation Editor" role that can approve translations for specific projects. There are two different Translation Editor roles: General Translation Editor and Project Translation Editor and processes are in place to add even more translation editors to the Armenian and Uzbek teams.

The Development project for 4.3 is already available for translation.

Weekly #metai18n meeting recap for Polyglots

Notes from the meta team chat (encouraging everyone that’s not following the channel and is interested in more than translating to join, weekly chats on Tue, 11am UTC).

Highlights from this week

  • Italian forums are online (win!)
  • Themes are being imported, all should be on translate.wordpress.orgtranslate.wordpress.org The platform for contributing to the translation of WordPress core, themes and plugins. by the end of the week
  • Sorting and prioritizing projects is high 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. team’s list for dev (see next point of the agenda)
  • @ocean90 started testing 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 WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party imports with selected plugins

Translation Project Sorting Ideas

@samuelsidler posted some ideas about sorting projects once themes and plugins get imported and the meta team needs our feedback. Ideas include:

  • Prioritizing by popularity: Projects could be organized by how popular they are, that is, how many users and/or downloads they have.
  • Prioritizing by fewest stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. remaining: If a project is almost complete – e.g., just a few strings away – it can be considered higher priority.
  • Prioritize by permissions: Show projects you have permissions for first.
  • “Hide” fully translated projects
  • Starring or Favoriting: Giving translators the ability to “favorite” a project and have it raise to the top. A new “tab” for “Favorites” that could be the default if a translator has favorites. Use a user’s favourites from the plugin and theme directories.
  • Sort by waiting: Translation editors should be able to see which projects have waiting strings so they can approve them. Within this view, we should probably prioritize projects based on some of the ideas above.
  • Improved search: Translators should be able to search by author name (theme or plugin) and see a list of their projects, for example.

More ideas from the Polyglost team:

  • Some polyglots expressed concern about using plugin/theme repoWordPress Localization Repository The WordPress Localization Repository at https://i18n.svn.wordpress.org/ is a Subversion repository where official WordPress translations are maintained. See Working with the Translation Repository for details. Favourites for translations
  • There was a suggestion for a page for Favourites from the repos and a separate one for Installation Favourites
  • We discussed use cases for TE and Translators in terms of sorting and default views, most people weren’t keen on hiding projects that are 100% translated.

WordPress 4.3 – soft freezeSoft freeze See String freeze. A soft string freeze or "soft freeze" is announced when all the strings of an upcoming WordPress release are frozen, except for the strings of the About page. update and release dates

  • RC1 coming on July 29 together with the soft freeze
  • Discussed some open issues on HTMLHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites. in strings that couldn’t make it into 4.3
  • There was a mutual agreement to keep bugging @ocean90 for those
  • We’re waiting on the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team to give us the heads up for the date of the hard freezeHard freeze See String freeze. A hard string freeze or a hard freeze is announced when all the strings of the upcoming release are frozen including the strings of the About page. A hard freeze is the final string freeze before a release. (aka all strings get frozen including the About page)
  • Release of 4.3 is still scheduled for August 18th

Open discussion

  • There was a request to post the agenda for the chat on Tuesday. If it makes more sense to people I will try posting on Tuesday after the #metai18n meeting

 

 

#weekly-meeting-notes