MakeTextWebFrameworks

Web-based translation tools

Pootle

• Project: http://translate.sourceforge.net/wiki/pootle/index
• Demo: http://pootle.locamotion.org/de/
• vitality: regular releases, last release 2008-10-08, many big projects using it
• License: GPL

Features

• has a web-based translation editor
• can run against our existing PO files and don't need a database
• can submit directly to version control including CVS, Subversion, darcs, git and Bazaar
• users can make suggestions for translations and supports bug reporting
• can generate suggestions from a translation memory to aid translators
• can display an alternative source language while translating

Requirements

• Translate Toolkit package from http://translate.sourceforge.net/
• Python 2.4 or higher.

Rosetta (Launchpad)

Launchpad is a hosting service for open source projects. It includes a project registry, code branch registry and mirroring service, bug tracker, specification tracker, translation service, and question tracker.

• Project: https://launchpad.net/rosetta
• vitality: last release 2008-09-25, seems pretty healthy
• License: online service (no download) translation in BSD

netbabel

• Projekt: http://sourceforge.net/projects/netbabel
• vitality: last release 2005-11-28
• License: GPL

Kartouche

• Project: http://www.dotmon.com/kartouche/
• License: GPL
• vitality: last release 31 October 2003

Entrans

• Project: http://entrans.sourceforge.net/wiki/index.php/Main_Page
• Demo: http://entrans.sourceforge.net/demo/main.php
• vitality: last release 20 Apr 2006

Flossmanuals (maketext translations possible?)

• Project: http://en.flossmanuals.net

Discussion

I did a research for a proper tool to get our translation process straight. It comes all down to use Pootle, which is vital and give us full access to modify it to our needs.

Please add missing tools and comment on existing, so that we can base a final decision on it.

-- AndreUlrich - 21 Nov 2008 - 15:44

Lots of phrases require context knowledge. How would such an open framework cope with that?

Another concern I have is consistency of wording. Can that be guaranteed? Do we need to create a jargon checklist before handing phrases over to the translating community?

-- ArthurClemens - 21 Nov 2008 - 23:41

Andre, great idea, thanks for the work!

I like the jargon checklist. "Poetry is what doesn't translate," and stringing words like a native can't be automated.

Basically, I think every language requires at least one supporter who has at least 2 languages. (And I'm out: Dieser Amerikaner hat meiste seine Deutsche verloren . . . strangely, though, I actually remembered "verloren" before I checked with translate.Google.com

-- NathanDye - 22 Nov 2008 - 04:02

Main goal of this translation tool is, to keep the barrier of contributing translations as low as possible. It should provide translators an easy access and and a usable editor without much work on their side. At the moment they have to download files from SVN, translate them with the tool of their choice (without context) and upload them again.

Context of strings would be nice. I had a project where we build a translator and also had concepts for such a context tool. For now I think we should stick with what´s available.

BTW Pootle supports some kind of jargon list: http://translate.sourceforge.net/wiki/pootle/terminology_matching

-- AndreUlrich - 22 Nov 2008 - 13:46

Sounds good. Could you create a how-to overview for Foswiki translators?

-- ArthurClemens - 22 Nov 2008 - 16:20