You can configure project settings according to your needs in the Settings tab.
In the Naming section, you can change the project name, add a public description, and display social buttons.
The Privacy section allows you to set preferred privacy settings using the following options:
Project visibility
Require two-factor authentication for all the project members
Select if you want to request project participants to enable two-factor authentication in their Account Settings > Password & Connections tab to access the private project.
Moderated project joining
Select if you want 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 will be able to submit new requests to join translation teams in other target languages.
Allow offline translation
Select if you want to allow translators 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
Select if you want to allow proofreaders to work with hidden strings. Project owner and managers can always work with hidden strings, not depending on the option status.
Embed badges into your website or README to share the localization progress of your project.
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:
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, with the enabled Unify placeholders option, 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, iOS XLIFF, 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, iOS XLIFF, and Android XML formats only.
If the Save context information in the files option 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.
If 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 Allow project members to manage glossary terms option 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.
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.
With the Word count option, 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.
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.
By default, Crowdin uses a predefined set of import and export parameters for each supported file format.
With Parsers configuration, you can change some of these settings according to your needs.
Read more about Parsers configuration.
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, 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.
To add language mapping, follow these steps:
Target File Bundles section allows you to manage bundles for exporting sets of strings in one of the selected formats.
Read more about configuring bundles.
Translation Memory is automatically enabled for each project. Which means that the approved or the latest translation for each string is stored under the project’s Resources > TM.
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.