xTranslator finalizing MCM

[Kh47]

First of all, sorry if this is the wrong forum to post this.
Anyway, I started using xTranslator relatively recently and so far I'm good in that the mods I translated either don't have an MCM menu or, if they do, it's inconsequential so I tend to ignore it.

So my question is: how to go about finalizing an MCM translation? I ask because usually the MCM is a file in the .bsa, and of course I avoid touching that.

[IsharaMeradin]

It is totally fine to extract the translation file from the BSA and then translate that file. Just make sure to change the language name in the file name to whatever you are translating to. i.e.

Interface > Translations > SomeMod_English.txt --> SomeMod_Spanish.txt

 

If there isn't a translation file then all the strings are inside the MCM script. Personally, I wouldn't bother with translating those since it would require re-compiling the script. Especially avoid them should you not understand papyrus.

[Kh47]

Thanks.

I have another question though: when I open a pex archive (where usually the mcm strings are, named something like "modmcm"), xTranslator automatically locks the actual scripts and highlights only the actual text that needs translating. When I'm done doing that and getting my translation ready to go, should I finalize and add back to the bsa or it's best not to?

Edited August 15, 2020 by Kh47

[IsharaMeradin]

Any files you change, keep them loose. That way if your translation of a particular mod is limited to the translation file and / or a couple scripts, then you do not need to provide the entire mod. The user can get the original and then apply your translation. This is typically preferred as the end user will then get access to the original mod page where they can learn about any known issues or conflicts with others mods. This would keep translation issues with the translation mod and functional issues with the original mod.

 

That is my personal opinion on the matter.