It is now possible to translate text both in Launcher and in Speeder. This is mainly for resellers who want to sell Speeder to non-English-speaking customers, but you can translate for your own use as well—or to help out other Speeder users.
The syntax for the translation file is exactly the same between Speeder and Launcher (do not include the brackets):
[original text]===[new text]
[original text]===[new text]
[original text]===[new text]
etc.
such as
OK===Aceptar
Cancel===Cancelar
Log Window===Consola
The "original text" must match EXACTLY, including capitalization, punctuation, and spacing.
In Launcher, this will translate buttons, log window text, message box text—almost everything. See the Launcher section below for more information on how to set up the translation file.
In Speeder, this will translate text in the console window. See the Speeder section below for more information on how to translate dynamic text and how to set up the translation file.
Translation files can be encrypted. This is meant to protect your file from particularly invasive anticheats that might try to scan for strings in text files. Normally, anticheats do not scan files that are not open, but they might try to hash the text file or its contents. To encrypt your translation file, use Encrypter, located here. Place the translation file in the same folder as Encrypter, and choose the fourth option.
Launcher
Place all translated text into a file called "translations.ini." Place this file in the same folder as Launcher. If this file exists, Launcher will read it and use it to translate text in Launcher. In this file, write your translations, one per line. That's basically all you have to do. Make sure Launcher is v142+.
Speeder
In config.txt, write the name of your translation file on the appropriate line, such as translations.txt (file extension doesn't matter). The file name should not contain any spaces. Make sure the file is in the same folder as config.txt. In this file, write your translations, one per line.
Speeder can contain a lot of dynamic text. For example, you might see something like
Player animation: 1008
This text cannot be translated in the normal way because it is composed of two 'blocks' of text: "Player animation: " and "1008." Thus, to translate, you will want to use
Player animation: ===Animación del jugador:
Note the space after the colon (: ); this is imperative as the text must match exactly.
I will need to update a lot of the dynamic text to work with the translations because I don't always use the 'block' method. As such, you may notice that some dynamic text cannot be translated. Let me know if there is something in particular you really need translated, and I can fix it.