[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: localisation: status, migration to pootle

From: Mattias Engdegård <mattiase_at_bredband.net>
Date: Wed, 7 Aug 2013 23:43:36 +0200

2 aug 2013 kl. 21.27 skrev Andreas Stieger:

> I would like to hear from active translation maintainers if they are
> happy to move their respective translations into Pootle and work on
> that
> system. If so I am willing to coordinate the import, even if just for
> trying it out. With sufficient support from active translation
> maintainers we can bring all languages in.

Sorry about the late reply; I rarely have time to read the development
list. It seems unlikely that many translators do - how are they
notified about the need to update their translations? It is common to
have this as an explicit step in the release process; perhaps I have
missed the broadcasts so far.

It has been very valuable to work in the Subversion source tree
directly for several reasons. Doing so provided a direct source code
context for the translation, without which many strings would have
been difficult to interpret correctly. It would also have been
impossible to get formatting and line breaks right without being able
to build and test Subversion with the new .po file.

I know nothing about Pootle; it may very well be the bee's knees. How
well does it cope with the mammoth strings in Subversion's help (like
that for "svn merge")? What about fixed layout (indentation, ASCII
art, etc)? Line length limitations? I'm not saying these aspects are
of utmost importance, but they are probably somewhat peculiar to
Subversion.

Perhaps Pootle is the answer, but I'd rather suggest involving some
broader translation collective like the Translation Project.
Received on 2013-08-07 23:44:12 CEST

This is an archived mail posted to the Subversion Dev mailing list.