OFPEC Forum
Editors Depot - Mission Editing and Scripting => OFP - Editing/Scripting General => Topic started by: Doktor Headshot on 18 Sep 2006, 16:59:56
-
Hi all!
It's Guido89 here.
As you may know (by reading my last post inside OFP:E forum) I'm making a mission.
I finished it and I'm scanning it for bugs...
But I'm also translating it in English (when I'm sure it is 100% completed, I would like to translate it in German, French and Spanish).
I almost translate everything but...
There are some texts that seems to be impossible to fix them in the stringtable.csv file.
Theese texts are the ones provided by the TitleText ["mytext","PLAIN DOWN"] command; I know also that I need the localize command and here I need your (appreciated) help: how to combine TitleText and localize? Or does exist another way to reach the goal?
Thanks in advance...
Guido
-
hum - sorry but i can't look into ofp at work
What you could do is: create a mission, using the ingame wizzard.
You find it in multiplayer at map selection screen (not sure wether it's in singleplayer too or not).
Once found, create e.g: a ctf - then open it in editor and you should see in some
triggers or waypoints, how BIS did localize titletexts.
~S~ CD
-
Thanks, I'll try it!
Guido
-
Using the localize command isn't necessary (at least, not on my pc :confused:)
First, create the stringtable.csv and make a few strings.
STR_Example,"This is a test"
Then create a description.ext and include this:
class CfgSounds
{
sounds[] = { STR_Example };
class STR_Example
{
name = "STR_Example";
sound[] = {"\sounds\STR_Example.ogg", db+40, 1.0};
titles[] = { 1, $STR_Example };
};
};
In the mission, use this:
titleText ["STR_Example","PLAIN DOWN"];
Not tested, works with the: unitname say "STR_Example".
-
Cheetah is right that you don't need localize for titletexts, but it is necessary for some commands. Making a mission in several languages is not as easy as it looks. Can't remember the details but will investigate and post examples.
Edit: here we go.
sn1 addaction [localize "STR_ACTION_1", "firstaid.sqs"]
hint localize "STR_SCRIPT_2"
1 setRadioMsg localize "STR_RADIO_1"
_boss globalChat localize "STR_JOIN_2"
I originally discovered this using exactly the technique Chris Death suggested.
-
Thanks both of you Mac Guba & Cheetah, I'll try your suggestions!
Guido