Поддерживаемые форматы

Crowdin supports a wide range of localization formats, including but not limited to files for mobile, software, documents, subtitles, and graphic assets. Supported file formats and details about custom file formats are listed below and sorted by category.

Мобильные приложения

Локализуйте мобильные приложения на разных устройствах.

Программное обеспечение для ПК

Локализуйте сайты и программное обеспечение для ПК.

Документы, субтитры

Локализуйте свою справочную документацию и субтитры к видео.

Графика и другие ресурсы

Локализуйте изображения, связанные с вашим продуктом, чтобы улучшить пользовательский опыт вашего продукта.

  1. Загрузите графические материалы в Crowdin.
  2. Добавьте всю необходимую информацию для переводчиков, чтобы объяснить как должен выполняться перевод.
  3. Подождите, пока переводчики загрузят локализованные файлы.
  4. Загрузите локализованную графику и используйте ее в производстве.

Converted File Formats

On import, some file formats are automatically converted into other formats to be further parsed and processed. You can see the list of the initial file formats and the file formats they’re being converted into in the table below.

Initial file format Converted file format
DOC DOCX
PPT PPTX
RTF DOCX
PDF DOCX

Индивидуальные услуги

Note: Custom services are available in selected subscription plans or as separately paid add-ons. Check out all pricing options available to choose the most suitable.

Пользовательские файлы форматов

File formats that are not officially supported will be recognized as plain text files (if they have text content) or as graphic assets.

Our team can add special code to support your original file formats and ensure that translators see only translatable texts instead of the whole file content. With this approach, you can manage custom file formats more effectively.

Email Crowdin customer success team at support@crowdin.com to start working with custom file formats in your project.

Пользовательский экспорт файлов

By default, we export the translations in the same format as the source files. For example, if you upload an XML file to Crowdin, you’ll have the XML file exported.
Our developers can make a special processor if you want to configure custom settings for your file export. Some use cases:

  • You manage both iOS and Android applications. With our help, you can upload just one file format (e.g., XML) to Crowdin and then have two different file types (.xml for Android and .strings for iOS) on export.
  • You upload a key-value file that doesn’t support string editing by default and want to modify it directly in Crowdin. We can temporarily convert your file to CSV file format to allow you to add strings online. The exported file will remain in the original format.

Get in touch with our support team at support@crowdin.com, and we’ll gladly help you with setting custom export options based on your needs.

Пользовательские заполнители

Crowdin supports all the placeholders typical for the supported file formats. They are all automatically highlighted in the Editor, so translators know that they shouldn’t be translated. Even if the translator attempts to save translation with some modified or missing placeholder, enabled QA checks will notify the translator about the mistake.

As various file formats allow the creation of custom placeholders, we can also add support for the custom ones you use in your project. To request the support of your custom placeholders – email the Crowdin customer success team at support@crowdin.com

Полезная информация

Была ли эта статья полезной?