A list with common words or words that are hard to translate would help a lot to improve the quality of the translation and it might reduce the time that's used to review the strings.

They use one on debian: http://ddtp.debian.net/ddtss/index.cgi/de/wordlist

"The wordlist is merely a convenience to help with consistent translation. If a word in the wordlist appear in the untranslated description, it becomes underlined and when you hover the mouse over it it will display the translation."

It's a great idea to have the words underlined, but on their system it's hard to add words to the list, and that's why those lists aren't used on most of the languages. I think that a better idea would be to have a simple way to suggest words that will be approved or rejected by the moderators of the translation.

Comments

meba’s picture

Sounds like a great addition, but I am not sure what it will do to the MySQL if we check if there is a "wordlist suggestion" for every word in a string...Gábor?

gábor hojtsy’s picture

Yeah, "automated translation" (even for simple words from a wordlist) is not yet in the scope of this project (there are still quite a few issues to solve so we can go live on drupal.org instead of sinking in feature-creep). There were quite a few suggestions with l10n_client about a Google translation service integration, so you can get automated translations from there. Granted that might not conform to your approved wordlist, so it does not cover exactly the same grounds.

gábor hojtsy’s picture

Version: 5.x-1.0-alpha3 » 6.x-1.x-dev

This was suggested multiple times by others as well. Ideally, we'd have a wordlist with suggested translations, and when you write a translation / suggestion, we'd have a pane showing which would list the words found in the wordlist and in the current text. There are some teams who implemented a wordlist but I'm not sure they integrated that with the editing interface. Any tips there?

droplet’s picture

we can make wordlist like this:
http://orderedlist.com/demos/quicksilverjs/jquery.html
(put it on sidebar, we can check it with AJAX results)

and while submit translation, automated check from wordlist.
if sentence contains wordlist keyword but translation haven't same suggest word.
notice to use suggest word.

for example,

Wordlist:
English: Apple
Other Lang: Applo

Translation:
English: This is an Apple
Translate: This is an Orange

When submit, give suggest:
suggest translation: Apple => Applo

(hope my explain make sense :) )

johnnoc’s picture

Also linking here http://localize.drupal.org/node/162 so people also become aware of the ongoing discussion about this on l.d.o.

podarok’s picture

subscribe

gábor hojtsy’s picture

Title: Word list » Add a wordlist / dictionary
balagan’s picture

I think it makes more sense to only parse the sentence being actually translated for the words contained in the wordlist, and then display only the occuring words on the right side (for example). Let the translator have the freedom to decide whether to use it (the context can be different).
In http://localize.drupal.org/node/162 there were quite a few solutions for wordlists, many used nodes with fields to store translations, and enable discussions.

SebCorbin’s picture

StatusFileSize
new39.24 KB

French team put a full glossary site (also used to provide guideline for contributors) that permits to vote on term translation suggestions and discuss via comments.

Then the glossary is exported in JSON and can be viewed while translating on l10n_client and localize.drupal.org via browser extensions, giving this:
Screen Shot 2012-10-15 at 14.48.03.png

Having this directly in l.d.o would be nice, unfortunately we have to wait (or better: contribute!) for D7 version.

Reviews and comments appreciated!

podarok’s picture

#9 can`t wait to see patch or extention for testing it

balagan’s picture

What if a word or expression can be (and should be) translated differently depending on the context and meaning of the source? Looking at the site I have only seen 1-to-1 translations, and not sure the extension supports displaying more items.

SebCorbin’s picture

Version: 6.x-1.x-dev » 7.x-1.x-dev
Status: Active » Postponed
StatusFileSize
new19.27 KB

Unfortunately we are down to a very basic functionality, for now we just separate contexts in our glossary like this
Screen Shot 2012-10-15 at 15.30.52.png
but working directly from l10n_server we could harness the context handling (providing developers actually use it)

balagan’s picture

Nice!

balagan’s picture

Version: 7.x-1.x-dev » 6.x-1.x-dev
Status: Postponed » Active

Well... Just thinking loudly: If that extension displays JSON from a source, it could just as well pull JSON from translation memory server. See my comments here: http://drupal.org/node/740494
The question is, is it possible to use this extension at the same time for 2 different purposes? Pulling JSON for vocabulary and also for TM?