v20.1 QuEIT: Quick Essentials INTL Translator for Essentials 16.1 - 20.1 v1.0.8

Hey, I posted this a year ago on the Spanish community forum but as I saw this could be useful in this community as well, here you are. Quick Essentials INTL Translator, aka QuEIT, is a desktop tool made in C# to translate the INTL file generated from Pokémon Essentials. Do you want to reach Spanish audience? French? Italian? No problem!


QuEIT basically reads the input file and translates it based on massive asyncronous web requests to Google Translator or DeepL (depending on the user configuration). Obviously, those translated phrases are not 100% correct in many cases but it will let you save a huge amount of time (26K text lines take about 5~ minutes on Ryzen 3800X + 32GB RAM and it won't collapse your CPU thanks to parallel threading). As Essentials 20.1 also extracts INTL messages from plugins, you won't need to translate those texts by hand. Essentials 21 extracts the game specific texts and core separately so QuEIT can be used in some cases but future version 1.0.9 will support translating all files in batch.

In the case of Attacks, Abilities, Moves and Pokémon names, PKHex core is used as GNU Public License (related code available on my github). This offers official translations to the names.

Note: DeepL translation requires you to add your own professional key to your config file.

How to use it:

1) First, extract the intl.txt file from your game by using Debug > other options > Extract text (the location of this option might change depending on the version you are using).

2) Open QuEIT by clicking on Quick Essentials INTL Translator.exe (It's windows exclusive as I don't know anybody developing Essentials games on MacOS or Linux. If so, I could support Apple Silicon, Intel 64 and AMD64).

3) Select the languages (from will be usually English and To the desired translated) you want to use in the translation process.

4) Click on Translate. A windows explorer prompt will ask you for the input file (the raw/original/unmodified intl.txt).

5) Let it translate. A new windows explorer prompt will ask you to select the save path for the translated file.

5.1) Check troubleshooting section below.

6) Use Debug > other options > Compile text to compile the intl.dat and set the language to the array in Settings script.

7) Enjoy your game!

Click to expand...

Do you need a 2 minute tutorial about the intl dat file compilation? Check this:



Troubleshooting:

QuEIT is not magic. Problems can occur and it is up to you to check the intl.txt file that is generated. Especially to report bugs. Anyway, if once translated the intl.txt file gives you some problem when compiling, it can be because of:

• Change QuEITconfiguration: If you want to skip the PKHex usage, you can set the configuration in the config.data file located in the Quick Essentials INTL Translator_Data folder (next to the .exe). In this file you can set your pro deepL key and set the translation to DeepL if you don't like Google Translator.
• There are more lines than in the original: Check that both intl.txt files have the same line amount.
• Lines where the one to be translated is different from the one that "serves as reference". Blank characters, special characters (commas, dots...) and capital letters DO matter. "Hello world" is not the same as "Hello, world" nor "hello world".
• Blank/Empty translated lines: This should not happen. However, if the request fails for some reason, an empty translation might occur. This happens with custom names as PKHex database will fail when searching for the "official translation". You are the ones in charge to fix these with your translation. It won't be more than a few lines anyway.
• Non translated lines: If you face non-translated lines in your game it will probably be because those are not using INTL and are not exported to the intl.txt file. Add _INTL to your code to export those and translate them with QuEIT. Other reason could be the previous one. As exception, when a blank line appears, QuEIT tries to fill it with the "reference" line. Follow the steps from the previous one.
• Non-Accurated localization: As said before, this is a translation not a localization. You will need to change badly translated phrases as the translator might not know what are you referring to. Eg: Save can be money or the game and in Spanish, both have different translations (Ahorrar vs Guardar respectively). For those phrases, a keywords.csv file is in Quick Essentials INTL Translator_Data folder with manual translations of specific phrases. You can edit this file on Excel, any text editor (Sublime Text, Notepad ++...). Just keep phrases with commas under quotes, as comma is the separation character. Eg: "Hello, how are you?".
• A debug session is added when clicking on the Pokémon logo. It will ask for permissions on the net. Just accept (so the firewall doesn't block the tool connection). It doesn't affect to anything as it's just a remote logger. If you don't click on the logo, nothing happens.
• After translating my game's inputs stop working: If you are using string keys for bindings, check they are not translated or at least, that they are kept as "non-translated" in the translation files. The keywords.csv will save your time to keep them untranslated.

Click to expand...