You can configure project settings according to your needs in the Settings tab.
For convenient navigation, all project settings are grouped as follows:
In the Details section, you can upload the project logo, change the project name, view the Project ID within your organization, and add a short description.
Originally, you own any project you create in Crowdin Enterprise. You can transfer your project ownership to any other user in the Organization you belong to.
Click Transfer and select the needed user to transfer ownership. New project owner will have access to all project resources and will be able to remove the project.
This option is accessible to project managers, project owner, parent group managers, and organization admins. You can delete the Crowdin Enterprise project with all the translations and related localization resources.
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.
In the Languages section, you can manage your project source and target languages and configure language mapping to use custom language codes.
If you want to change the source language for your project, select a new language from the drop-down list and click Save.
Here are a few points you should be aware of when changing the project’s source language:
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.
Add custom language codes and use them for translation files export. This will keep the structure of exported files consistent.
For example, in the screenshot below two custom codes are set for Greek language. If any of custom placeholders (2 letters, 3 letters codes) is used during file export the file name will include these specific language codes (GK, GEK).
In the Quality Assurance 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.
The project TM is automatically created for each project. Therefore, every approved or last added translation is automatically saved in the project TM.
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 assign and manage the glossaries for your project.
Read more about Glossary.
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:
Regular duplicates detection – when comparing strings, Crowdin Enterprise considers only source texts.
Strict duplicates detection – when comparing strings, Crowdin Enterprise 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.
Read Duplicate Strings article for more details on duplicates management.
You can set the preferred way Crowdin Enterprise should count words in your project. Specifically, it applies to whether HTML tags should be counted as regular words or not. By default, Crowdin Enterprise 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.
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.
With Custom placeholders you can modify a list of placeholders that will be highlighted in the source strings in the Editor.
Read Custom Placeholders article for more details on how to add and work with custom placeholders.
By default, when exporting translations, Crowdin Enterprise fills untranslated strings with source text to avoid exporting empty files.
You can configure export options using the following settings:
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|
Click Advanced Options to add separate export settings for specific project languages.
By default, Crowdin Enterprise 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.