Контекстный перевод для веб-приложений

Crowdin In-Context tool provides an overlay for your application. Translators and proofreaders can translate in context and preview completed translations instantly to see how they will be displayed in your application. You can use In-context for your web applications to help maintain the best translation quality.

In-Context localization is tied up with your Crowdin project, where translatable files are stored. Translations made using In-context will be added to your project the same way as translations made directly in the Editor.

This tool provides a view of your application with editable texts, so the translation process is real-time visible. Таким образом можно переводить даже динамическую часть приложения и заполнители.

Общий обзор

Crowdin In-Context works with the help of a one-line Javascript snippet and pseudo-language package. It creates a pseudo-language package based on the localization files uploaded to your project, which later will be integrated into your application as an additional localization language.

Integrated pseudo-language contains special identifiers instead of the original texts. Thus when switching your app to that language, all labels are converted to special identifiers. Javascript searches for those identifiers and replaces them with editable labels. So, the In-context page of your web app will look the same as your application, with the only difference that translatable strings will be editable.

In-Context View

Translations are made directly in the app, with no need to open the Editor. A simplified version of Crowdin Editor will be displayed, with all the functionality (TM, machine translation, approve/vote option, comments, terms) provided. Thus, it’s easier to make and review translations since translators can preview them in a real context.

In-Context Editor

Интеграция

There are two common approaches to integrate Crowdin In-Context with your application:

  • Staging or translation environment If you are not planning to invite your end-users to help with translations or not considering using a “translation mode” in your production application, integrating Crowdin In-Context to your staging or dedicated translation app environment would be a good solution.

  • Production environment Crowdin In-Context doesn’t require any code changes in your application so that you can use it even on production. You decide how to turn it on and which segment of users will use it. The most common use cases are the following:

    • You can create a mirror website that is a complete copy of your application but under a different URL (for example, instead of crowdin.com it can be translate.crowdin.com), where translators will make translations as if it was your actual application.
    • You can also add In-context as an additional language. So, when translators open your application, they will choose this additional language from the list, which will open In-context for them.

Follow the integration setup guide in your Crowdin project to set up In-context. To check out the guide, open your project and go to Tools > In-Context.

In-Context Tab

Note: If you use CSP, ensure to add the following rules to the policy: for loading the In-Context resource files, for CORS requests to crowdin.com

After the integration is successfully set up and you have refreshed your application, you should see the invitation dialog and Crowdin login box.

Login Window

Необязательные Параметры

You can add these parameters to the _jipt array in the configuration snippet.

Предварительная загрузка строк

_jipt.push(['preload_texts', true]);

Speeds up dynamic content displaying within the In-Context tool by preloading all source strings. Automatically disabled for large projects (5000+ strings). Acceptable values: true, false.

Кнопка перевод всегда видна

_jipt.push(['touch_optimized', true]);

This option is enabled on touchscreens by default and makes the translation button next to each translatable string permanently visible instead of showing on hover. Acceptable values: true, false.

Вызов функции перед коммитом

_jipt.push(['before_commit', function(source, translation, context, language_code) { return status_obj; }]);

Функция для проверки предложения перед коммитом.

Параметры
sourceИсходный текст
translationТекст перевода
contextКонтекст исходной строки
language_codeКод языка перевода (коды языка)
Возвращаемые значения
status_obj Объект. status_obj.status может быть "ок", "ошибка" или "исправлено". В случае ошибки, status_obj.message содержит описание ошибки. Когда статус «исправлен», status_obj.correction содержит исправленный перевод

Вызов функции перед вставкой в DOM

_jipt.push(['before_dom_insert', function(text, node, attribute) { return 'text'; }]);

Функция для преобразования строки перед ее подставлением в DOM.

Параметры
textСтрока для вставки
node
необязательный
DOM element in which the text must be inserted. It may be omitted if the text doesn't have a target element (text inside the browser's pop-ups)
attribute
необязательный
The attribute of DOM element, if the text is part of an attribute
Возвращаемые значения
textСтрока для вставки
falseЕсли функция возвращает false, то DOM не будет обновляться

Вызов функции при закрытии наложения In-Context

_jipt.push(['escape', function() { window.location.href = "http://app_domain.com"; }]);

If defined, users can close the In-Context overlay if they don’t want to translate. Реализуйте эту функцию на вашей стороне. Depending on the In-Context integration approach, it must change the app’s language or redirect from the translation environment to the production app.

Close Login Window

Была ли эта статья полезной?