hyunsupul/aesop-core

Prep for WordPress.org language packs

Opened this issue · 7 comments

As noted by @pippinsplugins:

"Translation packs were just announced for plugins on WordPress.org: https://make.wordpress.org/plugins/2015/09/01/plugin-translations-on-wordpress-org/

This is a really big deal and we should absolutely jump on board.

TLDR: WordPress.org will host all plugin language files and allow users to update their translations anytime a new version is available. ASE will no longer need to maintain or distribute language files.

There are a few things that have to happen in order for language packs to be supported by ASE:

WordPress.org has to enable them. This is happening in batches. See post above

Our textdomain must be changed to aesop-story-engine. They require the text domain match the plugin slug. This will break existing translations for anyone that has manually translated text through WPML, qTranslate, Polylang, Say What, etc.

Language files must be removed from the plugin.

Transifex would no longer be used as all translation would happen by the Polyglots team on WordPress.org. I do not yet know if our Transifex contributors could contribute there.

All translations need to be up to date before ASE gets language packs enabled.

@fxbenard Definitely want your input here."

Heads up from #3757.

Maintain backwards compatibility: http://ibrokemywp.com/2014/12/16/use-your-plugin-or-theme-slug-as-the-textdomain-not-whatever-other-stupid-idea-you-might-have/.

Read all my comments on that also!

Yea, we have. Thanks for being vocal and ever present @fxbenard!

:( @fxbenard I hope you guys can work out something with the WP polyglots so WP Translations can stay active, would hate to see you guys go obsolete

You all are wonderful! We want to continue with your help.

You are not forgotten for sure. It would be great if there was a way to integrate what you all are doing with GP somehow.