Let Google suggest translations
claudiu.cristea - October 19, 2009 - 07:23
| Project: | Localization server |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | claudiu.cristea |
| Status: | needs work |
Description
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...
| Attachment | Size |
|---|---|
| l10n_server_google_translate-D6.patch | 10.52 KB |
#1
Forgot the new icon. The attached icon should be copied to
sites/all/modules/l10n_server/l10n_community/images.#2
I 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)
#3
Let 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.
#4
Additional - 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.
#5
@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).
#6
CNW for abstraction layer.
I'm strongly against Google translation service. RIP!
#7
In 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
#8
subscribe
#9
I'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.