API Client library for the Cloud Translation API
Cloud Translation can dynamically translate text between thousands of language pairs. Translation lets websites and programs programmatically integrate with the translation service.
Actual client classes for the various versions of this API are defined in
versioned client gems, with names of the form google-cloud-translate-v*.
The gem google-cloud-translate is the main client library that brings the
verisoned gems in as dependencies, and provides high-level methods for
constructing clients. More information on versioned clients can be found below
in the section titled Which client should I use?.
View the Client Library Documentation for this library, google-cloud-translate, to see the convenience methods for constructing client objects. Reference documentation for the client objects themselves can be found in the client library documentation for the versioned client gems: google-cloud-translate-v2, google-cloud-translate-v3.
See also the Product Documentation for more usage information.
$ gem install google-cloud-translate
In order to use this library, you first need to go through the following steps:
- Select or create a Cloud Platform project.
- Enable billing for your project.
- Enable the API.
- Set up authentication.
The 3.0 release of the google-cloud-translate client is a significant upgrade based on a next-gen code generator, and includes substantial interface changes. Existing code written for earlier versions of this library will likely require updates to use this version. See the {file:MIGRATING.md MIGRATING.md} document for more information.
This library comes with opt-in Debug Logging that can help you troubleshoot your application's integration with the API. When logging is activated, key events such as requests and responses, along with data payloads and metadata such as headers and client configuration, are logged to the standard error stream.
WARNING: Client Library Debug Logging includes your data payloads in plaintext, which could include sensitive data such as PII for yourself or your customers, private keys, or other security data that could be compromising if leaked. Always practice good data hygiene with your application logs, and follow the principle of least access. Google also recommends that Client Library Debug Logging be enabled only temporarily during active debugging, and not used permanently in production.
To enable logging, set the environment variable GOOGLE_SDK_RUBY_LOGGING_GEMS
to the value all. Alternatively, you can set the value to a comma-delimited
list of client library gem names. This will select the default logging behavior,
which writes logs to the standard error stream. On a local workstation, this may
result in logs appearing on the console. When running on a Google Cloud hosting
service such as Google Cloud Run, this generally
results in logs appearing alongside your application logs in the
Google Cloud Logging service.
This library is supported on Ruby 2.7+.
Google provides official support for Ruby versions that are actively supported by Ruby Core—that is, Ruby versions that are either in normal maintenance or in security maintenance, and not end of life. Older versions of Ruby may still work, but are unsupported and not recommended. See https://www.ruby-lang.org/en/downloads/branches/ for details about the Ruby support schedule.
Most modern Ruby client libraries for Google APIs come in two flavors: the main
client library with a name such as google-cloud-translate,
and lower-level versioned client libraries with names such as
google-cloud-translate-v2.
In most cases, you should install the main client.
A versioned client provides a basic set of data types and client classes for a single version of a specific service. (That is, for a service with multiple versions, there might be a separate versioned client for each service version.) Most versioned clients are written and maintained by a code generator.
The main client is designed to provide you with the recommended client interfaces for the service. There will be only one main client for any given service, even a service with multiple versions. The main client includes factory methods for constructing the client objects we recommend for most users. In some cases, those will be classes provided by an underlying versioned client; in other cases, they will be handwritten higher-level client objects with additional capabilities, convenience methods, or best practices built in. Generally, the main client will default to a recommended service version, although in some cases you can override this if you need to talk to a specific service version.
We recommend that most users install the main client gem for a service. You can
identify this gem as the one without a version in its name, e.g.
google-cloud-translate.
The main client is recommended because it will embody the best practices for
accessing the service, and may also provide more convenient interfaces or
tighter integration into frameworks and third-party libraries. In addition, the
documentation and samples published by Google will generally demonstrate use of
the main client.
You can use a versioned client if you are content with a possibly lower-level
class interface, you explicitly want to avoid features provided by the main
client, or you want to access a specific service version not be covered by the
main client. You can identify versioned client gems because the service version
is part of the name, e.g. google-cloud-translate-v2.
Client library gems with names that begin with google-apis- are based on an
older code generation technology. They talk to a REST/JSON backend (whereas
most modern clients talk to a gRPC backend) and they may
not offer the same performance, features, and ease of use provided by more
modern clients.
The google-apis- clients have wide coverage across Google services, so you
might need to use one if there is no modern client available for the service.
However, if a modern client is available, we generally recommend it over the
older google-apis- clients.