Posted by druvision on October 18, 2006 at 2:14pm
Killes once pointed out that it would be worthwhile to use Pootle for translations. Pootle is an online translation management portal. The issue was delayed last year because of hardware issues. Is it the time to float it again? Or do we plan a Drupal-based online translation portal?

Comments
excellent
i was trying to remember the name of pootle system for a week now ... yes, would be a fine addition IMO.
The advantage of a drupal-based system over pootle
is more accurate, screen-by-screen translations.
Translation is hard work, let's admit it.
To get better translations, we must make the life of the translator easier.
What's the advantage of a Drupal-based system over pootle?
More integration = better translation.
Don't translate if you don't understand the context!
Best translation is achieved when you translate screen by screen, using a dictionary of terms, after you see the screen of the previous (translated) version.
Hey, WE CAN SHOW THE SCREEN OF THE PREVIOUS VERSION WHILE THE TRANSLATION is ACTIVE and DYNAMICALLY SHOW HOW & WHERE THE TEXT is CHANGED via the proper AJAX / JQUERY script!
Of course, some integration required...
agreeing Daniel F.
agreeing
Daniel F. Kudwien
unleashed mind
Daniel F. Kudwien
netzstrategen
As I said in private mail:
As I said in private mail: It would be possible to use Drupal with Konstantin's inline editing instead. This will take some time, though, as this isn't fully working yet.
I'm still interested
Just haven't had time to push it. We should do t.drupal.org....just need time and/or funding or ???
Maybe this is something that Gabor can help drive, as well?
I just had a (IMHO)
I just had a (IMHO) brilliant idea on how to solve the issue with
ted strings inselects, dropdown boxes and on buttons: We don't output any markup around the string (currently it works withspans around the text). All we do is adding the string as setting in the page header. A JavaScript function now searches the page for occurrences of that string. If it's a plain string, it will just wrap thespanaround it. If it's not, it will add a button next to the element. That way we could also solve the placeholder issue: We write the unaltered string that should be translated in the page header and let JavaScript regexp through the page.