People you invite to a project won’t have access to all the project steps and resources by default. After you add people to your project, you can give them manager access, or assign to project steps and languages as contributors. Managers will have access to all the project steps. Translators and proofreaders will be able to access only the steps they were assigned to.
To invite people, open your Project page, select Translations > Members on the left. Дізнатися більше
Each project in Crowdin Enterprise has a workflow with separate steps for translation and proofreading. You can assign people to steps and target languages in your workflow template or you can assign them after you add a workflow to your project.
One more option to give a person access to a specific language or languages is to invite a person directly to the project (Project Page, User Management tab). When inviting people to a project you can give them access to all workflow steps and languages or select specific ones.
To check all the project activities, open Project Page and using the left-hand navigation go to Translations > Activities. Use filters to find activities of specific types, related to specific people, or languages.
You can also go to Translations > Reports, Project Summary section to see a progress timeline for translation and proofreading, as well as to check when the source strings were added, deleted, or updated.
If you have some existing translations, you can upload them from the Project Page. Open the menu in the upper right corner and choose Upload translations.
You can easily upload translations for the source files with a key-value structure. This includes the following file formats: Android XML, iOS Strings, StringDict, JSON, Chrome JSON, YAML, INI, RESX, PO, TS, CSV, XLSX, PHP, XLIFF, RC, VDF.
For the files that do not have a defined structure (such as HTML, Plain Text, Markdown, OpenOffice, Microsoft Office, Adobe InDesign, Adobe FrameMaker, Generic XML) we do not recommend uploading your existing translations in the same file format. As the structure of the source and translated files might not match.
QA checks are the automatic checkup of all the translations against a set of rules such as translation consistency, spacing consistency, proper spelling, and more. You can find the list of all the QA checks parameters and enable the necessary ones in the Projects Settings, Quality Assurance Settings section. If a QA check issue is detected in a translation, proofreaders will be able to see it in the proofreading mode. Докладніше
Every project in Crowdin Enterprise has its own workflow. You can assign people to translate or proofread specific languages at each workflow step and live without manual task management.
If you need to split big files between translators or assign files to particular people, you can create tasks within your project. Using the left-hand menu on the Project Page, navigate to Translations > Tasks to create, assign, and manage project tasks. Докладніше
Crowdin Enterprise has VCS Integrations, provides a RESTful API and has a CLI, so you could integrate localization in the development process of your company. You can also configure Webhooks for the key events in Crowdin Enterprise.
Crowdin Enterprise provides a RESTful API. With the API you can add and update files, download translations, create projects, upload translation resources, create webhooks, and more.
You can also manage and sync your localization resources with the Crowdin project using an easy-to-use Command line tool (CLI).
To generate project reports, go to the Project Page, using the left-hand menu navigate to Translations > Reports. You can access the following types of reports:
Cost estimate – if you already know the rates of your translators, proofreaders, or vendors you can generate this report in advance to find out the approximate future localization cost.
Translation cost – with this report you’ll see how much you should pay your project translators, proofreaders, and vendors. The report shows the real expenses on translation and proofreading.
Top members – this report will be useful if you have a community engaged in the translation. Keep track of the most active members and reward them for their efforts.
The Reports section also includes charts with a project overview and information on project size, translation, proofreading activities, and more. Докладніше
Translation Memory (TM) and Glossary files are created automatically for each project. New records will be added to the Translation Memory as soon as project members start making translations. Glossary file will be empty, so you should either add terms manually from the Glossary tab or upload a file with your project’s terminology.
You can upload Translation Memory in TMX, CSV, or XLSX file formats and Glossary in TBX, CSV, or XLSX formats.
Go to your organization Workspace to upload localization resources directly to your organization and then simply enable them in the corresponding projects.
Your project might contain duplicate strings, especially if you’re translating several branches. A master string is a string that was added to the project first, regardless of which branch this string belongs to. A string becomes a duplicate if the same string was already added to the project. If you decide to auto-translate duplicate strings they will share the translation of a master string.
In Project Settings you can choose how Crowdin Enterprise should handle the duplicates:
Show – Translators will translate each duplicate separately
This option is enabled by default. Use it when duplicates are used in a different context and thus should be translated differently.
Show, but auto-translate them
Duplicates will be shown in the Editor but will be auto-translated once the source string is translated. This option is used in rare cases when some duplicates need to have unique translations and the others should be auto-translated.
Note: If the master string has no translations, duplicates won’t be auto-translated.
Show within a version branch – duplicates will be hidden only between version branches
All the duplicates within your master branch will be visible and translated separately. The duplicates in the version branches will be hidden and auto-translated.
Both Show within a version branch and Hide options are available in two versions: regular duplicates detection, strict duplicates detection. If your source files contain strings with apparent identifiers (keys), it’s better to use a strict version of the option. In other cases, feel free to use a regular one.
You can make particular strings hidden from translators if, for example, there’s no need to translate a string or it should be translated later after the release.
To hide a string, go to Project page and navigate to Content > Strings. You can hide all strings in a file or search for a specific string.
You can also make strings invisible from the Editor, Translation mode. In the top middle area open the menu and click Hide string. When the hidden strings are ready for translation or proofreading, you can use the filter to find them in the Editor and make these strings visible again.