Categories
Core

Moving languages packs to WordPress.org

Recently an announcement was made that plugins could soon make use of Language Packs, the same way in which core and themes do. This makes it easier for users to obtain translations (they are downloaded along with the plugin), lets everyone translate in the same place (translate.wordpress.org) and lets all plugins share a translation memory.

With the new language pack system, you’ll be able to update/install any translation from your WordPress dashboard within the “Updates” screen:

updates-screen

Up until now, WooCommerce has had its own custom language pack system implemented in 2.2, with our translations being hosted on Transifex. We’re like to move this over to .org as soon as possible.

Starting today, we’ll no longer update the languages packages within the Transifex and the 2.4.8 WooCommerce release will no longer include our custom language pack downloader.

Our new translations are located here.

If you’re like to contribute to translation going forward, or if you are maintaining a translation already, it’s important you start doing this now on translate.wordpress.org. WordPress will only install translations that are complete, with all strings revised.

If you are a translation reviewer today at Transifex or would like to be a reviewer, please leave a comment (see example below) with your WordPress.org username and which language you would like to be reviewer.

pt_BR – @claudiosanches

 

If you would like to learn more about how translation works in the new system with GlotPress, see this post.

Thanks to all of our contributors 🙂

By Claudio Sanches

Developer on the WooCommerce team and member of the WordPress Brazilian community.

82 replies on “Moving languages packs to WordPress.org”

fi – @arhipaiva . Yes, I would like to continue to keep up the consistency and quality of the Finnish translation as I have done since 2012. A reviewer role, please. Another thing: there is no need for fi_FI translations as the correct suffix is fi (and not fi_FI)

Liked by 1 person

de_DE – @nachtigall
de – @nachtigall

OLD
====

Current situation at transifex (woocommerce) is:
* de_DE (German (Germany)) is the formal “Sie” variant of German
* de (German) is the informal “du” variant of German

For WordPress (beginning with 4.3) the situation is like:
* de_DE is the informal “du” variant of German (which is also shipped by default, whereas in WooCommerce the formal “Sie” variant is currently shipped by default)
* Then for the formal variant there is a de_DE_formal

NEW
====

I think for WooCommerce it should become the same way like WordPress. That is:
– old transifex de (https://www.transifex.com/woothemes/woocommerce/language/de/) becomes de_DE on new translate platform (https://translate.wordpress.org/projects/wp-plugins/woocommerce/dev/de/default)
– old transifex de_DE (https://www.transifex.com/woothemes/woocommerce/language/de_DE/) becomes de_DE_formal on new translate platform (https://translate.wordpress.org/projects/wp-plugins/woocommerce/dev/de/formal)

So the mapping at https://translate.wordpress.org/projects/wp-plugins/woocommerce/dev/ for German is wrong at the moment and needs to be fixed.

BTW, imho this is really a very breaking change (“WordPress will only install translations that are complete, with all strings revised”). I do not understand why this done as a minor version number. I would do this for 2.5 For German it is even worse, as webshops with formal language will now default to informal which is a very breaking change.

Like

BTW, imho this is really a very breaking change (“WordPress will only install translations that are complete, with all strings revised”). I do not understand why this done as a minor version number. I would do this for 2.5 For German it is even worse, as webshops with formal language will now default to informal which is a very breaking change.

Not our rules, are the WordPress rules for all translations (core, themes and plugins).
You will get used to it.

Like

Yeah the changes suggested by Jens are totally correct.

In my case it ist totally perfect that the informal version is the standard now because we are only using informal language.

On the other side I have to aggree with Jens that this should be communicated clearly to everyone that there will be a switch of the standard from formal to informal.

I think we should discuss two issues here:
1) The correct languages should be imported to the correct language repos to be consistent with the WordPress way of the German translation – we should set up everything like Jens suggested. But as far as I see everything is already correctly set up, isn’t it Jens?

IMPORTANT: My first review of the translation showed that not the full version of the current transifex-translations (including all strings awaiting review) were imported.

2) I agree with Jens: Shouldn’t we consider to wait for a major release update like 2.5 and announce foremost to the German users that now everything is translated the “standard” WordPress way and that from now on the formal and informal translations are swapped?

Like

@Claudio: I created a ticket about the wrong import of German files: https://github.com/woothemes/woocommerce/issues/9179 I am happy to use translate.wordpress.org instead of transifex, but I do not like to start from 0 when in fact more than 3500 strings have already been translated (many by myself 😉

As for changing the german default wording from formal to informal, that is up to you. I think one can do it, but I would communicate it very well to all german users to make sure that everybody notices this upfront. That after the version upgrade to 2.4.8 one has to switch the language setting to have it back the way it was before. I would personally choose a mayor version number like 2.5 for this as this will be a deeper change than any API change or whatever (only for german users)…

Like

@Claudio / @Florian:

> In my case it ist totally perfect that the informal version is the standard now

+1

Just to make this clear, I do also welcome this change! And I also like that WooCommerce will be handled the same way as WordPress from now on. That is good.

Like

You will reviewer, will be free to do whatever you want with that language, but are impossible for us to import those languages again.
We as the plugin author’s, we don’t have any permission or tool to do this.
You are fighting with the wrong people. Because we can’t do what you want now.

Like

de_DE – @gerd.neumann
de_DE (formal) – @gerd.neumann

I was also reviewer at transifex for these two languages “codes” (formal and informal german as spoken in Germany)

Like

I would like to be a reviewer (Croatian lang files).
hr – @vipteam (WordPress.org username)

I am the last translator of Croatian lang files. Croatian langfiles are completed. I have extensive experience with translations. My translations are flawless and professional quality. I want to maintain the translation of future versions, too. Regards

Like

hu_HU – @vonsch. BTW I believe the hu branch needs to be separated to a formal and informal pack. The language is more formal in everyday life, by separating the 2 branches we simply provide an option.

Like

de_DE – @mhenschel
de_DE (formal) – @mhenschel

The formal german translation is at 96%. That’s why my shop is now set to default English language automatically. Who came up with this way of handling things?

Like

Comments are closed.