Difference between revisions of "TLK"
From Dragon Age Toolset Wiki
Dutch Master (Talk | contribs) (Make sure the string is 20 characters long, with 2 spaces.) |
Dutch Master (Talk | contribs) (Information about the representation of String data.) |
||
Line 34: | Line 34: | ||
*4 bytes | *4 bytes | ||
− | ** | + | ** Unsigned 32 bit integer, little endian - number of characters in string. |
− | *String in | + | ** The toolset seems to ignore this. |
+ | *String in UTF-16, little endian. | ||
+ | ** Terminated by a NUL character (0x00) and filled up to be a multiple of 4 bytes. |
Revision as of 01:46, 7 January 2010
These GFF files contain strings. They can be opened in the GFF editor.
Keep in mind that all numbers are in little-endian format if you are looking at the raw file.
This may be incomplete, as I believe previous TLK files had timing info, etc as well.
A cursory glance at the file leads me to believe it's formatted something like this:
Header
String ID section
String data section
Header
- 104 bytes
- 20 byte string describing the file, watch the 2 spaces between PC and TLK
GFF V4.0PC TLK V0.2
- 80 bytes of other info I haven't figured out yet. May include info about the table, offsets
- 4 bytes - number of entries in the table
- 20 byte string describing the file, watch the 2 spaces between PC and TLK
String ID section
Tightly packed
- 4 bytes
- unsigned 32 bit integer - TALK_STRING_ID
- 4 bytes
- unsigned 32 bit integer - offset to string (appears to be an offset from 0x60)
String Data
- 4 bytes
- Unsigned 32 bit integer, little endian - number of characters in string.
- The toolset seems to ignore this.
- String in UTF-16, little endian.
- Terminated by a NUL character (0x00) and filled up to be a multiple of 4 bytes.