ソフトウェア現地語化、毎ループ
ソフトウェア現地語化、毎ループ
ローカライズを遅くさせてはいけません。開発の翻訳でお申し込みは、複数の支店では、シームレスに楽々。エンジニアリングインフラストラ。
文書を参照してください
我々のアプローチ

もちろん、他のローカリゼーションソリューションプロバイダーからの自動化と開発者の親しみやすさについて聞いたことがある。..彼らが通常提供するのは、ファイル転送を自動化し、翻訳ジョブ要求を開始し、翻訳ステータスを確認するAPIです。それはそう2000年代です!せいぜい、GitHubリポジトリへのコネクタは、プリミティブ設定を持っているか、翻訳のためにファイルを選択して送信し、それらをマージして手動でファイ。

Smartcatでは、私たちが提供するのは、以下の原則に基づく真に自動化された連続ローカライズアプローチです:

Maintainable

Localization infrastructure as code. Your entire localization automation can be expressed in configuration files that are written once and which then serve as a single source of truth. Your localization infrastructure is reliable, reproducible and transparent.

Flexible

Multiple source file formats and version control systems. Advanced resource pre- and post-processing. Automatic propagation of translations across language dialects. Automatic generation of translation comments and preview links. Ability to work with any types of project folder and file structures, including working with multiple repositories within one logical translation project.

Reliable and engineer-friendly

No merge conflicts. Ever. You can freely update resource files in repository as translations happen in parallel. In fact, you will never need to worry about any localization files at all, focusing just on maintaining the source language resources, and localized resources will be kept in sync with your changes.

Granular

You are able to choose target languages on a per-project and per-resource file basis, making conscious decisions on what your company needs, and reducing the translation costs.

“Now we can manage our strings just as we manage our code. We can create new branches, merge them, roll them back — and all the while be sure that the Serge–Smartcat bundle does all the background job to get the strings for that specific branch localized in our repo. Works like magic!”

Maxim Kungurtsev

Front-End Developer at Xsolla

Read the Xsolla case study →

Consistent

The features that are usually treated as highly platform-dependent—plural and placeholder support, or pseudo-localization—can be supported consistently across platforms, programming languages, and file formats.

Translation of marketing content is handled the same way as the translation of product strings (though we still have a convenient interface to upload files for one-off translation tasks).

Secure

No proprietary file formats or SDKs. We know you prefer to follow your platform's internationalization best practices whenever possible.

It's up to you whether you want localization automation to run on Smartcat side for convenience or on your side for extra security and resilience. If you choose to self-host your localization automation, your localization infrastructure will be self-sufficient, and your localization files will continue to be updated regardless of the remote API availability.

Transparent

All localization activity goes through the content versioning system (e.g. Git) so it can be audited, backed up and restored.

Adaptable

We respect your development workflow. Using just one development branch or multiple feature branches? Our system supports both options. Yes, even in a free tier.

CI/CD-ready

The entire localization automation is built around your version control server (e.g. Git). As a part of the automation pipeline, we offer built-in pre- and post-processing of localization files to ensure they are ready to be used in your continuous integration builds as is, with no patching on your side.

Faster than agile

Localization files are updated automatically in just several minutes after the source language file is changed. The process works non-stop and requires no supervision. Best part: it unlocks a totally different kind of interaction between engineering, QA and design teams. You can start translating even before delivering the code, or do linguistic and internationalization QA in the context of internal builds.

“Before using Smartcat tools, our translation process consisted of 38 steps — Smartcat helped us reduce this to six! It simplified our process for onboarding new freelancers, and our overall efficiency got a huge boost due to the platform’s Vendor Management features, the Marketplace, and the open API.”

Alexander Markevitch

Localization team lead at Flo Health Inc.

Read the Flo Health case study →

No vendor lock-in

You can own your automation infrastructure. Whatever connectors to external systems you use or develop, they will not be specific to Smartcat proprietary APIs. We know developers hate to migrate data and write code twice, so when we say "no lock-in", we actually mean it.

No data lock-in

At any time you can get your project/translations database in an easy to work with SQLite format, suitable for developing custom reports, export or integration scenarios.

Scalable

1, 5 or 25 languages? Doesn’t really matter. A good automated process makes adding new languages a routine task, introducing virtually no management overhead.

But file processing automation is just a part of the story. Smartcat offers robust automated process management workflows, automated matching with language providers on our thriving marketplace, and full payment automation, making us the only localization platform with such a holistic approach to localization at scale.

Open and affordable

We're big believers in open-source software. Automation technologies and connectors that we build are free and open-sourced. This, combined with an honest free subscription tier, gives you true peace of mind. But if you need a paid or managed support, or want to simplify your payments with multiple vendors, we're here for you.

まだ販売されるか?