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:
- Public project – any user may search for the project and join it.
- Private project – project can’t be found via search engines and Crowdin search, only the invited users can join the project.
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.
Save Context Information in the Files
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.
Note: To iOS strings and RESX formats, this option is applied partially (i.e., only the context added in Crowdin will be visible in the downloaded files).
In case your project contains duplicated strings, you can choose how the system should treat them:
- Show – duplicated strings won’t be hidden; translators should translate each string manually.
- Show, but auto-translate them – duplicated strings won’t be hidden, though they will be automatically translated. Once the string is translated, its translation is automatically shared between the duplicates. Translators may review and re-translate those strings if necessary.
- Show (recommended for versions) – duplicates are hidden only across the version branches, so only the new strings will be visible to the translators in the latest branch.
- Hide – duplicated strings won’t be displayed for the translators on the translation page. One-time translation is required, translation of the phrase/word will be automatically applied to its duplicates during export.
Machine Translation Suggestions
When the Show Machine Translation Suggestions option is enabled, machine translation engines such as Microsoft Translator, Google Translate, and Yandex.Translate will be displayed in the Editor. The project owner should configure machine translation engines before using them.
Allow Translators to Create Glossary Terms
If the option Allow translators to create glossary terms is enabled, translators will be able to add new glossary terms to the project. Project owner, managers and proofreaders can always 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.
Note: if this option is enabled, depending on the file format, untranslated strings will be removed from translation files completely (for example Chrome JSON, Android XML, XLIFF) or exported with empty values (for example Generic JSON, QT TS, PO).
- 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 the regional dialects – useful when the project is translated into the language dialects (e.g. Spanish, Argentina). Translations from Spanish will be automatically copied to untranslated strings in Spanish, Argentina during the download.
- Add custom language codes – use custom language codes for the exported translation files. This will keep the exported file structure consistent.
Adding Custom Language Codes
To add language mapping, follow these steps:
- Click Language Mapping.
- Choose the necessary language and placeholder.
- Add custom code.
- You can map as many languages as you need. Click Add Mapping to add another custom code.
- Click Save.
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.
- Enable Auto-Substitution – the feature substitutes the non-translatable elements (such as tags, HTML entities, placeholders, numbers and more) in translations suggested by TM by the ones used in the source text. Improves TM suggestions applied during pre-translation and the ones shown as translation suggestions in the Editor. Improved suggestions are included in the Translation Costs report and the ones that can be improved are included in the Costs Estimation report.
- Use the 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 be also added to the Global Translation Memory, that anyone at Crowdin can have access to.
- 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 about new strings – project managers will receive an email notification about newly added content for translation each time after the update.
- Notify project managers about language translation/validation completion – project managers will receive the notification when some target language (all source files) is fully translated or fully validated.
This option allows you to publish your Crowdin project on your own domain name.
To set up a custom domain:
- Create a necessary domain in the domain name registrar.
- Create CNAME record for this domain name that will be pointed to cname.crowdin.com.
- Go to the Crowdin Project Settings, enter the created domain name into the Custom Domain field, click Update.
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.
Note! This action can't be undone.