Localization of MCM

[PJMail]

I have trawled but can't find a program that does this (like FO4Edit does for ESP's).

I know how MCM localization works, I just don't want to have to replace EVERY string in the MCM menu with a $variablename, and fill in the modname_en.txt file by hand. Call me lazy, but that is what programs are for... Fighting google translate afterwards is enough work thank you.

[PJMail]

Well, no answers so I used what I could find. For those who are interested, the Simple Json Translator mod can be repurposed.

Open up your MCM json in it and all the entries you need to 'localize' are listed.

You can 'select all' and copy them into notepad to turn them into the 'tags' you will use in place of the strings.

Keep this original 'English' list for later. With a copy of this list you need to turn those lines into the tags.

I just removed the spaces/non-numeric characters and placed a $modname_ in front of them all.

You can then "select all", copy, then 'paste' the entire list back into the json translator you still have open and they will go as the 'replacement text'.

Then just save the json back. It is now 'localized'.

Next you need to make languages file you put in data\interface\translations directory. Obviously the first one will be the english one you already have.

These files are of the form modname_xx.txt (xx is the language - normal rules bethesda use - fr = french, es = spanish, en = english etc).

They consist of the 'tags' you created (one per line), followed by a tab, then the translation text.

For this I used Excel as I can just 'copy' the entire tag list and 'paste' it into the first column, then do the same for the original english (that I first copied out of the Json tool) into the second column.If all goes well they will line up.

You then just 'save as' the resulting spreadsheet as a tab delimited unicode txt file (exactly what is needed) as the approriate modname_en.txt.

 

To do the other languages I just pasted the entire english list into google translate and then copied the resuting translated list and used that in a repeat of the above 'excel' trick to make the other language files.

 

Done in less than 1 hour.

 

Note. You can't put those translation files into your BA2 (they have to be loose) - you will end up with an MCM menu full of $variables (I tried it). Shame...

Edited January 27, 2021 by PJMail