Translation and review
How to choose a language and translation engine in LRPGM
Detect the original language, choose the target, select an engine, and test its connection before translating.
Source language
After extraction, LRPGM groups samples by detected language. In manual mode, review the groups and select only those you want to translate. In Express and some limited access modes, the source can remain Automatic.
Target language
Choose the language the game should use. Review regional variants before processing.
Translation engine
Google provided through LRPGM is the initial option. Bing, Microsoft Azure, DeepL, and DeepLX can appear according to plan and configuration. Some engines require your own API key, credentials, or session.
Before processing a large project, open Settings > Translation, select the engine, enter the requested details, and use Test connection. Formal or casual tone, enhanced context, and network options also appear there when supported.
Which one is best?
No engine is best for every game. Translate a short sample and compare names, dialogue, and consistency. A good glossary and human review often have more impact than switching providers without checking the result.
Related articles
Content that complements this guide and helps with the next steps.
How to choose which game text LRPGM will translate
Configure a simplified or professional scope for dialogue, databases, plugins, structured files, and videos.
Read articleTranslation and connectionLRPGM API or translator error: what to check
Test the connection and verify credentials, plan access, provider limits, and network settings.
Read articleSettingsLRPGM settings: translation, performance, and backups
Learn what to change under General, Translation, Glossary, and Advanced without putting projects at risk.
Read articleAdvanced featuresHow to create a glossary for names and game terminology
Create rules that keep characters, places, items, and recurring expressions consistent.
Read article