Prerequisites
Download access to Lokalise
Excel
Supervisor access to SameSystem
Downloading translations from Lokalise
Start by pressing the Download button in Lokalise:
You will be directed to Lokalise's setup page for downloading files. Make sure of the following:
1. Format is .xlsx (Multilingual Excel)
2. All intended languages are ticked
3a. In Content to export, select Reviewed-only strings.
3b. In Advanced settings, ensure empty translations are not exported.
Note: In Include tags, you can choose to export translations by which tag they belong to in Lokalise.
Important: Do not ever tick the box Include other Project strings. 🙅♀️
4. At the bottom of the page, press Build and download.
The file should be downloaded to your computer shortly.
Preparing the Excel file for SameSystem
Before you can import the file to SameSystem, you'll need to make one small but important change to the Excel file. Simply change cell A1, from KEY to ID, and that's it.
Note: the coloring is just to highlight the cell
Before
After (ready to import)
Importing the file to SameSystem
After the file has been prepared (remember to save it to your computer), you're ready to import it into SameSystem. Head over to the translations page, make sure you're importing the correct type of strings (system strings/help strings) and hit Import.
Select the file you exported from Lokalise and hit the import button. Don't run away just yet though - you must also press the Update button to confirm the imported strings! (If not, the import is ignored 😢 )
Translations will now be processed and updated in the system. Well done 👏
Important until fixed by developers
At the moment, you need to do the same steps for others servers as well. Currently, we have two. To go to the 2nd server (or so-called shard2), you need to select a client located in the other shard or simply click on this link:
Import and update steps are the same.
Good to know
If you forgot to press the Update button after importing the excel file to SameSystem and either closed the window or moved to a different page of the system, you'll have to import the file again and then press Update.
❗ After importing the excel file and hitting the Update button, the translations will be visible after developers will perform a new code release to production servers. Usually, it takes a few hours or a full working day until they are present. For urgent cases, reach out to the #q_and_a_product Slack channel to request further help from a developer.
You can search for string IDs, whole sentences, or part of a sentence in the search field in SameSystem Translations when searching for strings. More on searching below:
Searching for strings 🕵️♀️
When developers create a string, it might be that the English string is changed later once imported to Lokalise.
However, the original text made by the developers will never change the "name" of the string (unless they change it in the backend), meaning, when searching for the edited "Lokalise version" in the SameSystem Translations search field, the original text will show up instead of the text you see in Lokalise. In other words, finding strings can be quite a tricky task 🙃
Our best advice is to find the string ID in Lokalise and search for this instead of words/sentences in SameSystem Translations.
Below you can see we've searched for the word "publish", and we see that ID 1633 was actually named "Released" originally, but later changed to "Published". We had to click on the 1633 string to view the translations to understand that we had found what we were looking for.
Languages
This field lets you search for a string in a specific language:
This field lets you select which languages you wish to see the string translated to:
Untranslated strings
Tick the Untranslated box to only search after strings that have not yet been translated:
Note: Leaving the search field blank will view all untranslated strings.