Re: Translations for LSR project

["Peter Parente" <parente gmail com>]

Lucky day. intltool-update --pot works fine. In fact, it actually
appears to do a better job than pygettext. I was not aware of this
improvement.

We already know that msginit works to generate language specific files
and have our install process setup properly to build po's and install
them as mo's. (At least it works with the dummy en_US.po translation
we provide.) I will go through the rest of i18n guide you sent me and
make sure all other requirements are met.

I do have one question. The license on LSR is the Common Public
License. It is an approved OSI license
(http://www.opensource.org/licenses/cpl1.0.php) but it isn't the GPL.
Is this a problem? How does licensing work for translations? Do they
inherit the license of the project or does gnome require the
translations to be GPL?

Thanks,
Pete

On 6/1/06, Christian Rose <menthos gnome org> wrote:
> On 6/1/06, Peter Parente <parente gmail com> wrote:
> > Thanks for the info. We can definitely look at how well the standard
> > intltool-update --pot commands works as compared with pygettext.py. My
> > guess is that intltool misses Python multiline strings, but we don't
> > have any of those that are translatable anyways.
> >
> > If I get the standard tools working with LSR, should I just email the
> > list again?
>
> Yes, please. As soon as LSR is compatible with the standard tools,
> we'd love to list it in the translation status pages so that
> translators can start translating it and track the status of their
> translations.
>
> Furthermore, if you have any questions for getting the standard tools
> to work, I'm sure there are some people on this list that can help.
> However, if the questions are very specific to implementation details
> or bugs in intltool itself, perhaps the intltool mailing list on
> freedesktop.org is a better choice.
>
>
> Christian