Here you can manually upload files for localization using various supported formats. Here you can manually upload files for localization using various supported formats. Here you can manually upload files for localization using various supported formats.
If you want to configure an automatic files’ synchronization with your project, use the Integrations tab.
You can set a specific priority for each file by clicking an arrow icon next to the needed file. Then translators will be able to see files sorted according to their priority on the language page and in the Editor.
Files might have the following priorities:
To access the configurations of specific files, right-click on the necessary file or click next to it and then select Settings.
Set more descriptive titles for the files to provide additional details for translators.
Define a file name or full path in the resulting archive, use the available placeholders to indicate the structure of exported content.
For example, you want the source file Overview.csv with Ukrainian translation to be named Overview.ukrainian.csv before integrating it with the application. In this case, you’d need to set the Resulting file after translations export to the following: Overview.%language%.csv.
Some file formats allow you to configure import and export behavior. In this case, file’s Settings dialog will also contain the Parser configuration tab.
Read more about Parsers configuration.
By default, the source files are available for translation into all target languages of the project. Clear the checkboxes next to the languages your file shouldn’t be translated into, and click Save.
Add an additional context or instructions for translators to better understand how to translate a file. You can use either plain text or Markdown. The provided context will be visible to translators in the Editor in the File Context tab.
To change the file’s name, right-click on the necessary file or click next to it and select Rename.
You can check the translation and approval progress for a branch, folder, or file you need. Right-click on the needed branch, folder or file, and select the View progress. To see how many words are translated and approved for each language, hover over the progress bar. To open the selected file in the Editor, click on the needed language. To download translations for the chosen file, select the required languages in the Details tab in the right-hand side menu, and click . Optionally, you can select Preserve folder hierarchy for export to export translation files along with the folders they’re stored in Crowdin Enterprise.
In case you have added some new strings to one of the source files, you’d want to update it to make newly added strings visible to translators. Right-click on the needed file, select Update, and then select the new file on your machine.
If some of the source strings were modified, the system shows a dialog with a list of edited strings. You’ll be able to choose which existing translations you want to keep without changes (Current strings column) and whether you want to keep or remove approvals. The translations for other changed strings will be removed.
Jedes Mal, wenn Sie eine Quelldatei aktualisieren, wird eine neue Version erstellt. To restore your file to the previous revision, click the number on the needed file in the Revision column. In the Revisions tab in the right sidebar, hover over the needed revision and click Restore next to it.
You can create folders and branches in Sources > Files with the following buttons:
Folders represent your content structure, while branches help to manage different versions of the content.
Still, if you need to create branches manually, make sure to upload the master branch first, as all the others will be considered the feature branches. Usually, branches in Crowdin Enterprise are created automatically if you use GitHub, GitLab, or other VCS integration. Duplicates might be managed in Settings > Import > Source Strings by choosing the corresponding option for Duplicates.
You can view all the project’s strings and manage strings settings via Sources > Strings.
If some strings contain data that is not supposed to be translated (e.g. placeholders, other technical entities), you can hide them from translators. To do this:
By default, all source strings of the project are displayed in Sources > Strings. If necessary, you can filter out strings using the available filter options (Issues: All, With unresolved issues, Without unresolved issues; Comments: All, With comments, Without comments; Screenshots: All, With screenshots, Without screenshots; Visibility: All, Visible only and Hidden only) and project labels.
You can add context to the string and set the max. length of the translation.
Once the translation limits are exceeded, the system notifies the contributor that translation should be shorter.
Some file formats allow editing (adding, deleting, and modifying) of the source texts and string identifiers directly in Crowdin Enterprise so you can do the necessary corrections without updating the source file via Sources > Files. Check the full list below:
To edit some particular word or phrase that appears in multiple source strings, you can use the Find and replace feature in Sources > Strings.
Use labels in your project for an easy way to add context to the strings or organize them by certain topics. Labels are also useful while creating translation and proofreading tasks or searching for specific strings in the Editor with the help of Advanced Filter.
To create, edit, or remove project labels, follow these steps:
There are a few possible ways you can add labels to the strings.
Add labels to the source strings in CSV and XLSX files using a dedicated column for labels.
Read more about Configuring Columns for Import for XLSX and CSV Files
File formats like CSV and XLSX might require changing the initially configured scheme. Usually, it might be needed when you add a new target language to your Crowdin project.
Read more about changing the scheme for CSV and XLSX files.