Posted by: SConrad
« on: May 10, 2005, 03:57:20 PM »So I can use ~This is a string.~ inside a .baf?
Short version of this thread: Yes. That and %String%.
So I can use ~This is a string.~ inside a .baf?
I think he's saying that he thinks there is no point not tra-ing files, which personally I feel is bollocks. But oh well.Can I hire you as a Gibberish2English translator?
Well, there is no reason at all to use hard strings instead of tranlsation files, so I fail to see where is the problem in hard strings not working, after allI'm not entirely sure what you're talking about, but what I meant is that WeiDU will compile and traify bafs with strings wrapped in %s.
Well, there is no reason at all to use hard strings instead of tranlsation files, so I fail to see where is the problem in hard strings not working, after allI'm not entirely sure what you're talking about, but what I meant is that WeiDU will compile and traify bafs with strings wrapped in %s.
Wrap 'em in %s.Well, there is no reason at all to use hard strings instead of tranlsation files, so I fail to see where is the problem in hard strings not working, after all
Ah, you can't use quotes to enclose the string. Try again with tildes.I, err, umm...
Yes, they do work inside bafs and yes you can traify a .baf.False and false, I just run a test.
IF
True()
THEN
RESPONSE #100
DisplayStringHead(Myself,"Hey this is a new string!")
END
IF
True()
THEN
RESPONSE #100
DisplayStringHead(Myself,0) // ~<NO TEXT>~
END
IF
True()
THEN
RESPONSE #100
DisplayStringHead(Myself,"Hey this is a new string!")
END
Strings don't work inside BAFs, and you cannot traify a baf.
You'll have to use @ in a baf (or use the old cumbersome way of putting placeholder numbers and then using REPLACE)