Make material translatable via LP whenever possible

Bug #1257291 reported by Pierre Slamich on 2013-12-03
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

For SVG files (and others as possible), would it be possible to turn them into a po file and make them translatable using launchpad ?
Translations would then be imported back into files, which would be reviewed manually (to see if the size of the translation doesn't break the design) and then approved.

Evan Boldt (echowarp) wrote :

I definitely see the advantage of using LP for translations. Initially, the site navigation features were translatable that way. However , it became a problem to make sure that both translation places are syncronized. That is why the interface is only translatable on the site now. It also happens to be more convenient because it allows the important strings to be more obvious on the page while you are translating them. I think the same thing would happen with translatable materials, if that were technologically easy to accomplish. It would likely be easier to simply use the site to find a material you want to translate, and then do the translation in an editor on the source file. This also allows further localization, like if a screenshot is in another language, flag happens to be on it, or a LoCo logo is on it.

That being said, launchpad does have some nice features for translators. I don't think it would even be very easy to implement without having to just manually transcribe between the two mediums constantly. While it might be possible for SVGs, some source files are PSDs, or ZIP/TAR files with SVGs. I don't think there's any way to make it a complete solution.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers