Update Japanese translation #284
Conversation
|
Hi, Per #66 (comment) we prefer to handle translations on Launchpad. See https://translations.launchpad.net/variety |
|
@peterlevi Just for future reference, can you walk me through the process for importing translation updates once they're made on Launchpad? |
|
@jlu5 from Lauchpad to the app: https://translations.launchpad.net/variety/trunk/+export, request a zip download, you'll get an email with the zip, get the PO files for the languages we support the zip (I limit this only to languages that are at least some 80-85% complete, see the list in https://translations.launchpad.net/variety and compare to the language files we already have in the app), and update them in our codebase. Reflecting text changes in the app in Launchpad - this used to be an automatic process when we were hosting in Launchpad, but now I think we need to be doing it manually, and I'm not fully sure what the right process is. I think the .pot file needs to be generated with something along these lines: and then the .POT file needs to be manually uploaded via https://translations.launchpad.net/variety/trunk/+translations-upload. But I've only done it once after we migrated to Github, and I'm not 100% sure this is fully correct. Also we probably need a way to automate more of this process. |
|
Also, as a whole, Translations are right now not synced at all with releases, and they kinda follow in lock-step fashion, so we practically never release 100%-fully translated software. This would be desirable, but also very hard to achieve and I'm not sure it's realistic for releases to wait for Lauchpad translators to "fill in the gaps". So up till now I've always treated translations as "facilitate them, but don't let them block the process, don't wait on them". |
|
Yuck, manual steps are not ideal... I'll admit that I glossed over the translations process when I migrated the repo to GitHub. It looks like Launchpad only supports importing repos from bzr, and it isn't trivial syncing them together. Do we have any other options for i18n management that integrate better with our current repo? |
|
It's not something I've researched much... Could be there are better options than Launchpad. On the other hand, the amount of input we've received there from translators is pretty huge - it's not only the tooling, it's also the existing translators groups and available community and established processes around Ubuntu that's been valuable there. I suppose with the tools provided for syncing git and bzr repos in Launchpad, it should be able to get a more-or-less equivalent process as before, I've just never spent the time to research this, and also Launchpad is confusing as hell in that aspect. |
|
Hi.
I got it. |
|
I want to apologize for the confusion - lacking an automerge process it looks like a lot of the proposed translations updates on Launchpad have gone stale. I've merged your PR into master just now. In #362 I hope we can find a better process for translations going forward. |
No description provided.