Wp-calypso: i18n: define process for localizing extensions

Created on 9 Apr 2017 · 6Comments · Source: Automattic/wp-calypso

Extensions need to be translated separately from the main calypso codebase:

Most strings already exist in the wp-admin version of the extension
Extension strings are often specific and require more context and knowledge for translators.
Just adding all strings to our main string file regardless of if they're being used will create bloat.

Imagining the best solution possible, we'd probably want extensions to define their translate.wordpress.org URL, and download the translations directly from there, without using any wpcom infrastructure. Our translation functions syntax is different from WP's in a few areas, but nothing that can't be normalized in the transfer.

TODOs:

[x] Disable extensions strings from being added to calypso-strings.pot
[ ] Figure out a process for reusing translations from translate.wordpress.org

Extensions [Status] Stale [Type] Task i18n

Source

yoavf

Most helpful comment

Pinging a few people who might have thoughts on this @allendav @ockham @mtias
It'd be great if we can figure out a plan before we launch popular extensions.

yoavf on 16 May 2017

👍2

All 6 comments

Pinging a few people who might have thoughts on this @allendav @ockham @mtias
It'd be great if we can figure out a plan before we launch popular extensions.

yoavf on 16 May 2017

👍2

cc @gedex

allendav on 16 May 2017

@Automattic/store Bump! Since we're going to open Store internationally soon, we should figure out how to translate extensions.

Since all the current extensions are our own and are part of the wp-calypso codebase, what about including the /extensions folder again for translations? So it follows the same process as the rest of Calypso.

DanReyLop on 14 Jan 2018

@DanReyLop We could - but that wouldn't solve the points from this issue, which are still painful.
@Automattic/i18n is going to work on this. Eventually, we'd want to have:

A separate project per extension on translate.wordpress.com
Automatic import of existing translations (including placeholder substitution) from respective existing wp-admin translations (i.e, import any matching translations from https://translate.wordpress.org/projects/wp-plugins/woocommerce for the store extension)

yoavf on 15 Jan 2018

👍1

As a first step, for the WooCommerce store extension, I've created https://translate.wordpress.com/projects/wpcom/calypso-extensions/woocommerce/ and imported several projects from translate.wordpress.org (as per the plugins listed on https://github.com/Automattic/wp-calypso/blob/master/client/extensions/woocommerce/README.md) :

Which gives us already a nice translated percentage of up to 36%. After we have translated them, we should be able to share them back to translate.wordpress.org.

akirk on 15 Jan 2018

This issue has been marked as stale and will be closed in seven days. This happened because:

It has been inactive in the past 9 months.
It isn't a project or a milestone, and hasn’t been labeled `[Pri] Blocker`, `[Pri] High`, `[Status] Keep Open`, or `OSS Citizen`.

You can keep the issue open by adding a comment. If you do, please provide additional context and explain why you’d like it to remain open. You can also close the issue yourself — if you do, please add a brief explanation.