Talk:JPEG XT

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
Low	This article has been rated as Low-importance on the project's importance scale.
	This article is supported by WikiProject Software (assessed as Low-importance).

Photography Low‑importance

	This article is within the scope of WikiProject Photography, a collaborative effort to improve the coverage of photography on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.PhotographyWikipedia:WikiProject PhotographyTemplate:WikiProject PhotographyPhotography articles
Low	This article has been rated as Low-importance on the project's importance scale.

Computer graphics Mid‑importance

	This article is within the scope of WikiProject Computer graphics, a collaborative effort to improve the coverage of computer graphics on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.Computer graphicsWikipedia:WikiProject Computer graphicsTemplate:WikiProject Computer graphicscomputer graphics articles
Mid	This article has been rated as Mid-importance on the project's importance scale.

"Binary" metadata[edit]

@DmitryKo: I've removed the word binary again. The phrase "binary metadata" is a misnomer, and it is not supported by the reference (pdf). Please do not re-add it without further discussion. nagualdesign 07:27, 6 March 2018 (UTC)[reply]

See binary file vs text file. Dmitry _{(talk•contibs)} 10:45, 6 March 2018 (UTC)[reply]

Which part of a JPEG XT file isn't binary? nagualdesign 20:47, 6 March 2018 (UTC)[reply]

To encode image dimensions as binary data, you define file offset, data type, and data size in bytes. You can then load the data from that file offset directly to registers/memory for processing. Example: 4 bytes 1780 0FB0 would encode "6016x4016 pixels" as two 16 bit integer numbers.

OTOH, to encode image dimensions as text metadata, you'd need to come with something like "dimensions: v=4016 h=6016; units=px". That's 36 ASCII-encoded bytes to parse and convert into two 16-bit integers. An order of magnitude bigger storage requirements, probably two orders of magnitute higher CPU processing power requirements. That's before you involve structured text data like XML or JSON.

So absolutely no similarities here. --Dmitry _{(talk•contibs)} 22:08, 28 April 2018 (UTC)[reply]