If you have some existing translations, you can migrate them to your project in Crowdin. Import files with translations from the Project Settings, language page, or open the specific file in the Editor and upload translations from there. The best practice would be to upload translated files with the key-value structure.
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. The system maps uploaded translations according to the string keys.
For the files that do not have a defined structure, translation upload is handled by an experimental machine learning technology. This includes the following file formats: HTML, TXT, Markdown, Generic XML, DOCX, HAML, IDML, DITA, Wiki, and FLSNP. To achieve the best results, we recommend uploading translation files with the same or as close as possible file structure as in source files.
Currently, this feature is available for the following languages (not depending on the language pair combination): Arabic, Chinese Simplified, Chinese Traditional, English, French, German, Italian, Japanese, Korean, Dutch, Polish, Portuguese, Portuguese, Portuguese Brazilian, Spanish, Thai, Turkish, and Russian.
There is a possibility to do the offline translation for all file formats, having downloaded existing content in the XLIFF format. As soon as the offline translations are finished, use the Upload XLIFF Translations.
To upload XLIFF translations for all files for a specific target language, follow these steps:
You can configure the desired system behavior towards the uploaded translations using the available options in the appeared dialog.