Cloud Translation: Node.js Client

release level npm version

Cloud Translation API Client Library for Node.js

A comprehensive list of changes in each version may be found in the CHANGELOG.

Read more about the client libraries for Cloud APIs, including the older Google APIs Client Libraries, in Client Libraries Explained.

Table of contents:

Quickstart

Before you begin

  1. Select or create a Cloud Platform project.
  2. Enable billing for your project.
  3. Enable the Cloud Translation API.
  4. Set up authentication with a service account so you can access the API from your local workstation.

Installing the client library

npm install @google-cloud/translate

Using the client library

/**
 * TODO(developer): Uncomment the following line before running the sample.
 */
// const projectId = 'YOUR_PROJECT_ID';

// Imports the Google Cloud client library
const {Translate} = require('@google-cloud/translate').v2;

// Instantiates a client
const translate = new Translate({projectId});

async function quickStart() {
  // The text to translate
  const text = 'Hello, world!';

  // The target language
  const target = 'ru';

  // Translates some text into Russian
  const [translation] = await translate.translate(text, target);
  console.log(`Text: ${text}`);
  console.log(`Translation: ${translation}`);
}

quickStart();

Samples

Samples are in the samples/ directory. Each sample's README.md has instructions for running its sample.

SampleSource CodeTry it
Translation_service.adaptive_mt_translatesource codeOpen in Cloud Shell
Translation_service.batch_translate_documentsource codeOpen in Cloud Shell
Translation_service.batch_translate_textsource codeOpen in Cloud Shell
Translation_service.create_adaptive_mt_datasetsource codeOpen in Cloud Shell
Translation_service.create_glossarysource codeOpen in Cloud Shell
Translation_service.delete_adaptive_mt_datasetsource codeOpen in Cloud Shell
Translation_service.delete_adaptive_mt_filesource codeOpen in Cloud Shell
Translation_service.delete_glossarysource codeOpen in Cloud Shell
Translation_service.detect_languagesource codeOpen in Cloud Shell
Translation_service.get_adaptive_mt_datasetsource codeOpen in Cloud Shell
Translation_service.get_adaptive_mt_filesource codeOpen in Cloud Shell
Translation_service.get_glossarysource codeOpen in Cloud Shell
Translation_service.get_supported_languagessource codeOpen in Cloud Shell
Translation_service.import_adaptive_mt_filesource codeOpen in Cloud Shell
Translation_service.list_adaptive_mt_datasetssource codeOpen in Cloud Shell
Translation_service.list_adaptive_mt_filessource codeOpen in Cloud Shell
Translation_service.list_adaptive_mt_sentencessource codeOpen in Cloud Shell
Translation_service.list_glossariessource codeOpen in Cloud Shell
Translation_service.translate_documentsource codeOpen in Cloud Shell
Translation_service.translate_textsource codeOpen in Cloud Shell
Translation_service.batch_translate_documentsource codeOpen in Cloud Shell
Translation_service.batch_translate_textsource codeOpen in Cloud Shell
Translation_service.create_glossarysource codeOpen in Cloud Shell
Translation_service.delete_glossarysource codeOpen in Cloud Shell
Translation_service.detect_languagesource codeOpen in Cloud Shell
Translation_service.get_glossarysource codeOpen in Cloud Shell
Translation_service.get_supported_languagessource codeOpen in Cloud Shell
Translation_service.list_glossariessource codeOpen in Cloud Shell
Translation_service.translate_documentsource codeOpen in Cloud Shell
Translation_service.translate_textsource codeOpen in Cloud Shell
Quickstartsource codeOpen in Cloud Shell

The Cloud Translation Node.js Client API Reference documentation also contains samples.

Supported Node.js Versions

Our client libraries follow the Node.js release schedule. Libraries are compatible with all current active and maintenance versions of Node.js. If you are using an end-of-life version of Node.js, we recommend that you update as soon as possible to an actively supported LTS version.

Google's client libraries support legacy versions of Node.js runtimes on a best-efforts basis with the following warnings:

  • Legacy versions are not tested in continuous integration.
  • Some security patches and features cannot be backported.
  • Dependencies cannot be kept up-to-date.

Client libraries targeting some end-of-life versions of Node.js are available, and can be installed through npm dist-tags. The dist-tags follow the naming convention legacy-(version). For example, npm install @google-cloud/translate@legacy-8 installs client libraries for versions compatible with Node.js 8.

Versioning

This library follows Semantic Versioning.

This library is considered to be stable. The code surface will not change in backwards-incompatible ways unless absolutely necessary (e.g. because of critical security issues) or with an extensive deprecation period. Issues and requests against stable libraries are addressed with the highest priority.

More Information: Google Cloud Platform Launch Stages

Contributing

Contributions welcome! See the Contributing Guide.

Please note that this README.md, the samples/README.md, and a variety of configuration files in this repository (including .nycrc and tsconfig.json) are generated from a central template. To edit one of these files, make an edit to its templates in directory.

License

Apache Version 2.0

See LICENSE