-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prep for WordPress.org language packs #289
Comments
Read all my comments on that also! |
Yea, we have. Thanks for being vocal and ever present @fxbenard! |
Great. I will be less now ;)
Cya
|
:( @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. |
They aren't ready for it and don't even consider it. So I guess nope.
But people will come back as an alternative when they'll found out how
GP isn't ready yet to handle such an amount of plugins waiting for
translations. That's life, learning everyday. To tell you the truth I'm
kind of sad. My bad I didn't found the way to become an etasblished
alternative as fast as I expected. But I haven't told my last world.
|
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. |
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/.
The text was updated successfully, but these errors were encountered: