Help to use ESP/ESM Translator

[limonotu]

Hello everyone.

I belong to the french community of this site and I occasionally translate some mods that I've really liked.

Until now, it was simple .esp to translate with ESP/ESM Translator (I have the v2.63), with no MCM or Scripts to complicate the task.

But now I want to translate Devious Device Cursed Loot with LOT of scripts and MCM, and I can't figure how Translator works with that.

 

For example:

-I don't know what folders I have to keep in addition to the .esp to treat scripts and MCM.

-When I open the .esp, Translator ask me if I want to open French files or English files, and again just after for MCM files. But when I select french for the first choice, there are many less lines to translate than when I choose english.

-The MCM menu, when I try the mod with some lines translated, doesn't appears in-game, so the mod doesn't works.

 

It is rather sloppy and I can't identify all the problems I encounter. I search someone who knows how to use this program, especially with some complex mods like DD Cursed Loot, to tell me a step by step method.

 

Thanks

[Guest]

To translate the pages of a MCM, the MCM for the mod has to be done in a way that supports translations.

Usually all the "Strings" used inside the MCM can be written as "$someline", and then you have a file in Interface/Translation/modname_ENGLISH.txt, modname_FRENCH.txt, modname_SPANISH.txt, etc.

 

If the mod was not created in a "translatable" way, then the only way is to open its PSC file that implements the MCM and replace the strings inside.

[CGi]

As CPU wrote. The mod needs to use SKSE translations files, what DCL does.
Just open the file Interface\Translations\Deviously Cursed Loot_FRENCH.TXT in an text editor of your choice (but NOT Windows default notepad, as it can change the BOM) and translate. Just make sure to not delete the tab delimiter and possible space chars at the beginning and/or end of entries.

But i know that the program you use offers functionality to translate those files and maintain a database for them, as TESVTranslator does. Maybe you should check the programs description again.

Or you contact Heulsuze, a german translator who uses the same program you do.

[limonotu]

Well, thanks, now I know the Interface folder is really important for MCM.

I think I'll contact Heulsuze for more details on Translator.

 

EDIT: I've just tried to translate the translation file in Interface folder without touching the esp: the MCM is translated. But when I work on .esp and String / Scripts folders, the MCM disapears.

[Guest]

Well, thanks, now I know the Interface folder is really important for MCM.

I think I'll contact Heulsuze for more details on Translator.

 

EDIT: I've just tried to translate the translation file in Interface folder without touching the esp: the MCM is translated. But when I work on .esp and String / Scripts folders, the MCM disapears.

 

The MCM shows the pages checking if the name of the current page to be displayed is something known.

You should check this part of the MCM script to understand if the mod expectes a static string or a translated string.

 

If the page expected is "Config", and you translated the page to "Configuration", then the page will never be shown.

But without looking at the mod MCM code I cannot tell what the problem can be.

 

(Et je parle Frncais, si ca t'interesse.)

[limonotu]

Eh bien j'ai envoyé un mp à Heuluze, je verrais bien ce qui me répond. En attendant je mets ça u peu de côté, merci tout de même pour l'aide déjà apporté !

[Heulsuze]

Have to see, if it's possible to work out the real problem, @limonotu has. Using a program is one part, understanding the basic structure another. I recommended him also to use ModOrganizer, like I do, because it affect the workflow essentially.