Smartcat for Developers — Introduction

So, you want to integrate with Smartcat — that's a great place to start. Below you will learn about the available options.

Localizing your software and documentation

When it comes to localizing your code on any platform — Android, iOS, macOS, Windows, Linux, Web — you usually start with keeping your localizable resource files in a version control system, such as Git, Mercurial, or Subversion.

Smartcat offers you a cross-platform command-line tool that you can use to quickly set up your localization automation without having to work directly with our APIs.

We offer the following preconfigured examples:

If you don't find your specific technology in the list, don't worry! Use the generic continuous localization project as a starter (the last link), and tweak the configuration file to deal with your type of content.

Every example project above comes with the documentation on how to install our command-line automation tool named Serge (which stands for String Extraction and Resource Generation Engine), how to configure it, and what commands to use. After providing your credentials and creating a blank project in Smartcat, you will have a working continuous localization workflow that will do the following:

  1. Pull changes from your version control system;
  2. Automatically gather resource files in source language, parse them and send over to Smartcat for translation;
  3. Download translations from Smartcat;
  4. Generate up-to-date localized files and push them back to your code repository.

With this approach, not only you can handle most common localization scenarios, but also implement robust localization pipelines or functionality:

  1. Localize multiple code branches at once;
  2. Generate pseudo-localized resources for all of your projects, regardless of source file formats;
  3. Automatically add clickable links or comments to each translation unit for additional context;
  4. Pre-process and post-process both source and localized files to make sure the final files are ready to be used in your CI/CD processes;
  5. Conditionally include or exclude strings or entire files or folders based on file path or contents;
  6. Specify the list of target languages right within your source language files.

What to do next? Use one of the links above to install and run your first continuous localization project, or continue reading about our automation tool, supported parsers, plugins and configuration settings on serge.io website.

Localizing marketing materials (via Google Docs)

Beside software strings, you typically have random content that goes along with it: App store descriptions, release notes, blog posts, marketing emails and social media campaigns. You can localize them continuously as well, without having to manually upload and download files into Smartcat! What we offer here is our integration with Google Docs where you can collaborate on content in real time and have it translated at the same time!

This integration works on top of the same automation platform we described above.

Check out our blog post for the full description of how Google Docs integration works, and then drop a line to support@smartcat.ai if you want us to enable it for your account.

Custom API integrations

When it comes to specific integration needs not typically related to software localization (integration with your payment systems, notifications, statistics), we offer you a REST API. It provides atomic methods and access to different objects and properties of your account, allowing you to implement the integration exactly the way you need it, and in any programming language.

Continue reading: Getting started with Smartcat API 

Connectors

Smartcat comes with pre-built integrations for certain platforms like Wordpress, Joomla, Drupal, or Zapier. Please refer to the documentation on each connector on how to use and install it.

Continue reading: Integrations

Was this helpful?

7

Similar articles:

    No related articles