https://datoolset.net/mw/api.php?action=feedcontributions&feedformat=atom&user=Dutch+MasterDragon Age Toolset Wiki - User contributions [en]2026-04-10T08:17:11ZUser contributionsMediaWiki 1.25.6https://datoolset.net/mw/index.php?title=TLK&diff=12838TLK2010-04-08T17:54:18Z<p>Dutch Master: clarify the string termination</p>
<hr />
<div>These [[GFF]] files contain strings. They can be opened in the GFF editor.<br />
<br />
Keep in mind that all numbers are in little-endian format if you are looking at the raw file.<br />
<br />
This may be incomplete, as I believe previous TLK files had timing info, etc as well.<br />
<br />
A cursory glance at the file leads me to believe it's formatted something like this:<br />
<br />
'''Header'''<br />
<br />
'''String ID section'''<br />
<br />
'''String data section'''<br />
<br />
----<br />
<br />
'''Header'''<br />
<br />
*104 bytes<br />
**20 byte string describing the file, watch the 2 spaces between PC and TLK <pre>GFF V4.0PC TLK V0.2</pre><br />
**80 bytes of other info I haven't figured out yet. May include info about the table, offsets<br />
**4 bytes - number of entries in the table<br />
<br />
'''String ID section'''<br />
<br />
Tightly packed<br />
<br />
*4 bytes <br />
**unsigned 32 bit integer - TALK_STRING_ID<br />
*4 bytes<br />
**unsigned 32 bit integer - offset to string (appears to be an offset from 0x60)<br />
<br />
'''String Data'''<br />
<br />
*4 bytes<br />
** Unsigned 32 bit integer, little endian - number of characters in string.<br />
** The toolset seems to ignore this.<br />
*String in UTF-16, little endian. <br />
** Terminated by a NUL character (0x00) (twice, since it is UTF-16LE) and filled up (with 0xff) to be a multiple of 4 bytes.<br />
<br />
<br />
[[Category:File types]]</div>Dutch Masterhttps://datoolset.net/mw/index.php?title=User:Dutch_Master&diff=9842User:Dutch Master2010-01-16T21:13:54Z<p>Dutch Master: initial</p>
<hr />
<div>= Dutchy =<br />
== About Me ==<br />
<br />
I am Edwin Smulders, a computer science student from The Netherlands. I have done some research on the TLK format and other file types for the toolset.<br />
I am currently involved with writing converters for the BG 2 Redux[http://bgr.gamersnexus.net] project.<br />
<br />
== Software ==<br />
Please contact me for any software I've written related to the toolset if you are interested.<br />
<br />
== Stuff ==<br />
- Language: Java<br />
- Music: Metal</div>Dutch Masterhttps://datoolset.net/mw/index.php?title=TLK&diff=9367TLK2010-01-07T00:46:55Z<p>Dutch Master: Information about the representation of String data.</p>
<hr />
<div>These [[GFF]] files contain strings. They can be opened in the GFF editor.<br />
<br />
Keep in mind that all numbers are in little-endian format if you are looking at the raw file.<br />
<br />
This may be incomplete, as I believe previous TLK files had timing info, etc as well.<br />
<br />
A cursory glance at the file leads me to believe it's formatted something like this:<br />
<br />
'''Header'''<br />
<br />
'''String ID section'''<br />
<br />
'''String data section'''<br />
<br />
----<br />
<br />
'''Header'''<br />
<br />
*104 bytes<br />
**20 byte string describing the file, watch the 2 spaces between PC and TLK <pre>GFF V4.0PC TLK V0.2</pre><br />
**80 bytes of other info I haven't figured out yet. May include info about the table, offsets<br />
**4 bytes - number of entries in the table<br />
<br />
'''String ID section'''<br />
<br />
Tightly packed<br />
<br />
*4 bytes <br />
**unsigned 32 bit integer - TALK_STRING_ID<br />
*4 bytes<br />
**unsigned 32 bit integer - offset to string (appears to be an offset from 0x60)<br />
<br />
'''String Data'''<br />
<br />
*4 bytes<br />
** Unsigned 32 bit integer, little endian - number of characters in string.<br />
** The toolset seems to ignore this.<br />
*String in UTF-16, little endian. <br />
** Terminated by a NUL character (0x00) and filled up to be a multiple of 4 bytes.</div>Dutch Masterhttps://datoolset.net/mw/index.php?title=TLK&diff=9366TLK2010-01-06T22:09:08Z<p>Dutch Master: Make sure the string is 20 characters long, with 2 spaces.</p>
<hr />
<div>These [[GFF]] files contain strings. They can be opened in the GFF editor.<br />
<br />
Keep in mind that all numbers are in little-endian format if you are looking at the raw file.<br />
<br />
This may be incomplete, as I believe previous TLK files had timing info, etc as well.<br />
<br />
A cursory glance at the file leads me to believe it's formatted something like this:<br />
<br />
'''Header'''<br />
<br />
'''String ID section'''<br />
<br />
'''String data section'''<br />
<br />
----<br />
<br />
'''Header'''<br />
<br />
*104 bytes<br />
**20 byte string describing the file, watch the 2 spaces between PC and TLK <pre>GFF V4.0PC TLK V0.2</pre><br />
**80 bytes of other info I haven't figured out yet. May include info about the table, offsets<br />
**4 bytes - number of entries in the table<br />
<br />
'''String ID section'''<br />
<br />
Tightly packed<br />
<br />
*4 bytes <br />
**unsigned 32 bit integer - TALK_STRING_ID<br />
*4 bytes<br />
**unsigned 32 bit integer - offset to string (appears to be an offset from 0x60)<br />
<br />
'''String Data'''<br />
<br />
*4 bytes<br />
**unsigned 32 bit integer - number of characters in string<br />
*String in 16bit wide characters (unicode?)</div>Dutch Master