Suggestion for localized versions Scenario compatibility

[Gramphos]

As PTW will make scenarios possible the, already big problem of language compatibility will be even bigger. I therefore suggest that the localized expansions by default come with dual Unit folders; the localized and the English unit names. The English folders only need to contain ini-files refereeing to the localized unit graphics.

[Alanus]

Do you think of a mechanism similar to what was used in CtP / CtP2 ?

Actually, text labels also will be impacted (i.e. those under the "/text" subdirectory) and not only the scenario BIC file.

So yes, the smart thing would be to have a pointer an an .ini file to the directory where the localized scenarii files are located (with probably a compulsary organization of subdirectories).

A smart installer could also resolve this issue for MODs that would be available in more than one language.

[Gramphos]

I don't know of CtP's Mechanism.

[Alanus]

Originally posted by Gramphos
I don't know of CtP's Mechanism.

Well, CtP works as follows, for localized versions :

Both for the standard game, and scenarii (located in a specific directory), contain a game data section in which you can find two subdirectories :
- the “default” one where default files of the English game are,
- the “country” one where localized version of the files are (in my French version = the "country" dir name is ... "French" )

The “country” that you are using is listed in an .ini file at the root of the game directory.

At start-up the game searches for files first in the “country” subdirectory, and for those it couldn’t find, in the “default” directory. For scenario, it searches first in the “country” scenario subdirectory, then the “country” standard directory, then the “default” scenario subdirectory, then the “ default ” standard directory.

So, if you want to make a multi-language scenario, just provide the localized files in as many “country” subdirectories as you want : only the “country” that you are using will be read, the other countries’ files will be ignored (only take space on your HD).

That’s quite simple and it works very well.

But, that’s not the way Civ3 seems to be structured…

[Gramphos]

Well, that was not the way I was thinking. I was just suggesting that they use the current mechanims. Just includes a few folders with ini-files for the standard units.

[Imp. Montezuma]

No, leave English names for unit folders for compatiblity for mods, future patches etc. Need only parsing for *.ini with folowed structure

[default]

Settler=Settler
...
Privateer=Privateer


[french] ; or language ID
language=french
Settler=xxxxx ; something translation
....
Privateer=Fliboustier ; something translation

[german] ; or language ID
language=german
Settler=xxxxx ; something translation
...
Privateer=Pirat ; something translation

....
etc.

first parsed *.ini in Scenarios folder or own \Scenarios\The Mod folder
second parsed *.ini in root folder