Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.This a first attempt to add Google Translate as a suggestion generator to Localization Server interface.
Here's a first patch for testing, reviewing and improving.
Due to the UI impact of this feature, in some way this must be related to #563128: Rework the translation UI.
TODO:
- Add a configuration option to enable Google Translation. Basically setting the
l10n_community_google_translate. The variable is defaulting now to TRUE. - Check the availability of the Google service
- Check if language being translated is supported. See google.language.isTranslatable(lngCode)
- other improvements...
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | icon_google-translate.gif | 553 bytes | claudiu.cristea |
| l10n_server_google_translate-D6.patch | 10.52 KB | claudiu.cristea | |
Comments
Comment #1
claudiu.cristeaForgot the new icon. The attached icon should be copied to
sites/all/modules/l10n_server/l10n_community/images.Comment #2
Gábor HojtsyI think this is a good idea, but:
- let me prioritize the reworked UI before this :)
- we'd better make this a per-group feature, so groups can turn it off, or some people will scream on us to allow automated translations where people will not follow the guidelines for teams (many teams are very quality sensitive)
Comment #3
hass CreditAttribution: hass commentedLet Google suggest translations is really the most worst idea I have ever heard... I would never use Google as translation service. Have you ever read the damn ugly sh** that came out? I believe not... better translate by hand than using Google translation service.
I remember many approvers complained that many suggestions have "Google translation service" quality and are therefore not approved. It was often used as a "name" for bad suggestions :-)
This should be an extra and optional submodule what could also allow us to enable other (much more better) services.
Comment #4
hass CreditAttribution: hass commentedAdditional - in reference to claudiu.cristea's comment - Google translation service results are not a suggestion. This "suggestions" are simply wrong in most if not all cases. I cannot remember a day where I've got a suggestion by google translation service that was usable.
Comment #5
claudiu.cristea@hass
When I'm translating small pieces of text I'm translating by hand. When the text is bigger (help text, description, etc.) it would be helpful to have at least a Google Translate sh** to work on. That can be a bit more than "copy from source" - Believe me!
I totally agree that with you regarding the quality... That's why this should be enabled on "per-group" basis.
Yes. The condition is that those services should exists for your language. I have no doubt that they exists for German. But what about other languages?
In a "perfect world" this should be a sub-module that act like an abstraction layer where you can plug various services (including Google Translate).
Comment #6
hass CreditAttribution: hass commentedCNW for abstraction layer.
I'm strongly against Google translation service. RIP!
Comment #7
Gábor HojtsyIn an ideal world, we'd have an abstraction layer for suggestions on the UI at least and to some degree on the backend as well. Plugging in a translation memory based CAT tool would provide way better results. So having optional support for that would be great. Google translate can be one example where the text will indeed not be of highest quality :) See http://en.wikipedia.org/wiki/Computer_assisted_translation
Comment #8
podaroksubscribe
Comment #9
joachim CreditAttribution: joachim commentedI'm with hass. Translation is a job for humans; machines cannot do it. And I wouldn't use Google's suggestion as a basis to start from, because I'd probably leave cruddy bits in the text.
Comment #10
Gábor HojtsyI'm still at the position that this could be a good boost in some cases (it works on the UI and will not mass-submit suggestions for you). However, it would clearly need to be configurable per group I'd say. Also, it might be best to implement this as separate submodule maybe. Anyway, this is not currently in the critical path of the module as far as I'm seeing, since we are focusing on solving workflow issues with suggestion submission and moderation first before we add tools to submit even more suggestions :)
Comment #11
andypost+1 to submodule with abstraction layer. The "suggested staff" should never pasted directly to input element of translation interface.
My experience tolls me that first we need a tool to cleanup machine-translated strings that already take exists because lazy translators
Comment #12
Thomas_Zahreddin CreditAttribution: Thomas_Zahreddin commentedto #5
@claudiu.cristea
I can understand you prefer manual translations.
Form a professional point of view: If the translation can be done faster with the same quality (or maybe better), than I prefer this way.
I don't use google alone, but also bing, open-tran.eu and tausdata.org
on http://www.tausdata.org/index.php/starters-guide you can read:
‚Check out TDA member use cases to learn how others are increasing productivity and producing better machine translation. The benchmarks so far show 50% improvements on average.‘
and i can confirm the value of 50% for machine aided translation.
The most important tools i use are virtaal http://translate.sourceforge.net/wiki/virtaal/index
and omegaT http://omegaT.org
So, maybe you and others are interested to test these tools.
Comment #13
SebCorbin CreditAttribution: SebCorbin at Makina Corpus commentedGoogle Translation is now a paid service, so I'm going to postpone that for a while on branch 7.x