Details
-
Type:
Feature Request
-
Status: Open (View Workflow)
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
Description
Support for Google Translator would be a cool feature to have in Seam i18n.
Gliffy Diagrams
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
Important: The Google Translate API has been officially deprecated as of May 26, 2011. Due to the substantial economic burden caused by extensive abuse, the number of requests you may make per day will be limited and the API will be shut off completely on December 1, 2011. For website translations, we encourage you to use the Google Translate Element.
http://code.google.com/apis/language/translate/overview.html
Marek Schmidt
added a comment -
Important: The Google Translate API has been officially deprecated as of May 26, 2011. Due to the substantial economic burden caused by extensive abuse, the number of requests you may make per day will be limited and the API will be shut off completely on December 1, 2011. For website translations, we encourage you to use the Google Translate Element.
http://code.google.com/apis/language/translate/overview.html George,
I agree with Marek that implementing a link to a soon to be defunct service is wasted effort.
There is, however, the possibility of implementing an SPI for it in i18n.
Were you thinking more for build or runtime usage? I believe there is certainly a case for a build usage, possibly auto translating property files for a developer, but not sure I can see a valid runtime use.
Ken
Ken Finnigan
added a comment - George,
I agree with Marek that implementing a link to a soon to be defunct service is wasted effort.
There is, however, the possibility of implementing an SPI for it in i18n.
Were you thinking more for build or runtime usage? I believe there is certainly a case for a build usage, possibly auto translating property files for a developer, but not sure I can see a valid runtime use.
Ken Ken,
Totally agree with that. I wasn´t aware that the Google Translator API has been deprecated. Too bad.
A SPI is the right way to go, so it would be possible to extend this behavior to future implementations.
George Gastaldi
added a comment - Ken,
Totally agree with that. I wasn´t aware that the Google Translator API has been deprecated. Too bad.
A SPI is the right way to go, so it would be possible to extend this behavior to future implementations. 
Probably will need Seam REST integration, since it´s a REST service