CSV - Revision history

imported>Ikskoks at 14:57, 10 January 2021

2021-01-10T14:57:10Z

← Older revision	Revision as of 14:57, 10 January 2021
(No difference)

imported>Ikskoks at 14:57, 10 January 2021

2021-01-10T14:57:10Z

← Older revision		Revision as of 14:57, 10 January 2021
Line 40:		Line 40:

	Each field is NULL-terminated (either 0x00 or 0x00 0x00 depending on 8- or 16-bit data). Then, the remainder of the field is padded with either 0xCC (8-bit data) or 0xCD (16-bit data).		Each field is NULL-terminated (either 0x00 or 0x00 0x00 depending on 8- or 16-bit data). Then, the remainder of the field is padded with either 0xCC (8-bit data) or 0xCD (16-bit data).


			[[Category:File Format]]

imported>Multimedia Mike: omit the filenames

2016-12-18T00:40:03Z

omit the filenames

← Older revision	Revision as of 00:40, 18 December 2016
(No difference)

imported>Multimedia Mike: omit the filenames

2016-12-18T00:40:03Z

omit the filenames

← Older revision		Revision as of 00:40, 18 December 2016
Line 12:		Line 12:

	=== XPEC Textual CSV ===		=== XPEC Textual CSV ===
	The Windows version has ~~CSV files entitled, e.g., 'ACT1dialog_PC_ENGLISH.csv'. These are~~ textual CSV files. The specific type of text is little-endian UTF-16 as evidenced by the 0xFF 0xFE byte order mark (BOM) in the first 2 bytes of the file.		The Windows version has textual CSV files. The specific type of text is little-endian UTF-16 as evidenced by the 0xFF 0xFE byte order mark (BOM) in the first 2 bytes of the file.

	These are the column names indicated by the first line of the CSV:		These are the column names indicated by the first line of the CSV:
Line 37:		Line 37:

	=== XPEC Binary CSV ===		=== XPEC Binary CSV ===
	The Wii version has files ~~entitled, e~~.~~g., 'ACT1dialog_WII_SPANISH.csv'. It contains~~ the same data as the textual variant, ~~but~~ the fields are fixed width. Further, some of the fields are 8-bit/ASCII and some are big-endian UTF-16 (not little-endian as seen in the PC variant).		The Wii version also has CSV files. While these CSV files contain the same data as the textual variant, the fields are fixed width. Further, some of the fields are 8-bit/ASCII and some are big-endian UTF-16 (not little-endian as seen in the PC variant).

	Each field is NULL-terminated (either 0x00 or 0x00 0x00 depending on 8- or 16-bit data). Then, the remainder of the field is padded with either 0xCC (8-bit data) or 0xCD (16-bit data).		Each field is NULL-terminated (either 0x00 or 0x00 0x00 depending on 8- or 16-bit data). Then, the remainder of the field is padded with either 0xCC (8-bit data) or 0xCD (16-bit data).

imported>Multimedia Mike: wiki can't store the Chinese characters correctly; specify the Unicode code points instead

2016-12-17T22:14:41Z

wiki can't store the Chinese characters correctly; specify the Unicode code points instead

← Older revision	Revision as of 22:14, 17 December 2016
(No difference)

imported>Multimedia Mike: wiki can't store the Chinese characters correctly; specify the Unicode code points instead

2016-12-17T22:14:41Z

wiki can't store the Chinese characters correctly; specify the Unicode code points instead

← Older revision		Revision as of 22:14, 17 December 2016
Line 18:		Line 18:
	* name		* name
	* Speaker		* Speaker
	* ?? (Chinese for '~~text~~')		* ''(the Chinese characters for text: Code points U+6587 U+672C)''
	* jumpto		* jumpto
	* select_1		* select_1

imported>Multimedia Mike: trying to restore Chinese characters

2016-12-17T22:11:27Z

trying to restore Chinese characters

← Older revision	Revision as of 22:11, 17 December 2016
(No difference)

imported>Multimedia Mike: trying to restore Chinese characters

2016-12-17T22:11:27Z

trying to restore Chinese characters

← Older revision		Revision as of 22:11, 17 December 2016
Line 12:		Line 12:

	=== XPEC Textual CSV ===		=== XPEC Textual CSV ===
	The Windows version has CSV files entitled, e.g., 'ACT1dialog_PC_ENGLISH.csv'. These are textual CSV files. The specific type of text is little-endian UTF-16 as evidenced by the 0xFF 0xFE byte order mark (BOM) in the first 2 bytes in the file.		The Windows version has CSV files entitled, e.g., 'ACT1dialog_PC_ENGLISH.csv'. These are textual CSV files. The specific type of text is little-endian UTF-16 as evidenced by the 0xFF 0xFE byte order mark (BOM) in the first 2 bytes of the file.

	These are the column names indicated by the first line of the CSV:		These are the column names indicated by the first line of the CSV:

imported>Multimedia Mike: fill in XPEC CSV details

2016-12-17T22:09:35Z

fill in XPEC CSV details

← Older revision	Revision as of 22:09, 17 December 2016
(No difference)

imported>Multimedia Mike: fill in XPEC CSV details

2016-12-17T22:09:35Z

fill in XPEC CSV details

← Older revision		Revision as of 22:09, 17 December 2016
Line 5:		Line 5:

	There are invariably caveats to dealing with CSV data. For example, if a value is a text string that contains a comma, then the comma either needs to be escaped or the string needs to be enclosed in quotes (and then, if the string contains quotes, ''those'' need to be escaped as well).		There are invariably caveats to dealing with CSV data. For example, if a value is a text string that contains a comma, then the comma either needs to be escaped or the string needs to be enclosed in quotes (and then, if the string contains quotes, ''those'' need to be escaped as well).

			== The Hardy Boys: The Hidden Theft ==
			The game [http://www.mobygames.com/game/hardy-boys-the-hidden-theft The Hardy Boys: The Hidden Theft] stores conversation dialog in a CSV file. However, this game was released on 2 platforms -- Windows and Wii -- and the CSV is different on each platform. Windows uses a textual format while the Wii version encodes the same data fields into a fixed-width binary format while retaining the CSV extension.

			This game was developed by [http://www.xpec.com/ XPEC Entertainment], a Shanghai-based company (which helps explains why one of the CSV fields has a Chinese name). It's possible that this same format was used in other games developed by the same group.

			=== XPEC Textual CSV ===
			The Windows version has CSV files entitled, e.g., 'ACT1dialog_PC_ENGLISH.csv'. These are textual CSV files. The specific type of text is little-endian UTF-16 as evidenced by the 0xFF 0xFE byte order mark (BOM) in the first 2 bytes in the file.

			These are the column names indicated by the first line of the CSV:

			* name
			* Speaker
			* ?? (Chinese for 'text')
			* jumpto
			* select_1
			* select_2
			* select_3
			* itemevent
			* i_jumpto
			* clueevent
			* c_jumpto
			* no_jumpto
			* clue_1
			* item_1
			* item_2
			* item_3
			* expression
			* camera
			* eventname

			=== XPEC Binary CSV ===
			The Wii version has files entitled, e.g., 'ACT1dialog_WII_SPANISH.csv'. It contains the same data as the textual variant, but the fields are fixed width. Further, some of the fields are 8-bit/ASCII and some are big-endian UTF-16 (not little-endian as seen in the PC variant).

			Each field is NULL-terminated (either 0x00 or 0x00 0x00 depending on 8- or 16-bit data). Then, the remainder of the field is padded with either 0xCC (8-bit data) or 0xCD (16-bit data).