Potencius, on Nov 3 2002, 08:27 AM, said:
When I compile, I'd like another source file to be created that looks like this:
IF ~True()~ THEN BEGIN SOURCE01
SAY ~#71345~ ~This is my original source.~
IF ~~ THEN REPLY ~#71346~ ~No, it's not!~ EXIT
IF ~~ THEN REPLY ~#71347~ ~Of course it is.~ EXIT
END
This way, any changes I make to the dialog can be put into the same strref, not wasting any or creating any duplicates if I make a typo or decide that I want to change what it says.
That a little bit more understandable?
Yes, I understand what you are asking for. However, you can already get it with this sequence of commands:
copy dialog.tlk dialog.bak
weidu myfile.d --tlkout dialog.tlk --out override
notice typeo ; edit myfile.d
weidu myfile.d --tlkout dialog.tlk --out override
notice typeo ; edit myfile.d ; all typos now gone
copy dialog.bak dialog.tlk
weidu myfile.d --tlkout dialog.tlk --out override
Quote
DLTC (or even TDD) has not just a bunch of .dlg files which could be recompiled from scratch everytime a typo has been found. They contain 100+ .dlg files, 100+ item files, creatures, and other special string references in various .2da etc. It is impossible to reimport all this stuff.
I'm not sure I agree, but let's just accept this as true for now.
Quote
Therefore recycling of string refs is a must.
WeiDU will already recycle duplicate string refs, but that's not what you want.
Quote
Once a string reference has been allocated, it shouldn't move.
OK.
Quote
When i tried to get rid of the typos in TDD's .tlk file, i found dozens of similar strings, it made my work a nightmare.
:-) The Ascension Translation guys had a similar problem. I highly recommend TRA files for this sort of thing. You could probably also make a utility that scans all in-game files and clear all unused strrefs.
Quote
The same would happen if someone tries to translate a game.
In fact, it already has.
Quote
Unless they always reimport ALL objects. I suppose Max would like a feature (option) which outputs his original source file with ~#~ included in his source (or another copy) whenever one got allocated the first time.
I could do it. I just still don't understand. What is the model here?
Is it that: You already have a KEY/BIFF mod installed and deployed for many users. You notice some typos. You want to put out a
WeiDU "patch" that fixes those typos?
Is it that: You are still developing in-house. You have a big KEY/BIFF mod ... but you are also using
WeiDU ... I can't guess.
My apologies if I'm appearing dense here. I can see how to add this feature to
WeiDU. Since there are two of you who want it, it should get in ... assuming that it is actually necessary/useful. Why is what I suggested (just restore a good pre-dialogues dialog.tlk before your final DLG compilation or before you add any new items, etc.) not sufficient?
By the way, do you have a webpage for your project?