Re: Adding Python GTK+ 3 Tutorial to Damned Lies

[Claude Paroz <claude 2xlibre net>]

Le 05.04.20 à 11:18, Sebastian Pölsterl a écrit :
> Hi Claude,
>
> the text isn't changing very often these days, so having a .pot file
> added would be no problem.
>
> Once I added the .pot file, what would be required for integrating it
> into Damned Lies?

Nothing more, I guess.

> Can the project remain on github or should it be moved
> git GNOME's gitlab?

It can remain on github, the downside being that D-L cannot push
translations, so coordinators have to manually create pull requests.

Claude


> Am 21.03.20 um 23:06 schrieb Claude Paroz:
> > Hi Sebastian,
> >
> > Le 20.03.20 à 12:06, Sebastian Pölsterl a écrit :
> > > Dear translation team,
> > >
> > > I'm the author of The Python GTK+ 3 Tutorial
> > > (https://python-gtk-3-tutorial.readthedocs.io/) and recently was asked
> > > whether an integration with Damned Lies is possible (see
> > > https://github.com/sebp/PyGObject-Tutorial/issues/160). I never worked
> > > in translation before, therefore I'm not sure what would be required to
> > > make this happen.
> > >
> > > The tutorial is written in reStructered text using Sphinx. While Sphinx
> > > has support for i18n, I'm not sure whether integration into Damned Lies
> > > is possible at all.
> >
> > It is surely possible, but Damned Lies doesn't currently support the
> > sphinx i18n toolchain, so you'd have to provide the pot files in the
> > source code (and update them regularly).
> >
> > > Any suggestions on what be the best way forward to make it easy for
> > > translators to contribute would highly welcome.
> >
> > The sphinx toolchain is creating a po file for each subdocument, which
> > is good when you have big documents, less when you have smaller
> > documents, as this means more manipulations by translators and
> > coordinators. This is also taking much more space in the D-L interface.
> >
> > One solution would be to merge all pot files into one, then re-splitting
> > the translated po files into multiple po files through msgmerge. This
> > would certainly require more work at Makefile level...
> > See https://stackoverflow.com/questions/15408348
> >
> > Claude