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:
- 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 Require two-factor authentication for all the project members option 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 Limited access to the languages option is enabled, translators should send requests to join the translation team of the preferred language. Nach der Überprüfung kann ein Projektleiter oder Korrekturleser den Antrag genehmigen oder ablehnen.
Allow Offline Translation If the Allow offline translation option 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 Allow proofreaders to access hidden strings option 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 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:
- Please note that there might be a plural form mismatch for imported strings depending on the new source language. For example, some plural forms might not be displayed in the Editor, or some plural form translations might be used in other ones on translation export. We recommend updating the source files if the new source language has different plural forms than the initial one.
- If you had an opened browser tab with the Editor during the source language update, you might need to refresh it for changes to take effect and continue translating from the new source language.
If 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 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.
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).
If your project contains duplicated strings, you can choose how the system should treat them:
- Show – translators will translate each instance (string) separately. Duplicated strings won’t be hidden.
- Show, but auto-translate them – Duplicated strings will be automatically translated but will stay visible to translators. Once the string is translated, its translation is automatically shared between the duplicates. Translators may review and re-translate those strings if necessary.
- Show within a version branch (regular detection) – duplicates will be hidden only between version branches.
- Show within a version branch (strict detection) – duplicates will be hidden only between version branches.
- Hide (regular detection) – all duplicates will share the same translation.
- Hide (strict detection) – all duplicates will share the same translation.
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.
Allow Project Members to Manage Glossary Terms
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.
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. <table class="table table-bordered">
|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.
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.
Benutzerdefinierte Sprachcodes hinzufügen
Um die Sprachzuordung zu aktivieren, befolgen Sie diese Schritte:
- Click Language Mapping.
- Wählen Sie die gewünschte Sprache und Variable.
- Fügen Sie einen benutzerdefinierten Code hinzu.
- You can map as many languages as you need. Click Add Mapping to add another custom code.
- Klicken Sie auf Speichern.
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.
Anmerkung! Diese Aktion kann nicht rückgängig gemacht werden.