Параметри проекту

You can configure project settings according to your needs in the Settings tab.

Note: Some project settings may be unavailable in string-based projects.

For convenient navigation, all project settings are grouped as follows:

  • General
  • Access
    • Privacy & collaboration
  • Translation
    • Languages
    • Перевірки якості
    • Translation Memories
    • Словники
  • Вміст
    • Import
    • Export
    • Parser configuration

Параметри проекту

General

Ім’я

In the Name section, you can change the project name and add a public description.

Naming

Branding

The custom domain lets you publish your Crowdin project on your own domain name.

To set up a custom domain, follow these steps:

  1. Create a necessary domain in the domain name registrar.
  2. Create a CNAME record for this domain name that will be pointed to cname.crowdin.com.
  3. Open your Crowdin project and go to Settings > General > Branding.
  4. Enter the created domain name into the Custom Domain field and click Update.

Domain

The project logo allows you to customize the appearance of your project’s main page.

Логотип

Badges

With badges, you can share the localization progress of your Crowdin project by embedding them into your website or README.

To embed badges, follow these steps:

  1. Open your Crowdin project and go to Settings > General > Badges.
  2. Enable Display badges.
  3. Copy the badge code using Markdown, HTML, or Image URL.
  4. Paste the badge code on your website or README.

Badges

Видалити проект

This option is accessible exclusively to the project owner. You can delete your Crowdin project with all the translations and related localization resources if necessary.

Note! This action can't be undone.

Видалити проект

Privacy & Collaboration

Project visibility

Set the preferred visibility for your project with the following options:

  • Public project – public projects can be found via search engines and Crowdin search. Crowdin users can join public projects without approval if the Moderated project joining option is disabled.
  • Private project – private projects can’t be found via search engines and Crowdin search. Only the invited users can join the project.

Доступність проекту

Privacy

Configure your project privacy settings with the following options:

  • Require two-factor authentication for all the project members – request project participants to enable two-factor authentication in their Account Settings > Password & Connections tab to access the private project.
  • Moderated project joining – require users to send requests to join the translation team of the preferred language. After the review, a project manager or proofreader can approve or decline the request. After joining the project, multilingual translators can submit new requests to join translation teams in other target languages.
  • Task-based access control – allow project members to work with tasks they are assigned to, even if they do not have full access to the language in the project.
  • Allow offline translation – allow translators to download source files to their machines for offline translation and upload translations back into the project. The project owner and managers can always download sources and upload translations, not depending on the option status.
  • Allow proofreaders to access hidden strings – allow proofreaders to work with hidden strings. The project owner and managers can always work with hidden strings, not depending on the option status.
  • Allow project members to manage glossary terms – allow translators and proofreaders to add new glossary terms to the project. The project owner and managers can always add and edit glossary terms, not depending on the option status.
  • Show machine translation suggestions – enable MT suggestions from machine translation engines such as Microsoft Translator, Google Translate, and others to be displayed in the Editor. The project owner should configure machine translation engines before using them.

Privacy Settings

Сповіщення

Project notifications are disabled by default. Enable the necessary notifications for an agile translation process. Such approach helps to avoid creating additional tasks for every contributor.

  • Notify translators about new strings – translators will receive an email notification about newly added content for translation each time after the update. The Receive emails option should be activated in the translator’s profile.
  • Notify project managers and developers about new strings – project managers will receive an email notification about newly added content for translation each time after the update.
  • Notify project managers and developers about language translation/proofreading completion – project managers will receive the notification when some target language (all source files) is fully translated or fully proofread.

Сповіщення

Languages

In the Languages section, you can manage your project source and target languages and configure language mapping to use custom language codes.

Source Language

If you want to change the source language for your project, select a new language from the drop-down list and click Update.

Here are a few points you should be aware of when changing the project’s source language:

  • Please note that there might be a plural form mismatch for imported strings depending on the new source language. For example, some plural forms might not be displayed in the Editor, or some plural form translations might be used in other ones on translation export. We recommend updating the source files if the new source language has different plural forms than the initial one.
  • If you had an opened browser tab with the Editor during the source language update, you might need to refresh it for changes to take effect and continue translating from the new source language.

Source Language

Target Languages

The Target Languages section allows you to add or remove target languages in your project, copy the target languages list from one project to another, and add custom languages.

Read more about Target Language Management.

Target Languages

Додавання користувацьких мовних кодів

To add language mapping, follow these steps:

  1. Open your project and go to Settings > Languages.
  2. Scroll down to the Add custom language codes section.
  3. Click Language Mapping.
  4. Choose the necessary language and placeholder.
  5. Add custom code.
  6. You can map as many languages as you need. Click Add Mapping to add another custom code.
  7. Click Save.

Зіставлення мови

Перевірки якості

In the QA Checks section, you can manage the types of QA issues to be highlighted in the Editor during the translation process.

Read more about Quality Assurance Checks.

Налаштування ПЯ

Translation Memories

The project TM is automatically created for each project. Therefore, every approved or last added translation is automatically saved in the project TM.

  • Enable Auto-Substitution – the feature substitutes the non-translatable elements (such as tags, HTML entities, placeholders, numbers, and more) in TM translation suggestions with the ones used in the source text. The feature improves the TM suggestions applied during pre-translation and those shown as translation suggestions in the Editor. Improved suggestions are included in the Translation Costs report, and improvable ones are included in the Costs Estimation report.
  • TM Suggestions for Dialects – the feature allows you to display and use TM suggestions from the primary language for dialects if no dialect-specific suggestions are available.
  • Use global Translation Memory – translators will have access to the Global Translation Memory, where all translations from the projects with this feature enabled are stored.

    Note: Once this option is enabled, translations made in this project will also be added to the Global Translation Memory, which anyone can access at Crowdin.
  • TM Match Context Type – the feature allows you to choose what should be considered as string context when suggesting Perfect (101%) match Translation Memory (TM) suggestions. You can choose between the following options:

    • Key and Context – when selected, the system considers both the key and context of strings for suggesting Perfect match TM suggestions. This mode is particularly useful for key-value file formats.
    • Auto – when selected, the system automatically applies the most suitable context consideration mode based on your file format.
    • Previous and next segment – when selected, the system considers the segments immediately preceding and following the current segment for context. Most applicable to HTML-based and other formats without a defined key-value structure.

Translation Memory Settings

TM Pre-translate

In the TM Pre-translate section, you can enable and configure the automatic pre-translation via TM. When enabled, the system will automatically apply translations from your TM in the following cases: when there is newly uploaded content, when target languages change, or after file settings are modified.

You can configure the automatic pre-translation via TM using the following options:

  • Match Ratio – select TM Match type of TM suggestions that should be applied during automatic pre-translation:
  • Approve Added Translations – select whether to approve new translations. Further configure it with the following options:
    • With perfect match – approves only Perfect match translations.
    • With perfect match (approved previously) – approve Perfect match translations that were previously approved.
    • All (skip auto-substituted suggestions) – approve all except auto-substituted translations.
    • All – approve all new translations added during the pre-translation.

Similar automatic pre-translation is also available via MT engines.

Translation Memory Automatic Pre-translation

Penalties

In the Penalties section, you can configure penalties that decrease the match percentage of TM suggestions based on specific conditions. This feature helps when you want to fine-tune the relevance of TM suggestions to your specific requirements.

You can configure the penalties using the following options:

  • Auto-substitution Applied – penalize TM suggestions to which an auto-substitution was applied.
  • Multiple Identical TM Matches – penalize TM suggestions where multiple identical TM matches are found.
  • TM Priority Less Than – penalize TM suggestions that originate from a TM with a priority lower than a specified value. Besides a penalty value, you can also set the preferred TM priority threshold.
    Read more about TM Priority Values.
  • TM Suggestion Last Modified More Than – penalize TM suggestions that were last modified more than a specified number of months ago. Besides a penalty value, you can also set the threshold in months.
  • TM Suggestion Last Used More Than – penalize TM suggestions that were last used more than a specified number of months ago. Besides a penalty value, you can also set the threshold in months.

TM Suggestion Penalties

Assigned Translation Memories

In the Assigned Translation Memories section, you can assign and manage the translation memories for your project.

Read more about Translation Memory.

Пам'ять перекладів

Словники

In the Glossaries section, you can enable the translation of the glossary.

Translate Glossary

In the Assigned Glossaries section, you can assign and manage the glossaries for your project.

Read more about Glossary.

Glossaries Settings

Import

Source Strings

  • Unify Placeholders – if your project contains iOS strings, iOS XLIFF, and Android XML files, you can enable the Unify placeholders option, and the system will transform placeholders into a unified look. For example, Crowdin will make the Android string Hello, %s!, and the iOS string Hello, %@! look in the Editor this way: Hello, [%s]!. This option is beneficial when you work with TM since TM suggestions from iOS strings, iOS XLIFF, and Android XML will be completely interchangeable. Crowdin will transform the translation placeholders back to the original format on export. This option only applies to iOS strings, iOS XLIFF, and Android XML formats.
  • Duplicate Strings – if your project contains duplicated strings, you can choose how the system should treat them using the following options:

    • Show – translators will translate each instance (string) separately. Duplicate strings won’t be hidden.
    • Show, but auto-translate them – Duplicate strings will be automatically translated but will stay visible to translators. Once the string is translated, its translation is automatically shared between the duplicates. Translators may review and re-translate those strings if necessary.
    • Show within a version branch (regular detection) – duplicates will be hidden only between version branches.
    • Show within a version branch (strict detection) – duplicates will be hidden only between version branches.
    • Hide (regular detection) – all duplicates will share the same translation.
    • Hide (strict detection) – all duplicates will share the same translation.

Regular duplicate detection – when comparing strings, Crowdin considers only source texts.
Strict duplicate detection – when comparing strings, Crowdin considers both string identifiers (keys) and source texts.

If your source files contain strings with apparent identifiers (keys), it’s better to use a strict version of the Duplicate Strings options. In other cases, feel free to use a regular one.

Source Strings

Word count

You can set the preferred way Crowdin should count words in your project. Specifically, it applies to whether HTML tags should be counted as regular words or not. By default, Crowdin considers HTML tags as regular words for most of the supported formats, excluding the following ones: HTML, Front Matter HTML, HAML, MD, Front Matter MD, XML, WEBXML, IDML, XLIFF, XLIFF 2.0, ADOC, DOCX, MIF, DITA.

  • Auto (default) – HTML tags will be counted as regular words or skipped depending on the source file format.
  • Count tags – all HTML tags will be counted as regular words.
  • Skip tags – all HTML tags won’t be counted.

When you change the word count option, only newly uploaded words will be counted according to the new settings. So it’s recommended to set the preferred word count settings before uploading source files to the project.

Word count

Export

By default, when exporting translations, Crowdin fills untranslated strings with source text to avoid exporting empty files.

You can configure export options using the following settings:

  • Save context information in the files – the context and max.length added in Crowdin will be visible in the downloaded files. This option only applies to CSV, Android XML, iOS strings, and RESX formats.
    Note: This option only partially applies to iOS strings and RESX formats (i.e., only the context added in Crowdin will be visible in the downloaded files).
  • Skip untranslated strings – only translated strings will be included in the exported translation files.

    This option works in three different ways, depending on the file format. This option is not applied to text-formatted documents since missing texts can make downloaded files unreadable. Others are exported with empty values. And for the third file category, untranslated strings are entirely removed from the exported translation files.

    Option not applied Untranslated strings exported with empty values Untranslated strings removed
    DOCX, IDML, DITA, ADOC, MD, MediaWiki, TXT, HAML, HTML, assets, FM MD, FM HTML, Contentful JSON, SVG JSON (with nested structure), PHP, XLSX, CSV, FJS, RC, XAML, XML, Web XML, TypeScript, JS, TOML, QT TS, i18next JSON, gettext PO, FLSNP, Coffee Android XML, macOS/iOS Strings, Stringsdict, Chrome JSON, JSON (without nested structure), YAML, XLIFF, XLIFF 2.0, ARB, DTD, RRC, GO JSON, Flex, Joomla INI, Maxthon, Java Properties, Play Properties, Java Properties XML, RES JSON, RESW, RESX, SBV, STR, STF, VTT, WXL, VDF, FBT JSON
  • Skip untranslated files – only translated files will be included in the exported translation archive.
    Note: if this option is enabled, it overrides the effect of the Skip untranslated strings option.
  • Export only approved translations – only texts that are both translated and approved will be included in the exported translation files.
  • Automatically fill in regional dialects – useful when the project is translated into the language dialects (e.g., Spanish, Argentina). On export, translations from Spanish will be automatically copied to untranslated strings in Spanish, Argentina.

Export Settings

Parser Configuration

By default, Crowdin uses a predefined set of import and export parameters for each supported file format.

With Parser configuration, you can change some of these settings according to your needs.

Read more about Parser configuration.

Parser configuration

Дивись також

Ця стаття була корисною?