Talk:Xtf - Revision history

CobaltHex at 18:34, 12 September 2017

2017-09-12T18:34:37Z

JayFoxRox: /* Add file format info */

2017-08-23T19:57:46Z

‎Add file format info

JayFoxRox: /* Add file format info */

2017-08-22T18:49:35Z

‎Add file format info

JayFoxRox: /* Add file format info */ new section

2017-08-22T18:49:11Z

‎Add file format info: new section

JayFoxRox: /* Merge with dashboard article */ new section

2017-08-22T18:45:23Z

‎Merge with dashboard article: new section

New page

== Merge with dashboard article ==

I think it makes sense to merge this with the dashboard article or even move such file format stuff to other wikis.
However, I'm not sure how to integrate it best with the dashboard article, and I'm not aware of any wikis where this would fit.
--[[User:JayFoxRox|JayFoxRox]] ([[User talk:JayFoxRox|talk]]) 11:45, 22 August 2017 (PDT)

← Older revision		Revision as of 18:34, 12 September 2017
Line 1:		Line 1:
		+	== Change to article about promo fonts ==
		+	Both of these fonts were used as part of the Xbox's marketing materials. More info there than the XTF format. Perhaps move the XTF to a generic file format article (below)
		+
	== Merge with dashboard article ==		== Merge with dashboard article ==

@@ Line 17: / Line 17: @@
 * JayFoxRox: apparently the last structure [with mesh data] keeps repeating towards the end, so it's probably each glyph seperately
 * JayFoxRox: I don't have more time for doing this now - I already did more than I wanted by sourcing the Xbox.xtf and Xbox Book.xtf and looking at it with hexedit and googling for MS structures :P
-* JayFoxRox: I think there are degenerates, so looks like tri-strip
+* JayFoxRox: I think there are degenerates, so looks like tri-strip << edit: actually those are just tris!
 --[[User:JayFoxRox|JayFoxRox]] ([[User talk:JayFoxRox|talk]]) 11:49, 22 August 2017 (PDT)

@@ Line 9: / Line 9: @@
 from #xqemu irc channel
-JayFoxRox: I looked at the file, it seems to be a 2D mesh format, indices, followed by vertices
+* JayFoxRox: I looked at the file, it seems to be a 2D mesh format, indices, followed by vertices
-JayFoxRox: header is XTF0, then, then 4 bytes length for the following name of font [should be 32 bytes]
+* JayFoxRox: header is XTF0, then, then 4 bytes length for the following name of font [should be 32 bytes]
-JayFoxRox: seemingly this is used too: https://msdn.microsoft.com/en-us/library/dd144956(v=vs.85).aspx
+* JayFoxRox: seemingly this is used too: https://msdn.microsoft.com/en-us/library/dd144956(v=vs.85).aspx
-JayFoxRox: or at least there is a 4 byte length prefix again
+* JayFoxRox: or at least there is a 4 byte length prefix again
-JayFoxRox: near end of file it's very surely <code>u16 icount, u16 vcount, u16 indices[icount] { float x,y; }[vcount]</code>
+* JayFoxRox: near end of file it's very surely <code>u16 icount, u16 vcount, u16 indices[icount] { float x,y; }[vcount]</code>
-JayFoxRox: if there are any structures between those 2? no idea.
+* JayFoxRox: if there are any structures between those 2? no idea.
-JayFoxRox: apparently the last structure [with mesh data] keeps repeating towards the end, so it's probably each glyph seperately
+* JayFoxRox: apparently the last structure [with mesh data] keeps repeating towards the end, so it's probably each glyph seperately
-JayFoxRox: I don't have more time for doing this now - I already did more than I wanted by sourcing the Xbox.xtf and Xbox Book.xtf and looking at it with hexedit and googling for MS structures :P
+* JayFoxRox: I don't have more time for doing this now - I already did more than I wanted by sourcing the Xbox.xtf and Xbox Book.xtf and looking at it with hexedit and googling for MS structures :P
-JayFoxRox: I think there are degenerates, so looks like tri-strip
+* JayFoxRox: I think there are degenerates, so looks like tri-strip
 --[[User:JayFoxRox|JayFoxRox]] ([[User talk:JayFoxRox|talk]]) 11:49, 22 August 2017 (PDT)

← Older revision		Revision as of 18:49, 22 August 2017
Line 4:		Line 4:
	However, I'm not sure how to integrate it best with the dashboard article, and I'm not aware of any wikis where this would fit.		However, I'm not sure how to integrate it best with the dashboard article, and I'm not aware of any wikis where this would fit.
	--[[User:JayFoxRox\|JayFoxRox]] ([[User talk:JayFoxRox\|talk]]) 11:45, 22 August 2017 (PDT)		--[[User:JayFoxRox\|JayFoxRox]] ([[User talk:JayFoxRox\|talk]]) 11:45, 22 August 2017 (PDT)
		+
		+	== Add file format info ==
		+
		+	from #xqemu irc channel
		+
		+	JayFoxRox: I looked at the file, it seems to be a 2D mesh format, indices, followed by vertices
		+	JayFoxRox: header is XTF0, then, then 4 bytes length for the following name of font [should be 32 bytes]
		+	JayFoxRox: seemingly this is used too: https://msdn.microsoft.com/en-us/library/dd144956(v=vs.85).aspx
		+	JayFoxRox: or at least there is a 4 byte length prefix again
		+	JayFoxRox: near end of file it's very surely <code>u16 icount, u16 vcount, u16 indices[icount] { float x,y; }[vcount]</code>
		+	JayFoxRox: if there are any structures between those 2? no idea.
		+	JayFoxRox: apparently the last structure [with mesh data] keeps repeating towards the end, so it's probably each glyph seperately
		+	JayFoxRox: I don't have more time for doing this now - I already did more than I wanted by sourcing the Xbox.xtf and Xbox Book.xtf and looking at it with hexedit and googling for MS structures :P
		+	JayFoxRox: I think there are degenerates, so looks like tri-strip
		+
		+	--[[User:JayFoxRox\|JayFoxRox]] ([[User talk:JayFoxRox\|talk]]) 11:49, 22 August 2017 (PDT)