Upload and Replace Items on the Documents Ta

Lokalise supports most popular iOS, Android, and Web evolution cord file formats. If yous would similar the states to extend support to a new format or format version, just drop us a line.

Getting started

To become started, click the Upload menu item:

Alternatively you can utilize our CLI, API or GitHub/GitLab integrations to upload the files. Lokalise will match keys and translations from the files where possible.

Before uploading

To upload one or more than files, click Select a file and choose them from your PC. Information technology is as well possible to cull the whole directory. Finally, yous can click Copy-paste data and place file contents into the text box.

Lokalise will detect translation files languages automatically. Certain file formats provide language settings. If not, our system volition use Google Translate detection engine to observe the proper language from translations.

For compatibility reasons, Lokalise will also scan the filenames for language codes (marked in light-green below).

Once the detection is done, review the filenames and detected languages, and make corrections every bit needed. To rename a file, click on it an enter a new name:

In this example Lokalise automatically provided a special placeholder %LANG_ISO% which means "linguistic communication ISO lawmaking". Thus, once you lot export translation keys, the language code will exist inserted properly in the filename.

It is non mandatory to utilize a language lawmaking in filenames, however. If you keep files organized by folders with linguistic communication codes, you tin set the required bundle structure on the Downloads page later.

Upload options

In that location are a scattering of upload options that yous may enable or disable as needed:

• Replace \n with line break — in some programming environments new line in the text is marked with a \due north grapheme. It only means that the text after this character should kickoff with a new line. All the same, it may confuse some interpreters. So it may be a skillful idea to get rid of \n and plow it into line breaks within Lokalise editor. When y'all are going to export translations back, these line breaks can exist replaced with \n once again.

• Convert to universal placeholders — sometimes in your translations you lot may utilize special placeholders to represent a dynamically inserted value. You volition probably desire to store all platform keys in a unmarried Lokalise projection. Even so, each platform (say, Spider web or Android) requires placeholders to be written in a specific manner. Conveniently, Lokalise allows to convert these placeholders into a universal format. When you consign your translation files, these universal placeholders will be replaced back with platform-specific ones.

• Find ICU plurals — ICU is a special library for internationalization. ICU's special format for plurals is widely used for representing word's declension depending on some variable count. If you lot enable this option, Lokalise detects ICU expressions and shows them in the interface. To larn more most ICU message format, delight cheque out our weblog postal service.

• Tag keys — if you would like to tag the afflicted translation keys, enable this option. Choose the existing tags or enter new ones. And so determine which keys should be tagged: inserted (newly created ones), updated (existing ones with the values being updated), or skipped (existing ones that were not modified).

• Differentiate keys by file — enable this option if you lot don't want to merge similar keys from different files. Remember that in Lokalise you are not working directly with the uploaded files. The platform extracts data from your files, parses it, stores it inside the system and exports it on need by generating files again.

• Fill up empty keys with key names — if some keys practise not have whatsoever value yet, the key itself volition act as a value. Y'all may update that value later, of class.

• Hibernate from contributors — if y'all would like to make the newly added keys invisible to the projection's contributors, enable this selection. In this instance the keys volition exist visible to projection admins merely. Later the subconscious keys can be made visible to everyone.

• Custom translation statuses — this choice will become visible only if you have enabled custom translation statuses feature in your project settings. When this pick is checked, yous'll be able to select which statuses should be assigned to inserted, updated, or skipped keys.

• Enable automations — use automations for the uploaded keys. To larn more about automations, delight check the respective documentation.

• Pre-translate with 100% TM matches — while doing translations, you will probably find yourself in a situation when you are starting to translate the same phrases and sentences. Lokalise remembers your translations and analyzes friction match betwixt the text you have already translated and text from the uploaded file. If the system detects a 100% lucifer, it will automatically translate keys in the files you've uploaded.

• Supercede modified translations — suppose you are uploading a translation file which has a handful of translation keys that were already added to the project. Past default, Lokalise uploader will keep the values under such keys intact. Nonetheless, if yous do want to update translations under already existing keys, enable this option.

• Enable cleanup fashion — when this option is enabled, Lokalise will delete all keys with their translations that are not establish in the uploaded file. Be conscientious with this option! Before the upload happens, you lot will exist asked to confirm deletion for extra protection. Delight note that this fashion takes filenames and platforms into consideration. Suppose, your project contains multiple keys assigned to a file named %LANG_ISO%.json and a handful of keys non assigned to whatever filename. If yous upload a %LANG_ISO%.yml file containing new keys, all existing entries will be preserved as they are assigned to a different file (or not assigned to any file at all). However, existing entries assigned to the %LANG_ISO%.yml file will be removed.

Starting the upload

When all filenames and languages wait right, adjust the upload settings and click Import the files. The upload process will be performed in the groundwork so you may navigate to another page. To view the status of your upload click More > Activity in the primary menu.

Agile processes tab lists all the currently running imports and other jobs. You may cancel the process past clicking the Cancel button.

Once the import finishes, the corresponding job volition exist moved under the Finished processes tab.

Click on a procedure to see more details:

• What files were imported.

• How many keys were inserted, updated, and skipped.

• What languages were imported.

• What was the status for each file.

To remove all finished processes from the list, press Clear. Please annotation, that all finished processes older than 48 hours volition be automatically cleared from the list.

Custom language codes

If you are using a custom language code, e.one thousand. sk-SK instead of the standard sk , please practise the following after the upload succeeds:

• Go to your project

• Click on the linguistic communication flag in the top menu

• Choose Linguistic communication settings...

• Enable the Custom language code switch

• Set up the desired language code

Looking for CLI tool upload/download examples? Check out the Filenames commodity.

williamsshave1981.blogspot.com

Source: https://docs.lokalise.com/en/articles/1400492-uploading-files

Share this post