Hello, Peer Sommerlund wrote: > There have been som license talk on the list where we should use > Launchpad or not. As I understand it the present situation is that > all translations are licenced under GPL v2, but we can still use > Launchpad. If this is not correct, we may have to skip Launchpad.
Disclaimer: I don't fully understand all the legal issues even on my own country, so please take the following as pure speculation :-) The Launchpad FAQ states that "Translations are freely shared between projects on Launchpad. Copyright complicates that free exchange. That's why our terms of use require that, when you translate in Launchpad, you grant us the right to share those translations with other projects." If all TortoiseHg translated messages are indeed licensed under GPL v2 only, they may only be reused by compatible projects. But the Launchpad web interface doesn't help here: it shows links for the projects containing the suggested translations, but the translator must check the project licenses himself to be sure he is able to reuse it - and the Launchpad FAQ says exactly otherwise (so the "induce people to violate the GPL" complaints). That *may* not be a problem because if a translation is reusable, its original string is already available under the other project license. So if the translation work itself has a compatible license, it might be used without licensing conflicts. The safest of course would be to avoid Launchpad (its main instance, actually; a separate instance restricted to GPLv2 projects would be fine) until this issue is clarified. > The roundtrip to Launchpad looses translator emails on csets (it > will look as if Steve did all the translations), but it also allows > some translators to contribute translations in small steps via the > web interface. IMHO the missing attributions is another reason to avoid Launchpad. Looks like only the last translator is mentioned on the .po headers. The small step translations may also not be as useful as they sound, because sometimes the translator needs to understand the *purpose* of the message. I just found on a small contribution the button label "Push" (as in "hg push") translated as a Portuguese word with a totally different meaning (as in "to push a button"); in this particular case it's even better not translating it at all, so it matches the hg command. > The above description is the current way of working. If you have > a better way to work with translations, please post it here. I don't know any tool that would give proper attribution and a web interface, unfortunately. For Mercurial, I believe most translation teams use a separate repository and work on the .po files directly. Thanks, Wagner ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Tortoisehg-develop mailing list Tortoisehg-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop
