TLK - Revision history

Sunjammer: Adding "See also" section

2015-03-31T21:14:08Z

Adding "See also" section

2015-03-30T17:29:54Z

added link to TLK_DA2 page

2015-03-29T20:17:31Z

2015-03-29T19:42:40Z

Split new DA2 information to its own TLK (DA2) page, minor reformating

2015-03-24T17:40:09Z

adding info about TLK format used in Dragon Age 2

2010-04-08T17:54:18Z

clarify the string termination

2010-01-12T15:17:14Z

2010-01-07T00:46:55Z

Information about the representation of String data.

2010-01-06T22:09:08Z

Make sure the string is 20 characters long, with 2 spaces.

2009-12-08T17:53:15Z

They're GFFs, so you can open them in the GFF editor.

@@ Line 1: / Line 1: @@
 The [[TLK]] file is a [[GFF]] formatted file used to contain strings. They can be opened in the Toolset or the GFF Editor.
@@ Line 42: / Line 38: @@
 *String in UTF-16, little endian.
 ** Terminated by a NUL character (0x00) (twice, since it is UTF-16LE) and filled up (with 0xff) to be a multiple of 4 bytes.
 [[Category:File types]]

← Older revision		Revision as of 17:29, 30 March 2015
Line 1:		Line 1:
		+	''This page is about the TLK file format used in Dragon Age Origins.''
		+	''For information about TLK file format used in Dragon Age 2, please go here [[TLK_%28DA2%29]]''
		+
		+
	The [[TLK]] file is a [[GFF]] formatted file used to contain strings. They can be opened in the Toolset or the GFF Editor.		The [[TLK]] file is a [[GFF]] formatted file used to contain strings. They can be opened in the Toolset or the GFF Editor.

@@ Line 11: / Line 11: @@
 <pre>
 Header
-String ID section
+String ID Section
-String data section
+String Data Section
 </pre>
@@ Line 31: / Line 31: @@
 **unsigned 32 bit integer - offset to string (appears to be an offset from 0x60)
-=== String Data ===
+=== String Data Section ===
 *4 bytes

@@ Line 37: / Line 37: @@
 ** 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.
+** Terminated by a NUL character (0x00) (twice, since it is UTF-16LE) and filled up (with 0xff) to be a multiple of 4 bytes.
 [[Category:File types]]

← Older revision		Revision as of 15:17, 12 January 2010
Line 38:		Line 38:
	*String in UTF-16, little endian.		*String in UTF-16, little endian.
	** Terminated by a NUL character (0x00) and filled up to be a multiple of 4 bytes.		** Terminated by a NUL character (0x00) and filled up to be a multiple of 4 bytes.
		+
		+
		+	[[Category:File types]]

@@ Line 34: / Line 34: @@
 *4 bytes
-**unsigned 32 bit integer - number of characters in string
+** Unsigned 32 bit integer, little endian - number of characters in string.
-*String in 16bit wide characters (unicode?)
+** The toolset seems to ignore this.

@@ Line 18: / Line 18: @@
 *104 bytes
-**20 byte string describing the file (GFF V4.0PC  TLK V0.2)
+**20 byte string describing the file, watch the 2 spaces between PC and TLK <pre>GFF V4.0PC  TLK V0.2</pre>
 **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

← Older revision		Revision as of 17:53, 8 December 2009
Line 1:		Line 1:
−	~~This contains~~ strings.	+	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.		Keep in mind that all numbers are in little-endian format if you are looking at the raw file.