Puoi configurare le impostazioni del progetto secondo le tue esigenze nella scheda Impostazioni.
For convenient navigation, all project settings are grouped as follows:
In the Name section, you can change the project name and add a public description.
The custom domain lets you publish your Crowdin project on your own domain name.
To set up a custom domain, follow these steps:
cname.crowdin.com
.The project logo allows you to customize the appearance of your project’s main page.
With badges, you can share the localization progress of your Crowdin project by embedding them into your website or README.
To embed badges, follow these steps:
This option is accessible exclusively to the project owner. You can delete your Crowdin project with all the translations and related localization resources if necessary.
Set the preferred visibility for your project with the following options:
Configure your project privacy settings with the following options:
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.
In the Languages section, you can manage your project source and target languages and configure language mapping to use custom language codes.
If you want to change the source language for your project, select a new language from the drop-down list and click Update.
Here are a few points you should be aware of when changing the project’s source language:
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.
To add language mapping, follow these steps:
In the QA Checks section, you can manage the types of QA issues to be highlighted in the Editor during the translation process.
Read more about Quality Assurance Checks.
The project TM is automatically created for each project. Therefore, every approved or last added translation is automatically saved in the project TM.
Use global Translation Memory – translators will have access to the Global Translation Memory, where all translations from the projects with this feature enabled are stored.
TM Match Context Type – the feature allows you to choose what should be considered as string context when suggesting Perfect (101%) match Translation Memory (TM) suggestions. You can choose between the following options:
In the TM Pre-translate section, you can enable and configure the automatic pre-translation via TM. When enabled, the system will automatically apply translations from your TM in the following cases: when there is newly uploaded content, when target languages change, or after file settings are modified.
You can configure the automatic pre-translation via TM using the following options:
Similar automatic pre-translation is also available via MT engines.
In the Penalties section, you can configure penalties that decrease the match percentage of TM suggestions based on specific conditions. This feature helps when you want to fine-tune the relevance of TM suggestions to your specific requirements.
You can configure the penalties using the following options:
In the Assigned Translation Memories section, you can assign and manage the translation memories for your project.
Read more about Translation Memory.
In the Glossaries section, you can enable the translation of the glossary.
In the Assigned Glossaries section, you can assign and manage the glossaries for your project.
Read more about Glossary.
In the Machine Translation section, you can manage the following MT-related settings:
Show machine translation suggestions – enable MT suggestions from machine translation engines such as Microsoft Translator, Google Translate, and others to be displayed in the Editor. Il proprietario del progetto dovrebbe configurare i motori di traduzione automatica, prima di usarli.
Enable MT Pre-translate for new content – enable and configure the automatic pre-translation via MT. When enabled, the system will automatically apply translations provided by the selected MT engine in the following cases: when there is newly uploaded content, when target languages change, or after file settings are modified.
You can configure the automatic pre-translation via MT by selecting the preferred MT engine and specifying all or selected project languages.
Similar automatic pre-translation is also available via TM.
In the AI Prompts section, you can configure AI Prompts for your project.
Before the AI Prompts can be configured in the Project Settings > AI Prompts, it’s also necessary for the project owner to configure the AI Providers.
Read more about Crowdin AI.
Hello, %s!
, and the iOS string Hello, %@!
look in the Editor this way: Hello, [%s]!
. This option is beneficial when you work with TM since TM suggestions from iOS strings, iOS XLIFF, and Android XML will be completely interchangeable. Crowdin will transform the translation placeholders back to the original format on export. This option only applies to iOS strings, iOS XLIFF, and Android XML formats.Duplicate Strings – if your project contains duplicated strings, you can choose how the system should treat them using the following options:
Regular duplicate detection – when comparing strings, Crowdin considers only source texts.
Strict duplicate 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.
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 the new settings. So it’s recommended to set the preferred word count settings before uploading source files to the project.
By default, when exporting translations, Crowdin fills untranslated strings with source text to avoid exporting empty files.
You can configure export options using the following settings:
Skip untranslated strings – only translated strings will be included in the exported translation files.
Quest’opzione funziona in tre modi diversi, a seconda del formato del file. Quest’opzione funziona in tre modi diversi, a seconda del formato del file. Gli altri sono esportati con valori vuoti. And for the third file category, untranslated strings are entirely removed from the exported translation files.
Opzione non applicata | Stringhe non tradotte, esportate con valori vuoti | Stringhe non tradotte rimosse |
---|---|---|
DOCX, IDML, DITA, ADOC, MD, MediaWiki, TXT, HAML, HTML, assets, FM MD, FM HTML, Contentful JSON, SVG | JSON (con struttura nidificata), 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 (senza la struttura nidificata), 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 |
By default, Crowdin uses a predefined set of import and export parameters for each supported file format.
With Parser configuration, you can change some of these settings according to your needs.
Read more about Parser configuration.