You can configure the project settings according to your needs. For this, go to the General tab.
Privacy section allows you to set preferred privacy settings using the following options:
Require Two-Factor Authentication
If the option Require two-factor authentication for all the project members is enabled, project participants should enable two-factor authentication in the Account Settings, Passwords & Connections tab to be able to access the private project.
Languages Access Policy
If the option Limited access to the languages is enabled, translators should send requests to join the translation team of the preferred language. After the review, a project manager or proofreader can approve/decline the request.
Allow Offline Translation
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.
Allow Proofreaders to Access Hidden Strings
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.
In case your project contains both iOS strings and Android XML files, you can enable the Unify placeholders option, 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 will be visible in the downloaded files. This option is applied to CSV, Android XML, iOS strings, and RESX formats only.
In case your project contains duplicated strings, you can choose how the system should treat them:
Regular duplicates detection - when comparing strings, Crowdin considers only source texts.
Strict duplicates 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.
When the Show machine translation suggestions option is enabled, machine translation engines such as Microsoft Translator, Google Translate, and others will be displayed in the Editor. The project owner should configure machine translation engines before using them.
If the option Allow project members to manage glossary terms is enabled, translators and proofreaders will be able to add new glossary terms to the project. Project owner and managers always can add and edit glossary terms, not depending on the option status.
By default, Crowdin uses source texts for the untranslated strings while exporting translations. 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. 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, XLIFF2, 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.
To add language mapping, follow these steps:
Translation Memory is automatically enabled for each project. Which means that the approved or the latest translation for each string is stored under the TM & MT tab.
This option allows you to publish your Crowdin project on your own domain name.
To set up a custom domain:
Upload your logo to customize the appearance of the main page of your project.
This option is accessible only to project owner. If necessary, you can delete your Crowdin project with all the translations and related localization resources.