Thread: [translate-pootle] Pootle and Sphinx

Dear Pootle developers,

I am Robert Lehmann[1], a student from Germany currently engaging in
Google's Summer of Code for the Python Software Foundation[3] for
native language support in the Sphinx documentation generator.  We
stumbled over Pootle while researching PO tools and would like to
adapt it to our needs for translation maintenance.

I will quickly outline our scenario and run down my proposed
implementation strategy.  If you feel I am taking Pootle into a
direction it is unsuited for, reinventing wheels where unnecessary or
have any other feedback I'd love to hear from you!

Sphinx utilizes a light markup language called *ReStructedText*
[3][4][5] which boils down to plain text paragraphs with non-nestable
inline markers (*roles*).  Sphinx parses such documents and outputs a
variety of formats, including but not limited to HTML and PDF.  It
will grow an extractor for translatable strings this summer (a POT
builder).  (Or is directly feeding strings into a database more
appropriate?)

Text documents usually consist of large paragraphs and cannot be
reliably split into fine-grained individual messages. Thus it is
absolutely crucial to our workflow to identify small changes (eg. typo
fixes) and show them appropriately to translators. I plan to extend
Pootle's capabilites in this domain and integrate it with
ReStructedText and Sphinx.

I already checked out SVN trunk and toyed around a bit locally. I
would like to contribute my changes back to upstream -- do you require
any contribution forms or some such? Did Git gain any significant
traction?

Sincerely yours,
Robert

[1] http://www.robertlehmann.de/ -- see also my GSoC blog
http://gsoc.robertlehmann.de/
[2] on behalf of the Pocoo Team http://dev.pocoo.org/
[3] tutorial A ReStructedText Primer
http://docutils.sourceforge.net/docs/user/rst/quickstart.html
[4] markup reference Quick reStructedText
http://docutils.sourceforge.net/docs/user/rst/quickref.html
[5] technical reference An Introduction to reStructuredText
http://docutils.sourceforge.net/docs/ref/rst/introduction.html

On Fri, 28 May 2010 21:46:11 +0200
Robert Lehmann <ro...@ro...> wrote:

> Dear Pootle developers,
> 
> I am Robert Lehmann[1], a student from Germany currently engaging in
> Google's Summer of Code for the Python Software Foundation[3] for
> native language support in the Sphinx documentation generator.  We
> stumbled over Pootle while researching PO tools and would like to
> adapt it to our needs for translation maintenance.

yaaaay sounds exciting

> Sphinx utilizes a light markup language called *ReStructedText*
> [3][4][5] which boils down to plain text paragraphs with non-nestable
> inline markers (*roles*).  Sphinx parses such documents and outputs a
> variety of formats, including but not limited to HTML and PDF.  It
> will grow an extractor for translatable strings this summer (a POT
> builder).  (Or is directly feeding strings into a database more
> appropriate?)

if you implement a Translate Toolkit storage class it becomes easier to
write a converter to POT and for pootle to directly support the source
format (pootle basically converts to it's own in database format that's
also a translate toolkit storage class).

> Text documents usually consist of large paragraphs and cannot be
> reliably split into fine-grained individual messages. Thus it is
> absolutely crucial to our workflow to identify small changes (eg. typo
> fixes) and show them appropriately to translators. I plan to extend
> Pootle's capabilites in this domain and integrate it with
> ReStructedText and Sphinx.

this is certainly something we'd love to improve, making pootle more
useful for document translation. what are your plans exactly?
 
> I already checked out SVN trunk and toyed around a bit locally. I
> would like to contribute my changes back to upstream -- do you require
> any contribution forms or some such? Did Git gain any significant
> traction?

Nah I don't think we have much legalese to go through (Dwayne would
know more), I'm using git-svn on my machine last time I tried working
from two separate git-svn checkouts was a bit messy but I'm sure we can
figure something out.

cheers,
Alaa

Op Vr, 2010-05-28 om 21:46 +0200 skryf Robert Lehmann:
> Dear Pootle developers,
> 
> I am Robert Lehmann[1], a student from Germany currently engaging in
> Google's Summer of Code for the Python Software Foundation[3] for
> native language support in the Sphinx documentation generator.  We
> stumbled over Pootle while researching PO tools and would like to
> adapt it to our needs for translation maintenance.
> 
> I will quickly outline our scenario and run down my proposed
> implementation strategy.  If you feel I am taking Pootle into a
> direction it is unsuited for, reinventing wheels where unnecessary or
> have any other feedback I'd love to hear from you!

Welcome to the project.


> Sphinx utilizes a light markup language called *ReStructedText*
> [3][4][5] which boils down to plain text paragraphs with non-nestable
> inline markers (*roles*).  Sphinx parses such documents and outputs a
> variety of formats, including but not limited to HTML and PDF.  It
> will grow an extractor for translatable strings this summer (a POT
> builder).  (Or is directly feeding strings into a database more
> appropriate?)

POT files are good.  It would mean that you have a variety of options,
and you work the way that almost all translation in the world of Free
Software works.  You want many translators, right? :-)

Pootle works perfect from POT files - this being the most common way
that it is used.


> Text documents usually consist of large paragraphs and cannot be
> reliably split into fine-grained individual messages. Thus it is
> absolutely crucial to our workflow to identify small changes (eg. typo
> fixes) and show them appropriately to translators. I plan to extend
> Pootle's capabilites in this domain and integrate it with
> ReStructedText and Sphinx.

Sounds interesting.  We currently do some interesting visual diffing of
translations in both Pootle (for showing suggestions), and in Virtaal
(for showing the differences with suggestions from translation memory).

I guess you might want to look into doing something like that, right?


> I already checked out SVN trunk and toyed around a bit locally. I
> would like to contribute my changes back to upstream -- do you require
> any contribution forms or some such? Did Git gain any significant
> traction?

Your contribution is welcome without anything special. You might be
interested in
 - our bug tracker:  http://bugzilla.locamotion.org/
 - our IRC channel:  irc://irc.freenode.net/#pootle

Please keep us up to date and discuss your ideas.  I think the most
important thing is to share ideas and ensure that we agree on where we
should aim.

Welcome once again!

Friedel


--
Recently on my blog:
http://translate.org.za/blogs/friedel/en/content/translation-saturday