Using AMOS tool for language pack translation

Generating a translation memory and running a quality test

Picture of Daniel Neis Araujo
Re: Generating a translation memory and running a quality test
by Daniel Neis Araujo - Sunday, 8 February 2015, 10:56 PM
Language pack maintainers


nice work being done!

I am working with translating Moodle and other software and content - first was ubuntu at launchpad, back on 2009 or early, than moodle of course, and more recently i've tried Transifex for the GNU MediaGoblin project ( that have moved to Pootle recently ( They use gnu po files and this Pootle tool let you download the text file and translate offline and also translate and review online. I've used it just for an afternoon and it seems to be a very good tool. A point to note is that they count words to translate and not strings. It woul be nice to have this on AMOS too =)

Last year i have also participated on the Mozilla Translation quality project ( that is a very good approach to quality review and they generated a framework for this and have used a tool to conduct the job (

Thay have very good instructional videos on how to use the tools and it is really quick to review things to work on and have a better metric than "100% translated". With this revision tool you can see how many good and poor translated strings you have.

I've also played with video sub-titling on that is an awesome jaw-dropping tool, really amazed with how easy is the process to translate and sync subtitles.

Last month I've also tried the new Wikipedia Content Translation tool that easies the process of translating wikipedia pages from one language to another if the page does not exist on the destination language. Interesting links are:

It would be very nice if Moodle let users translate strings on the common interface, it woul eliminate the major problem with translations that is context. Much times on AMOS you don't know if a phrase is on "infinitive" or "declarative" or things like that.

We already have an option that let you pass "&strings=1" on the url and get the indentifier for the strings. What about implement a webserver on amos that let people click on the text, it get transformed on a text input with a confirm and cancel buttons attached that when you click confirm send it as a contribution to AMOS? A side benefit is to end with 300 strings contributions that are hard (time consuming) to review.

What do you say?

Kind regards,