Google Translate API Changelog

What's new in Google Translate API 0.52

Aug 3, 2012
  • Internally splitting sourceTexts to avoid "Too many text segments" Google Translate API error.
  • The splitting and sending is done internally in the translate and detect methods so there is no limitation of the length of sourceTexts as far as the user is concerned.
  • Adding location and locationType to ApiError.ErrorEntry

New in Google Translate API 0.51 (Aug 3, 2012)

  • Changing default toString behaviour in the core module to allow easier usage in applications:
  • Translation.toString() returns the translatedText
  • Detection.toString() returns the language
  • Language.toString() returns the name or the language if the name is null
  • The plain output format of the CLI module was not changed. The toString format can be determined by the "org.google.translate.api. v2.core.model.toString" Java property
  • Adding the "org.google.translate.api.v2.core.model.toString" Java property
  • Allowed values are:
  • short - returns the most simple and important info (Default when using the core module)
  • long - returns all the not null fields
  • full - returns all the fields (Default when using the CLI module)
  • Adding ability to pass the Google API key to the CLI module using an environment variable "GOOGLE_API_KEY" instead of the apiKey option
  • If both are available, the apiKey option will be used.
  • Adding the verbose option to allow more detailed info to assist troubleshooting

New in Google Translate API 0.5 (Aug 3, 2012)

  • translate - Translates source text(s) from source language to target language
  • languages - List the source and target languages supported by the translate methods
  • detect - Detect language of source text(s)