If you have some existing translations, you can migrate them to your project in Crowdin Enterprise. Import files with translations from the Project home or open a 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, macOS/iOS Strings, Stringsdict, JSON, Chrome JSON, GO JSON, i18next JSON, FBT JSON, XLIFF, XLIFF 2.0, Java Properties, Play Properties, Java Properties XML, RESX, RESW, RES JSON, YAML, INI, Joomla INI, JS, FJS, PO, TS, QT TS, Blackberry, Symbian, Flex, BADA, TOML, Coffee, DKLANG, XAML, SRT, VTT, VTT2, SBV, SVG, DTD, CSV, RC, WXL, Maxthon, Haml, XLSX, PLIST, PHP, ARB, 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, Front Matter HTML, Markdown, Front Matter Markdown, TXT, Generic XML, Web XML, DOCX, HAML, IDML, DITA, Wiki, FLSNP, MIF, and ADOC. 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 Brazilian, Spanish, Thai, Turkish, and Russian.
To upload multiple files with translations, follow these steps:
To upload a file with translations, follow these steps: