GNOME Bugzilla – Bug 579253
Memory translation
Last modified: 2010-11-07 17:31:56 UTC
It would be possible to implement a simple memory translation in gnome-subtitles? It would be great not to have to translate the same thing over and over again(like old sayings or expressions that are repetitive) and not have to depend on external apps to do this kind of thing. My original ideia is: - A database that stores frases and search for them by lenght first in the direction, biggest to the smallest strings. - A button maybe called "translate what you can" - The possiblity to add and edit translations to the database. Should function kind of like the find and replace asking before changing something(maybe with a option for automatic replacement)
This will be interesting once we have a plugin system in place (#515578). It has been suggested previously in the mailing list. I have some questions regarding where to store translation that, and also about interoperability with other applications. What applications do you know to perform memory translation? Do they store strings internally, or is there the possibility to store them in an online database?
GNOME Translate 0.99 Is the translator for Gnome and it uses a lot of backends. Is there a way to connect the two? I mean gnome subtitles and gnome translate? ps: those backends are all online as far as I know it.
Thanks for the tips. Gnome Translate seems to be just a GUI for libtranslate, which actually does all the work and handles backend stuff. That's where integration can be handled. References: http://www.nongnu.org/libtranslate/gnome-translate/ http://www.nongnu.org/libtranslate/
I made a mockup. Check it out: http://img138.imageshack.us/img138/8550/gnomesubs.png
Andrius, Interesting mockup.
Andrius, Interesting mockup. One question: do you prefer to translate by overwriting the original subtitle text (as the mockup doesn't include the translation parts of subtitle list and editing).
Marking as a duplicate. Comments on this bug must be taken into account when fixing bug #595084. *** This bug has been marked as a duplicate of bug 595084 ***