To configure the project settings open your project and choose Project settings at the sidebar menu.
In the Details section, you can change the project name, view the Project ID within your organization, add a short description, and change the project logo.
In the Source strings section, you can change the project source language, enable or disable placeholders unification, and enable or disable the saving of the context and max.length to the downloaded files.
If you want to change the source language for your project, select a new language from the drop-down list.
Here are a few points you should be aware of when changing the project’s source language:
In case your project contains both iOS strings and Android XML files, you can enable Unify placeholders, and the system will transform placeholders into a unified look. For example, with the enabled Unify placeholders option, both Android string
Hello, %s! and the iOS string
Hello, %@! will look in the Editor this way:
Hello, [%s]!. This option is especially useful when you work with TM since TM suggestions from iOS strings and Android XML will be completely interchangeable. On export, the system will transform the placeholders in the translations back to the original format. This option is applied to iOS Strings and Android XML formats only.
If the option Save context information in the files is enabled, the context and max.length added in Crowdin Enterprise will be visible in the downloaded files. This option is applied to CSV, Android XML, iOS strings, and RESX formats only.
In the Translations section, you can manage the duplicate strings, enable or disable machine translation suggestions for the contributors, allow translators to download files for offline translation, allow proofreaders to work with hidden strings, and allow translators to create glossary terms.
In Duplicates section, select how the system should treat the duplicated strings. You can choose one of the following:
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.
Read Duplicated Strings article for more details on duplicates management.
By default, the feature Show machine translation suggestions is enabled. You can disable it and hide machine translation suggestions for the project contributors in the Editor.
If the option Allow Offline Translation is enabled, translators will be able to download source files to their machines for offline translation and upload translations back into the project. Project owner and managers can always download sources and upload translations, not depending on the option status.
If the option Allow proofreaders to access hidden strings is enabled, proofreaders will be able to work with hidden strings. Project owner and managers can always work with hidden strings, not depending on the option status.
If the option Allow project members to create glossary terms is enabled, translators and proofreaders will be able to add new glossary terms to the project. Project owner and managers can always add and edit glossary terms, not depending on the option status.
With the Word count option, 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 new settings. So it’s recommended to set the preferred word count settings before uploading source files to the project.
Translation Memory is automatically enabled for each project. In the Translation Memory section, you can enable Auto-Substitution. The feature increases the benefit of using the Translation Memory (TM) by suggesting translations with a higher similarity match. If you enable the feature, the non-translatable elements (such as tags, HTML entities, placeholders, numbers and more) in translations will be substituted by TM suggestions used in the source text.
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.
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, Crowdin Enterprise uses source texts for the untranslated strings while exporting translations. You can configure export options using the following settings:
Skip untranslated strings
Select if you want to export only translated strings. This option works in three different ways, depending on the file format. For text formatted documents, this option is not applied 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.
In the Target files export section, you can add and configure bundles for exporting sets of strings in one of the selected formats. In simple words, bundles are the translation files that include sets of strings formed based on the specified patterns in the project settings. By default, you can choose from the following three formats: XLIFF, Android XML, and iOS Strings. Additionally, you can add more target file formats by installing respective applications from the Crowdin Marketplace.
The most common use cases are the following:
To configure a bundle, follow these steps:
You can download configured bundles either via your Project home or the Project settings.
To download configured bundles via Project home, follow these steps:
To download configured bundles via the Project settings, follow these steps:
The system will build and download a ZIP archive with folders for each of the project’s target languages containing the translation files of the selected format.
To edit configured bundles, follow these steps:
To delete bundles, follow these steps:
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).
Originally, you own any project you create in Crowdin Enterprise. You can transfer your project ownership to any other user in the Organization to which you belong.
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. If necessary, you can delete the Crowdin Enterprise project with all the translations and related localization resources.