[TOOL] Tõlge: A tool to help translate Paradox Interactive games

[Svip]

I am looking forward to using this tool in the future, when it is more complete and I have a bit more time to translate to my mother tongue.

Are you planning on adding support for translating mods in the future?

Yes. But right now that is down the line. Right now, each string/message is tied to a patch version. I intend to use this feature to tie it to mods as well (the patch-field is text based rather than an integer/float, so it can use some systems for this; although big mods will probably be recognised as 'games' themselves).

Update: A new term system have been add. Each game will have its own set of terms, which must be defined for each one.

The purpose of terms is for 'fuzzy translations'. To help new translators with terms that have been decided by the community. For instance, if it has been decided that the Danish word for 'Piety' is »Fromhed«, then each time an untranslated message with the word Piety appears, 'Piety' will be already replaced with »Fromhed«.

Terms are defined by their English counterpart. Each language can have versions of the term, and each user assigned to a language can create these terms in the language.

Although, I am considering some permissions for this. For until issues arise in that fashion, I shall remain neutral and restrict it simply.

At a later point, it will be possible to see all instances of where the English (or another language) term appears in a string of its kind and when the current local version of the term does not appear, e.g. every time 'Piety' appears in the English string, when does »Fromhed« not appear in the Danish versions?

But that is a feature for much later.

 

[kemerover]

It would be nice to have possibility to upload .csv files with translations.

 

[Svip]

It would be nice to have possibility to upload .csv files with translations.

That is a good idea. I shall put it up for version 1.1. So expect it within this month.

 

[unmerged(271387)]

So this translates your game from one language to another?

 

[Svip]

So this translates your game from one language to another?

I am not sure what you mean. The idea of this software is to help improve the existing messages as well as translating the games into new languages. But rather than sitting one by one translating thousands of messages, the system allows it to expand for multiple users, as a community driven thing.

Excellent happenings!

The export feature is now working (but it will still require some testing for game compatibility).

The export interface​

Right now, the export feature is a bit resource heavy. It takes about 10 seconds to do (so not too terrible). But it still means I am restricting it to developer accounts as of right now.

Eventually, I intend the generated .csv-files to be made available for all in a dump-directory.

The 'backup language' selection means which language to use in case a message in primary choice language is not translated. Only the four 'official' languages can be selected for a backup language (and it defaults to English).

In case you are wondering what the Patch:-selection means, let me explain. Each string/message is tied to a patch (as I mentioned earlier), which is designed so a developer can upload new strings/messages specific to a patch, so they can download the strings/messages for this patch once translated and only for that patch. They can - of course - also just download all of them.

This will also allow for translators to pick between 'versions' of strings/messages. Although, I do believe that the developers don't make significant changes (significant meaning meaning in the message, not style) to messages, but rather create new code names for those.

 

[Svip]

More news!

And I am double posting to bump the thread for you.

Importing and exporting now works (although reserved for developer accounts for now; importing translations already done is still an outstanding issue). I have tested exporting in Latin1 (UTF-8 available on the export screen per issue #18) and the game loads the new .csv-file without complaints. In fact, I did not have to do anything. Just download and insert.

However, while I am confident that it now works, I still would like you to test this.

Download my recent export (it covers all from text1 through 5) and see if it works by inserting the file in your localisation directory while backing up the other .csv-files (but be sure to move them to another directory, etc.). Hopefully then I can close issue #15.

Once that is cleared, I will work on issue #16 (exported files available for all) and issue #14 (mentioned earlier about importing existing translations).

Update

While issue #15 is still open, I have decided to work on issue #16 regardless and you can now obtain the exported files yourself. However, if you want a file generated, please contact me.

 

[unmerged(101730)]

French has « cousin » (male) and « cousine » (female), German has „Cousin” (male) and „Cousine” (female) (but „Vetter” and „Kusine” would be far more time appropriate) and Spanish has «primo» (male) and «prima» (female).

As for German: Close, but not quite - but then, I expect most Germans to get that one full wrong. With "Vetter" and "Kusine", you're already in the middle of the 18th century.

"Vetternkind" (actually "veter(n)kint" ...) would be a generic cousin of the father's brother ("Vetter") or sister ("Base"), "Vetternson" specifically a male cousin of the father's brother or sister; both were used for the mother's brother's ("Oheim") and sister's ("Muhme") children as well when the distinction didn't make any difference (and most of the time it didn't), else you could use "Oheimskind" and "Oheimson" as well, but that was rare.

tl;dr: Period-accurate German translation for "cousin" should be just "Vetternkind".