El dv 30 de 04 de 2010 a les 20:07 +0000, en/na Luca Invernizzi va
escriure:
> >From your link: "Note that this only works for Ubuntu packages available in the repositories. The Launchpad integration library does not work with PPAs or other projects hosted in Launchpad."
> We are an ubuntu package but we are not in the "main" repository. Why are you mentioning main?
>
I was just mentioning it because the methods described in the
documentation I was pointing to will only work for packages in main,
i.e. if you add Launchpad Integration support like that to the Ubuntu
package, it will not take you to the translation page of GTG in http://translations.launchpad.net/ubuntu/+source/gtg/+pots/gtg, since
there isn't one. So simply adding a patch for the Ubuntu package it will
not "just work" for translations.
I realise it is sometimes confusing to discern between Ubuntu and
upstream when a given project is in Launchpad. I'm sorry if I created
any confusion in the wording of the original text in the bug.
My intention here is to better direct translators to the translations of
the _upstream_ project in Launchpad, not Ubuntu. That's why I was
pointing out to gwibber, since IIRC they do the following:
Note that as I mentioned, 2. will not work in the case of GTG and
translations, as GTG is not yet in main. So if in the end you decide to
implement this, you might want to leave out the Ubuntu patch for now.
For more information on why we expose translations for packages in main: https://wiki.ubuntu.com/Translations/Upstream (note that in the very
near future this will improve a lot for Ubuntu packages and
Launchpad-hosted projects, as translations will be shared, I can explain
it in more detail offline or on IRC if anyone is interested).
> Anyway, I'm neutral on this, since a lot of our users do not use ubuntu (or even linux). Perhaps it should be a patch in the ubuntu package.
> Developers, what do you think?
>
As I say, I think for now there shouldn't be a patch on the Ubuntu
package. If you want to implement this, I'd recommend doing it un the
upstream sources. Ultimately the goal here is to better direct
contributors to where they can translate or report bugs, and for now, in
the case of translations at least, this should be the upstream project
at https://translations.launchpad.net/gtg/trunk
For bugs, again it's up to you guys.
> ps: David, thanks for the various suggestions!
>
Thanks for making GTG rock! I am simply a user loving it and interested
in any improvements or suggestions that I hope can make it also have a
rocking localization support and use all the potential of the
translation community.
El dv 30 de 04 de 2010 a les 20:07 +0000, en/na Luca Invernizzi va
escriure:
> >From your link: "Note that this only works for Ubuntu packages available in the repositories. The Launchpad integration library does not work with PPAs or other projects hosted in Launchpad."
> We are an ubuntu package but we are not in the "main" repository. Why are you mentioning main?
>
I was just mentioning it because the methods described in the translations. launchpad. net/ubuntu/ +source/ gtg/+pots/ gtg, since
documentation I was pointing to will only work for packages in main,
i.e. if you add Launchpad Integration support like that to the Ubuntu
package, it will not take you to the translation page of GTG in
http://
there isn't one. So simply adding a patch for the Ubuntu package it will
not "just work" for translations.
I realise it is sometimes confusing to discern between Ubuntu and
upstream when a given project is in Launchpad. I'm sorry if I created
any confusion in the wording of the original text in the bug.
My intention here is to better direct translators to the translations of
the _upstream_ project in Launchpad, not Ubuntu. That's why I was
pointing out to gwibber, since IIRC they do the following:
1. Upstream sources include Launchpad integration pointing to bugs /translations. launchpad. net/gwibber/ trunk) /translations. launchpad. net/ubuntu/ lucid/+ source/ gwibber)
and translations in the upstream project in Launchpad
(https:/
2. The Ubuntu package has a patch pointing to bugs and translations
in the Ubuntu source package space in Launchpad
(https:/
Note that as I mentioned, 2. will not work in the case of GTG and
translations, as GTG is not yet in main. So if in the end you decide to
implement this, you might want to leave out the Ubuntu patch for now.
For more information on why we expose translations for packages in main: /wiki.ubuntu. com/Translation s/Upstream (note that in the very
https:/
near future this will improve a lot for Ubuntu packages and
Launchpad-hosted projects, as translations will be shared, I can explain
it in more detail offline or on IRC if anyone is interested).
> Anyway, I'm neutral on this, since a lot of our users do not use ubuntu (or even linux). Perhaps it should be a patch in the ubuntu package.
> Developers, what do you think?
>
As I say, I think for now there shouldn't be a patch on the Ubuntu /translations. launchpad. net/gtg/ trunk
package. If you want to implement this, I'd recommend doing it un the
upstream sources. Ultimately the goal here is to better direct
contributors to where they can translate or report bugs, and for now, in
the case of translations at least, this should be the upstream project
at https:/
For bugs, again it's up to you guys.
> ps: David, thanks for the various suggestions!
>
Thanks for making GTG rock! I am simply a user loving it and interested
in any improvements or suggestions that I hope can make it also have a
rocking localization support and use all the potential of the
translation community.
Cheers,
David.