5 replies to this topic

[Sir Kalthorine]

The top of my Chrysta setup .tp2 file reads as follows:

BACKUP ~Chrysta/backup~
AUTHOR ~Sir Kalthorine ut Wistan~
BEGIN ~Chrysta NPC Add-on Mod BG2:SoA/ToB v.0.0.2a~

LANGUAGE ~English~
         ~english~
         ~Chrysta/english/chrysta.tra~

COPY ~Chrysta\NatAss\SPCHR101.spl~ ~override\SPCHR101.spl~
SAY NAME1 ~Bless~

COPY ~Chrysta\NatAss\SPCHR102.spl~ ~override\SPCHR102.spl~
SAY NAME1 ~Cure Light Wounds~

...etc.

The subdirectory "english" in the main "Chrysta" folder does exist, and so does the chrysta.tra translation file inside it. But since I added these lines, whenever I try to run the "Setup-Chrysta" WeiDU executable (version 82, and the same file I have used every time so far without any problems) I get the following message:

[CHRYSTA.TP2] PARSE ERROR at line 5 column 1-8
Near Text: LANGUAGE
              syntax error
ERROR: problem parsing TP file [CHRYSTA.TP2]: Parsing.Parse_error

ERROR: Parsing.Parse_error

Press ENTER to exit.

I can't see what I am doing wrong here! And yes I HAVE checked the spelling of "LANGUAGE" at least a dozen times. (line 5 column 1-8 IS the word "LANGUAGE")

I'd really like to know what the problem (and hopefully the solution!) is - I want to start using the .tra files right from the outset for dialog as it seems good practice (particularly as I might want eventually to translate Chrysta into other languages).

[Sir Kalthorine]

LANGUAGE(s) before any BEGIN(s).

And, presumably, "BRAIN(s) before any MODWRITING(s)" would help as well!

I promise that one of these days I will actually ask a question that doesn't have a ridiculously obvious answer. LOL!

[weimer]

Don't sell yourself short here. I would remind you that the TP2 syntax is completely arbitrary.

This bit of the documentation tries to make the order clear:

http://www.cs.berkel...iDU.html#htoc16

with this unhelpful paragraph describing a TP2 file:

BACKUP directoryName AUTHOR emailAddress  [ AUTO_TRA path  ] Language  list [ ALLOW_MISSING file  list ] Component  list

Hopefully this makes it clear that the Language bit comes before the Components (whcih have the BEGINs).

One reason for this is that you may want to provide multiple translations for your component names. "BEGIN @1" is just as common as "BEGIN ~Improved Dragons~". But in order to deal with that, I must already know what the language choices are before I start looking at the components. Kinda.

[weimer]

While we're on the topic ...

COPY ~Chrysta\NatAss\SPCHR101.spl~ ~override\SPCHR101.spl~
SAY NAME1 ~Bless~

COPY ~Chrysta\NatAss\SPCHR102.spl~ ~override\SPCHR102.spl~
SAY NAME1 ~Cure Light Wounds~

Those strings already exist in the default game, so you can just use IEEP or NI to assign them to the SPL files directly and they will work perfectly. You will also get the translations "for free". Another possibility is to use the string references directly:

String #12897 is ~Bless~
String #6620 is ~Cure Light Wounds~

So you could have:

SAY NAME1 #6620

Finally, in my experience you want to set both NAME1 and NAME2 for SPL files, just in case.

[Sir Kalthorine]

Thanks as usual (i.e. above & beyond the call of duty) to weimer & Jason!