> In Ubuntu, I don't see the locales in the Enigmail package although it might be in the source.
Of course they are in the package - as i said, the localization works fine.
To be exact, they are within
/usr/lib/xul-ext/enigmail/chrome/enigmail.jar
in the /locale/ folder.
If you want to go through the work of re-adding the ability to have "translation extensions" to enigmail, and somehow marry that to launchpad's TBD universe translation facilities, that is of course your choice. And at that point, we still don't have a single additional translated string yet.
I however think it should be way easier to do an automatic VCS import of enigmail, and set up LP to translate an enigmail branch automatically. Plus, this gives us a chance to cooperate with upstream, instead of rolling another ubuntu-only solution.
Oh, and if we cannot remove a source package from lucid, we can always upload a followup version that only builds one or a few empty transitional packages.
> In Ubuntu, I don't see the locales in the Enigmail package although it might be in the source. lib/xul- ext/enigmail/ chrome/ enigmail. jar
Of course they are in the package - as i said, the localization works fine.
To be exact, they are within
/usr/
in the /locale/ folder.
If you want to go through the work of re-adding the ability to have "translation extensions" to enigmail, and somehow marry that to launchpad's TBD universe translation facilities, that is of course your choice. And at that point, we still don't have a single additional translated string yet.
I however think it should be way easier to do an automatic VCS import of enigmail, and set up LP to translate an enigmail branch automatically. Plus, this gives us a chance to cooperate with upstream, instead of rolling another ubuntu-only solution.
Oh, and if we cannot remove a source package from lucid, we can always upload a followup version that only builds one or a few empty transitional packages.