Re: Requesting some room to install pootle.debian.org
> I would welcome a frontend for translations, but I would also like to
> either be able to restrict who is able to touch certain translations or
> have a review/approval mechanism before (changes in) translations are
> committed.
The point of tools like Pootle, Rosetta or any other is more offering
an easy to use interface to at least get the translation material,
handle the reviewing operations and synchronize work with some
"upstream".
This actually far more than online translation, which I actually don't
really believe into as well.
The framework we want to setup is more organizing the path of
translators towards PO files. After this, this is IMHo up to them when
it comes at choosing the tool to work on files.
I won't personnally focus on online translation features and,
actually, I don't really care of them for Debian. Our translators are
used to work offline, and anyway, the Debian distributed development
mechanism probably doesn't fit very well with online translation.
Thus the key features become:
-easy adaptability to the problesm we have in Debian (several
"sub-projects" such as debconf translations, programs translations,
documentation translation, web site translation, packages descriptions
translations...) and, inside these sub-projects, sub-suc-projects for
some of them (one per package for debcof translations for instance)
-correct reviewing process and easy to fit with the current review
processes (based on public reviews on mailing lists)
-interaction with the BTS
-interaction with many types of sources to get the material (CVS, SVN
repositories, Debian archive, arch repositories...)
--
Reply to: