Proposal: When langpack is created, always send the new updates on the the project translation (even if below 95%)

Welcome to the official blog of the translator team for the WordPress open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. project. This is where we discuss all things related to translating WordPress. Follow our progress for general updates, status reports, and debates.

We’d love for you to help out!

Translate WordPress

You can help translate WordPress to your language by logging in to the translation platform with your WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ account and suggesting translations (more details).

Want to help in managing and validating translations? Get in touch with the existing language team and follow the glossaries & style guides if the team has them.

Don’t see your language? You can request support for it.

Weekly Meetings

We have meetings every week on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. in polyglots (the schedule is on the sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. of this page). You are also welcome to ask questions on the same channel at any time!

Posting here

In order to post to this site, you will need to log in with your wordpress.org account. Your first post may take a while to show up, as it is moderated. Please follow our tag policy when posting.

#polyglots

This is a fragmented proposal of “Delete project’s language pack when below specific percentage”.

We had feedback from the following users, and that helped to create this new proposal: @fierevere, @tobifjellner, @wolly, @nao, @ocean90, @knutsp, @yordansoares, @casiepa, and @swissspidy.

Description: If the pack has been created for the project and it goes below 95%, we can’t update the language pack again until it reaches 95% again, so the proposal is always updating it in this case.

Goal: Being able to fix stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. typos and having the most updated version of the translation on the already created pack.

Dominik Schilling 7:31 am on April 6, 2020

We can give this a test for sure.
I think we can also lower the threshold to 90% and then disable the threshold check for all plugins/themes which have at least one active language pack. The checks are done per 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/.
tobifjellner (Tor-Bjorn Fjellner) 8:07 am on April 6, 2020

I think we can also lower the threshold to 90% and then disable the threshold check for all plugins/themes which have at least one active language pack.

I like that. If an existing language pack contains stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. with errors, then we’ll always be able to fix it quickly without being forced to first reach the threshold again.
Naoko Takano 5:58 am on April 8, 2020

+1 to both proposals (additional deployDeploy Launching code from a local development environment to the production web server, so that it's available to visitors., 90% threshold) too.
Javier Esteban 6:38 am on April 8, 2020

I like both proposals too and fully agree with them.
Pascal Birchler 12:48 pm on April 8, 2020

+1 from me; though I’d also argue that we should give a lower threshold a try, e.g. 50%. There’s no harm in that.
Dominik Schilling 5:53 pm on April 14, 2020

The changes have been deployedDeploy Launching code from a local development environment to the production web server, so that it's available to visitors. a few minutes ago, see https://meta.trac.wordpress.org/changeset/9721.
- Pedro Mendonça 1:18 pm on April 15, 2020
  
  This is an important change in years.
  It should be documented.
  I agree with Pascal, this will keep providing poor language packs for long time abandoned projects. A minimum threshold is useful to avoid it.

Translate WordPress

Weekly Meetings

Posting here

Share this: