Difference between revisions of "Translating the Big Ones - FCOM, MMM and the like"
Translating the Big Ones - FCOM, MMM and the like (edit)
Revision as of 11:05, 29 March 2011
, 11:05, 29 March 2011no edit summary
imported>Tom Brightblade m |
imported>Tom Brightblade m |
||
| Line 14: | Line 14: | ||
==So let's begin== | ==So let's begin== | ||
After all the texts were extracted from the ESP file (in CS main menu: File -> Export), translated into some language, the only thing remains is to import those texts back to the ESP file (again in CS main menu: File -> Import), recompile all scripts, save the ESP in CS, and then get rid of all unnecessary things that might be added by Construction Set. So once again: | After all the texts were extracted from the ESP file (in CS main menu: File -> [[Export]]), translated into some language, the only thing remains is to import those texts back to the ESP file (again in CS main menu: File -> [[Import]]), recompile all scripts, save the ESP in CS, and then get rid of all unnecessary things that might be added by Construction Set. So once again: | ||
| Line 41: | Line 41: | ||
As we can see, there is an ESP (a plugin, not a master) applied to our MMM for OOO.esp. | As we can see, there is an ESP ([[TES_Files#Esms_and_Esps|a plugin, not a master]]) applied to our MMM for OOO.esp. | ||
| Line 67: | Line 67: | ||
[[Image:TransBig1 04.png|thumb|140px|right|pic. 4: CSE Console logs]] | [[Image:TransBig1 04.png|thumb|140px|right|pic. 4: CSE Console logs]] | ||
OK, we are good to go and load our ESP file in CSE (or CS) to import translated texts. Let's do it: '''open CSE and load the data (our plugin as active file)'''. In the CSE Console window may appear a lot of error messages and warnings (pic. 04). | OK, we are good to go and load our ESP file in CSE (or CS) to import translated texts. Let's do it: '''open CSE and load the [[Data|data]] (our plugin as active file)'''. In the CSE Console window may appear a lot of error messages and warnings (pic. 04). | ||
Note: | Note: | ||