The challenge. Game rules depend on official terms, recurring phrases and multi-word expressions. General machine translation can communicate the meaning while missing the game’s established terminology.
My approach. After taking an introductory Python course, I applied what I had learned to my thesis: I analyzed the game’s language, compiled an English–Spanish terminology and phraseology glossary, and coded a prototype translator based on it. Giving glossary entries priority levels, so that longer fixed structures are matched first, helped preserve the game’s set phrasing.
The result. I compared my prototype with the official card translations and with DeepL, Reverso and Google Translate. The prototype kept terminology and fixed phrasing more consistent, while the general engines produced more fluent grammar. A key takeaway for post-editing: the prototype’s grammar errors are easy to spot, whereas a general engine’s terminology errors can hide behind natural-sounding sentences.
What I learned. Bugs like “graveyard” turning into “cementrenio” (the term “enter” was being replaced inside the word) taught me that programming problems in translation are, at heart, textual problems. I had started learning Python from scratch, so carrying the project through to my thesis defense, graded 9.9/10, was a challenge and a path I’m glad I chose.
The GitHub repository also includes the thesis abstract and conclusions in Spanish and English.
Python · introductoryTerminologyCSV resourcesMT evaluation