Before uploading your file for translation, please ensure that it's compatible with system requirements. If your file type is not listed below then please contact our localization team for assistance.
Please note: Non-spreadsheet based files that contain comments or instructions for the translators, will not be included in the submission. Your comments may be important, in which case please consider changing your file format so that your comments can be included.
We recommend using a spreadsheet based file (.xlsx, .xls, .csv)
Make sure file is UTF-8 encoded. Use double quote (") characters around each field and comma (,) to separate the fields. If the text contains an actual double quote (") then replace it with two double quotes ("").
"Identifier","English","Description""CaveSpeech_01","It's dangerous to go alone!","Old man speaking""CaveSpeech_02","Take this.","Old man speaking"
#: ../crop-thumbnails.php:35msgid "Globular Clusters"msgstr ""
msgid ""
"It's dangerous to go alone!\n"
"Take this.\n"
msgstr ""
Currently, we DO NOT support GetText PO file that has plural content.
/* Dialogue 1 */"CaveSpeech_01" = "It's dangerous to go alone!";// Dialogue 2"CaveSpeech_02" = "Take this.";
"iOS_String3" = "Thisis a multiline";
"File \"%@\" cannot be opened" = " ... ";"Type \"OK\" when done" = " ... ";"iOS_String5"="This is a \"quote\" "
<?xml version="1.0" encoding="utf-8"?><resources>
<string name="string_name">It's dangerous to go alone!</string></resources>
<?xml version="1.0" encoding="utf-8"?><resources>
<string-array name="string_array_name"> <item>It's dangerous to go alone!</item> <item>Take this.</item>
</string-array></resources>
<?xml version="1.0" encoding="utf-8"?><resources>
<plurals name="numberOfSongsAvailable">
<!--
As a developer, you should always supply "one" and "other"
strings. Your translators will know which strings are actually
needed for their language. Always include %d in "one" because
translators will need to use %d for languages where "one"
doesn't mean 1 (as explained above).
-->
<item quantity="one">%d song found.</item>
<item quantity="other">%d songs found.</item>
</plurals></resources>
{
"CaveSpeech_01": "It's dangerous to go alone!",
"CaveSpeech_02": "Take this." }
"etag" : "\"2f40495373a384b0d85aa37d7723f1dc\""
We DO NOT support extracting in cases of boolean, number, array:
{
"sammy" : {
"online" : true,
"followers" : 987,
"REF_21": [ "Ford", "BMW", "Fiat" ]
}}
<?xml version="1.0" encoding="utf-8"?>
<root>
<data name="CaveSpeech_01" xml:space="preserve">
<value>It's dangerous to go alone!</value>
<comment>Old man speaking</comment>
</data>
<data name="CaveSpeech_02" xml:space="preserve">
<value>Take this.</value>
<comment>Old man speaking</comment>
</data>
</root>
<?xml version="1.0" encoding="utf-8"?>
<root>
<data name="app.name" xml:space="preserve">
<value>Reach a \"total\" of {0} Trophies. Don &apos t change</value>
<comment>Please don't change the name of the application</comment>
</data>
</root>
</xml>
We DO NOT count content in the comments of .RESX file.
<trans-unit id="CaveSpeech_01">
<source>It's dangerous to go alone!</source>
<note>It's not really dangerous</note>
</trans-unit>
<trans-unit id="CaveSpeech_02">
<source>Take this.</source>
<note>Old man speaking</note>
</trans-unit>
<segment id="CaveSpeech_01">
<source>It's dangerous to go alone!</source>
<note>It's not really dangerous</note>
</segment>
<segment id="CaveSpeech_02">
<source>Take this.</source>
<note>Old man speaking</note>
</segment>
Python example code on GitHub for reading and writing string data via LocDirect HTTP API
Amazon Corretto 8 (64-bit) is since April 2019 the recommended version of Java to be used with LocDirect. Versions supported for Windows and macOS can be downloaded from here:
* All downloads of Amazon Corretto 8 can be found here.
LocDirect Mac OS installation instructions
Tip: After the installation you'll find LocDirect under Applications. You can drag the application to the Dock if you wish. You might get the following message when you try to start the application. Then please follow the instructions below:
To allow the application to open, you can do this:
Client versions | Released date | File |
---|---|---|
Client Release Version 2.14.162 | April 12 2021 | |
Client Release Version 2.14.161 | May 19 2020 | |
Client Release Version 2.14.160 | Dec 16 2019 | |
Client Release Version 2.14.159 | Dec 12 2019 | |
Client Release Version 2.14.158 | Apr 24 2019 | |
Client Release Version 2.14.157 | Apr 01 2019 | |
Client Release Version 2.14.156 | Mar 04 2019 | |
Client Release Version 2.14.155 | Mar 01 2019 | |
Client Release Version 2.14.154 | Oct 23 2018 | |
Client Release Version 2.14.153 | May 17 2018 | |
Client Release Version 2.14.152 | Mar 14 2018 | |
Client Release Version 2.14.151 | Jan 26 2018 | |
Client Release Version 2.14.150 | Dec 11 2017 | |
Client Release Version 2.14.149 | Oct 24 2017 | |
Client Release Version 2.14.148 | Sep 20 2017 |
Server versions | Released date | File |
---|---|---|
Server Release Version 2.9.162 (64-bit) | April 12 2021 | |
Server Release Version 2.9.161 (64-bit) | May 19 2020 | |
Server Release Version 2.9.160 (64-bit) | Dec 16 2019 | |
Server Release Version 2.9.159 (64-bit) | Dec 12 2019 | |
Server Release Version 2.9.158 (64-bit) | Apr 24 2019 | |
Server Release Version 2.9.157 (64-bit) | Apr 01 2019 | |
Server Release Version 2.9.156 (64-bit) | Mar 04 2019 | |
Server Release Version 2.9.155 (64-bit) | Mar 01 2019 | |
Server Release Version 2.9.154 (64-bit) | Oct 23 2018 | |
Server Release Version 2.9.153 (64-bit) | May 17 2018 | |
Server Release Version 2.9.152 (64-bit) | Mar 14 2018 | |
Server Release Version 2.9.151 (64-bit) | Jan 26 2018 | |
Server Release Version 2.9.150 (64-bit) | Dec 11 2017 | |
Server Release Version 2.9.149 (64-bit) | Oct 24 2017 | |
Server Release Version 2.9.148 (64-bit) | Sep 20 2017 |