Overview
This guide will show you how to make your own translations or edit existing texts for Shortest Trip To Earth, be it different version of English or some other non-English language. New languages appear in-game in the drop-down menu.
Disclaimer
Interactive Fate OÜ reserves the right to remove any translations of Shortest Trip To Earth that it deems inappropriate, regardless of language of origin. If you are concerned that a translation should be reported for content, please email: info at interactivefate dot com with the words “Translation Violation” in the subject line, and include a link to the problem translation with explanation.
We thank you for your enthusiasm for the game and your help in supporting great translations for Shortest Trip To Earth.
– Shortest Trip team
1. Downloading tools:
– Download SteamCMD from:
[link]
– Follow the instructions for your OS exactly!
2. Creating the translation:
– Subscribe to “Translation template” workshop item. It downloads the “localization.tsv” file and other localization files into “C:/Program Files (x86)/Steam/steamapps/workshop/content/812040/” folder. (if your steam library is in some other folder, then look there).
– Copy everything in that file to Google Sheets for editing.
3. Editing the translation:
– Enter the name of your language, right next to “:displayName“.
– If the language you’re translating to uses different plural forms compared to English then :mozillaPluralRuleNumber needs to be changed too.
– Write translations to the “translation” column on the right. “maxlen” is a hint how many characters fit nicely in the UI. Too long translations may be clipped or can result in tiny text. When 0, there’s usually enough room and there is no need to edit translation into a shorter variant.
– Some text lines contain control characters like n for newline. It is recommended to preserve these in translated texts. All empty lines without these control characters will be removed.
– Often times there are places like {1} or {0} these are replaced in-game with variable values, number refers to value, you can change the order of these in text. Sometimes there are things like {1:+0;-0;+0} or {0:0.00}, these are also variables, but in different format, latter is a numeric value with comma for example.
– To test a translation, export it from Google Sheets using “File->Download as…->Tab separated values” into “Mods/Translation english/localization.tsv” in the game installation folder (note that “Mods/Translation english/” folder must be created).
– From now on when a game is started, the English translation should be available in the language dropdown in the game menu.
Note: Localization file name is not important. For the game to load it, it only needs to have a tsv extension. This way one Steam Workshop item can contain many languages and for many DLCs or other mods.
4. Publishing the translation:
– Create a new plain text file (Notepad on Windows, TextEdit on OSX).
Note: In TextEdit, go to Edit->Substitutions and disable Smart Quotes
– Copy paste the following into the file:
“workshopitem”
{
“appid” “812040”
“visibility” “0”
“title” “INSERT_TITLE_HERE”
“description” “INSERT_DESCRIPTION_HERE”
“previewfile” “INSERT_PATH_HERE”
“contentfolder” “INSERT_PATH_HERE”
}
– Replace following values with ones corresponding to your item:
– “title”, which is the title that will be seen on the Steam Workshop page.
– “description”, which is the description that will be seen on the Steam Workshop page.
– “previewfile”, which is the full path of a .JPG or .PNG image that will be shown on the Steam Workshop page. Ideal image dimensions is 636x358px for landscape format.
– “contentfolder”, which is the full path of the folder to file(s) you created.
EXAMPLE:
“workshopitem”
{
“appid” “812040”
“visibility” “0”
“title” “Title for the item”
“description” “Description of the item”
“previewfile” “C:/Program Files (x86)/Steam/steamapps/common/Shortest Trip to Earth/Mods/Translation english/image.png”
“contentfolder” “C:/Program Files (x86)/Steam/steamapps/common/Shortest Trip to Earth/Mods/Translation english/”
}
– Save the text file as a .vdf file, NOT as a .txt file.
– If on Windows, open a command prompt window and type the following command, replacing STEAM_USERNAME and STEAM_PASSWORD with your account name (not display name!) and password:
C:steamcmdsteamcmd.exe +login STEAM_USERNAME STEAM_PASSWORD +workshop_build_item PATH_TO_VDF_FILE +quit
– If on OSX, open a terminal window and type the following command, replacing STEAM_USERNAME and STEAM_PASSWORD with your account name (not display name!) and password:
~/steamcmd/steamcmd.sh +login STEAM_USERNAME STEAM_PASSWORD +workshop_build_item PATH_TO_VDF_FILE +quit
Note: You may need to enter a Steam Guard code that Valve will send to your account’s email address.
Note: Sometimes when using Steam through CMD, you have to re-login to main client.
5. Updating an existing workshop item:
– Open the .vdf file for updated translation, and update the title, description, and paths if necessary.
– An entry called “publishedfileid” should have been added automatically, do NOT change it.
– Optionally, you can add an entry called “changenote” before the } at the end, and add a message to accompany this update.
– Save the file and follow the same steps, using SteamCMD, as in publishing a new workshop file as described in section 4.
Troubleshooting
In case of problems, it is best advised to reach out in forums first. Often times you can get answers from community faster than asking directly from developers.
You can also reach out in Discord[discord.gg]!
If you have any questions about this document, please email info at interactivefate dot com