Compound File Binary Format - Revision history

Frap at 10:29, 11 May 2025

2025-05-11T10:29:30Z

IceKarma: ce

2025-05-10T20:34:04Z

← Previous revision		Revision as of 20:34, 10 May 2025
Line 21:		Line 21:

	==Structure==		==Structure==
	The CFBF file consists of a 512-~~Byte~~ header record followed by a number of ~~sectors~~ whose size is defined in the header. The literature defines Sectors to be either 512 or 4096 bytes in length, although the format is potentially capable of supporting sectors ranging in size from 128~~-Bytes~~ upwards in powers of 2 (128, 256, 512, 1024, etc.). The lower limit of 128 is the minimum required to fit a single directory entry in		The CFBF file consists of a 512-byte header record followed by a number of Sectors whose size is defined in the header. The literature defines Sectors to be either 512 or 4096 bytes in length, although the format is potentially capable of supporting sectors ranging in size from 128 bytes upwards, in powers of two (128, 256, 512, 1024, etc.). The lower limit of 128 is the minimum required to fit a single directory entry in
	a Directory Sector.{{Relevance inline\|paragraph\|reason=MS-CFB standard clearly says that a sector MUST be 512 or 4096, this sentence is encouraging to break the standard\|date=November 2016}}		a Directory Sector.{{Relevance inline\|paragraph\|reason=MS-CFB standard clearly says that a sector MUST be 512 or 4096, this sentence is encouraging to break the standard\|date=November 2016}}

	There are several types of sector that may be present in a CFBF:		There are several types of sector that may be present in a CFBF file:

	* File Allocation Table (FAT) Sector – contains chains of sector indices much as a FAT does in the FAT/FAT32 filesystems		* File Allocation Table (FAT) Sector – contains chains of sector indices much as a FAT does in the FAT/FAT32 filesystems
Line 100:		Line 100:

	===Glossary===		===Glossary===
	* ''FAT'' – File Allocation Table, also known as: ''SAT'' – Sector Allocation Table		* ''FAT'' – File Allocation Table; also known as ''SAT'' – Sector Allocation Table
	* ''DIFAT'' – Double-Indirect File Allocation Table		* ''DIFAT'' – Double-Indirect File Allocation Table
	* ''FAT Chain'' – a group of FAT entries which indicate the ~~sectors~~ allocated to a Stream in the file		* ''FAT Chain'' – a group of FAT entries which indicate the Sectors allocated to a Stream in the file
	* ''Stream'' – a virtual file which occupies a number of ~~sectors~~ within the CFBF		* ''Stream'' – a virtual file which occupies a number of Sectors within the CFBF
	* ''Sector'' – the unit of allocation within the CFBF, usually 512 or 4096 Bytes in length		* ''Sector'' – the unit of allocation within the CFBF, usually 512 or 4096 Bytes in length

Fredklaus2278: Clarified overview of the Compound File Binary Format

2024-06-13T02:21:57Z

Clarified overview of the Compound File Binary Format

← Previous revision		Revision as of 02:21, 13 June 2024
Line 11:		Line 11:
	\|url=http://msdn.microsoft.com/en-us/library/aa378938%28VS.85%29.aspx		\|url=http://msdn.microsoft.com/en-us/library/aa378938%28VS.85%29.aspx
	\|title=Compound Files (Windows)		\|title=Compound Files (Windows)
	\|work=Microsoft Developers Network (MSDN) library – COM SDK\|publisher=Microsoft Corporation\|accessdate=23 September 2009\|date=20 November 2008}}</ref><ref>{{cite web\|url=http://msdn.microsoft.com/en-us/library/ydd3k45e.aspx\|title=Containers: Compound Files\|work=Microsoft Developers Network (MSDN) library – Visual Studio 2008 documentation\|publisher=Microsoft Corporation\|accessdate=23 September 2009}}</ref><ref>{{cite web\|url=http://msdn.microsoft.com/en-us/library/cc542545%28VS.85%29.aspx\|title=Understand Compound Files\|work=Microsoft Developers Network (MSDN) library – ActiveDirectory Rights Management\|accessdate=23 September 2009\|date=25 June 2009}}</ref>		\|work=Microsoft Developers Network (MSDN) library – COM SDK\|publisher=Microsoft Corporation\|accessdate=23 September 2009\|date=20 November 2008}}</ref><ref>{{cite web\|url=http://msdn.microsoft.com/en-us/library/ydd3k45e.aspx\|title=Containers: Compound Files\|work=Microsoft Developers Network (MSDN) library – Visual Studio 2008 documentation\|publisher=Microsoft Corporation\|accessdate=23 September 2009}}</ref><ref>{{cite web\|url=http://msdn.microsoft.com/en-us/library/cc542545%28VS.85%29.aspx\|title=Understand Compound Files\|work=Microsoft Developers Network (MSDN) library – ActiveDirectory Rights Management\|accessdate=23 September 2009\|date=25 June 2009}}</ref> The file format is used for storing storage objects and stream objects in a hierarchical structure within a single file.<ref>{{Cite web \|date=2020-01-28 \|title=Microsoft Compound File Binary File Format, Version 4 \|url=https://www.loc.gov/preservation/digital/formats/fdd/fdd000392.shtml \|access-date=2024-06-13 \|website=www.loc.gov}}</ref>

	Microsoft has opened the format for use by others and it is now used in a variety of programs from [[Microsoft Word]] and [[Microsoft Access]] to Business Objects.{{Citation needed\|date=November 2009}} It also forms the basis of the [[Advanced Authoring Format]].<ref>[http://www.aafassociation.org AMW Association (formerly AAF Association)] {{webarchive\|url=https://web.archive.org/web/20000815063147/http://www.aafassociation.org/ \|date=15 August 2000 }}</ref>		Microsoft has opened the format for use by others and it is now used in a variety of programs from [[Microsoft Word]] and [[Microsoft Access]] to Business Objects.{{Citation needed\|date=November 2009}} It also forms the basis of the [[Advanced Authoring Format]].<ref>[http://www.aafassociation.org AMW Association (formerly AAF Association)] {{webarchive\|url=https://web.archive.org/web/20000815063147/http://www.aafassociation.org/ \|date=15 August 2000 }}</ref>

SimLibrarian at 17:46, 5 January 2024

2024-01-05T17:46:29Z

← Previous revision		Revision as of 17:46, 5 January 2024
Line 1:		Line 1:
			{{Short description\|Compound document file format}}
	{{Use dmy dates\|date=December 2019}}		{{Use dmy dates\|date=December 2019}}
	'''Compound File Binary Format''' (CFBF), also called '''Compound File''', '''Compound Document format''',<ref>{{cite web\|url=http://poi.apache.org/poifs/index.html\|title=Apache POI – POIFS\|publisher=POI Project\|accessdate=10 May 2011\|archive-url=https://web.archive.org/web/20110426150340/http://poi.apache.org/poifs/index.html\|archive-date=26 April 2011\|url-status=dead}}</ref> or '''Composite Document File V2'''<ref>{{cite web		'''Compound File Binary Format''' (CFBF), also called '''Compound File''', '''Compound Document format''',<ref>{{cite web\|url=http://poi.apache.org/poifs/index.html\|title=Apache POI – POIFS\|publisher=POI Project\|accessdate=10 May 2011\|archive-url=https://web.archive.org/web/20110426150340/http://poi.apache.org/poifs/index.html\|archive-date=26 April 2011\|url-status=dead}}</ref> or '''Composite Document File V2'''<ref>{{cite web

InternetArchiveBot: Rescuing 1 sources and tagging 0 as dead.) #IABot (v2.0.1

2020-07-27T02:28:32Z

Rescuing 1 sources and tagging 0 as dead.) #IABot (v2.0.1

← Previous revision		Revision as of 02:28, 27 July 2020
Line 2:		Line 2:
	'''Compound File Binary Format''' (CFBF), also called '''Compound File''', '''Compound Document format''',<ref>{{cite web\|url=http://poi.apache.org/poifs/index.html\|title=Apache POI – POIFS\|publisher=POI Project\|accessdate=10 May 2011\|archive-url=https://web.archive.org/web/20110426150340/http://poi.apache.org/poifs/index.html\|archive-date=26 April 2011\|url-status=dead}}</ref> or '''Composite Document File V2'''<ref>{{cite web		'''Compound File Binary Format''' (CFBF), also called '''Compound File''', '''Compound Document format''',<ref>{{cite web\|url=http://poi.apache.org/poifs/index.html\|title=Apache POI – POIFS\|publisher=POI Project\|accessdate=10 May 2011\|archive-url=https://web.archive.org/web/20110426150340/http://poi.apache.org/poifs/index.html\|archive-date=26 April 2011\|url-status=dead}}</ref> or '''Composite Document File V2'''<ref>{{cite web
	\|url=https://linuxconfig.org/how-to-convert-documents-between-libreoffice-and-microsoft-office-file-formats-on-linux		\|url=https://linuxconfig.org/how-to-convert-documents-between-libreoffice-and-microsoft-office-file-formats-on-linux
	\|title= How to convert documents between LibreOffice and Microsoft Office file formats on Linux		\|title=How to convert documents between LibreOffice and Microsoft Office file formats on Linux
			\|accessdate=25 November 2016
⚫	~~\|accessdate=25 November 2016~~}}</ref> (CDF), is a [[compound document\|compound]] [[document file format]] for storing numerous files and streams within a single file on a disk. CFBF is developed by [[Microsoft]] and is an implementation of Microsoft [[COM Structured Storage]].<ref>{{cite web
			\|archive-url=https://web.archive.org/web/20190921163547/https://linuxconfig.org/how-to-convert-documents-between-libreoffice-and-microsoft-office-file-formats-on-linux
			\|archive-date=21 September 2019
			\|url-status=dead
		⚫	}}</ref> (CDF), is a [[compound document\|compound]] [[document file format]] for storing numerous files and streams within a single file on a disk. CFBF is developed by [[Microsoft]] and is an implementation of Microsoft [[COM Structured Storage]].<ref>{{cite web
	\|url=http://msdn.microsoft.com/en-us/library/aa378938%28VS.85%29.aspx		\|url=http://msdn.microsoft.com/en-us/library/aa378938%28VS.85%29.aspx
	\|title=Compound Files (Windows)		\|title=Compound Files (Windows)

DannyS712 bot: Task 70: Update syntaxhighlight tags - remove use of deprecated tags

2020-05-11T17:35:25Z

Task 70: Update syntaxhighlight tags - remove use of deprecated <source> tags

← Previous revision		Revision as of 17:35, 11 May 2020
Line 32:		Line 32:
	===CFBF Header format===		===CFBF Header format===
	The CFBF Header occupies the first 512 bytes of the file and information required to interpret the rest of the file. The C-Style structure declaration below (extracted from the AAFA's Low-Level Container Specification) shows the members of the CFBF header and their purpose:		The CFBF Header occupies the first 512 bytes of the file and information required to interpret the rest of the file. The C-Style structure declaration below (extracted from the AAFA's Low-Level Container Specification) shows the members of the CFBF header and their purpose:
	<~~source~~ lang="c">		<syntaxhighlight lang="c">
	typedef unsigned long ULONG; // 4 Bytes		typedef unsigned long ULONG; // 4 Bytes
	typedef unsigned short USHORT; // 2 Bytes		typedef unsigned short USHORT; // 2 Bytes
Line 79:		Line 79:
	SECT _sectFat[109]; // [4CH,436] the SECTs of first 109 FAT sectors		SECT _sectFat[109]; // [4CH,436] the SECTs of first 109 FAT sectors
	};		};
			</syntaxhighlight>
	</source>

	===File Allocation Table (FAT) Sectors===		===File Allocation Table (FAT) Sectors===

217.32.203.178: The correct name of the file format is "Composite Document File V2". File/exiftool adds the extra "Document" in its output.

2020-02-12T15:43:15Z

The correct name of the file format is "Composite Document File V2". File/exiftool adds the extra "Document" in its output.

← Previous revision		Revision as of 15:43, 12 February 2020
Line 1:		Line 1:
	{{Use dmy dates\|date=December 2019}}		{{Use dmy dates\|date=December 2019}}
	'''Compound File Binary Format''' (CFBF), also called '''Compound File''', '''Compound Document format''',<ref>{{cite web\|url=http://poi.apache.org/poifs/index.html\|title=Apache POI – POIFS\|publisher=POI Project\|accessdate=10 May 2011\|archive-url=https://web.archive.org/web/20110426150340/http://poi.apache.org/poifs/index.html\|archive-date=26 April 2011\|url-status=dead}}</ref> or '''Composite Document File V2 ~~Document~~'''<ref>{{cite web		'''Compound File Binary Format''' (CFBF), also called '''Compound File''', '''Compound Document format''',<ref>{{cite web\|url=http://poi.apache.org/poifs/index.html\|title=Apache POI – POIFS\|publisher=POI Project\|accessdate=10 May 2011\|archive-url=https://web.archive.org/web/20110426150340/http://poi.apache.org/poifs/index.html\|archive-date=26 April 2011\|url-status=dead}}</ref> or '''Composite Document File V2'''<ref>{{cite web
	\|url=https://linuxconfig.org/how-to-convert-documents-between-libreoffice-and-microsoft-office-file-formats-on-linux		\|url=https://linuxconfig.org/how-to-convert-documents-between-libreoffice-and-microsoft-office-file-formats-on-linux
	\|title= How to convert documents between LibreOffice and Microsoft Office file formats on Linux		\|title= How to convert documents between LibreOffice and Microsoft Office file formats on Linux

Dawnseeker2000: fixed dashes using a script, date formats per MOS:DATEFORMAT by script

2019-12-28T07:36:30Z

fixed dashes using a script, date formats per MOS:DATEFORMAT by script

← Previous revision		Revision as of 07:36, 28 December 2019
Line 1:		Line 1:
		⚫	{{Use dmy dates\|date=December 2019}}
	'''Compound File Binary Format''' (CFBF), also called '''Compound File''', '''Compound Document format''',<ref>{{cite web\|url=http://poi.apache.org/poifs/index.html\|title=Apache POI - POIFS\|publisher=POI Project\|accessdate=10 May 2011\|archive-url=https://web.archive.org/web/20110426150340/http://poi.apache.org/poifs/index.html\|archive-date=26 April 2011\|url-status=dead}}</ref> or '''Composite Document File V2 Document'''<ref>{{cite web		'''Compound File Binary Format''' (CFBF), also called '''Compound File''', '''Compound Document format''',<ref>{{cite web\|url=http://poi.apache.org/poifs/index.html\|title=Apache POI – POIFS\|publisher=POI Project\|accessdate=10 May 2011\|archive-url=https://web.archive.org/web/20110426150340/http://poi.apache.org/poifs/index.html\|archive-date=26 April 2011\|url-status=dead}}</ref> or '''Composite Document File V2 Document'''<ref>{{cite web
	\|url=https://linuxconfig.org/how-to-convert-documents-between-libreoffice-and-microsoft-office-file-formats-on-linux		\|url=https://linuxconfig.org/how-to-convert-documents-between-libreoffice-and-microsoft-office-file-formats-on-linux
	\|title= How to convert documents between LibreOffice and Microsoft Office file formats on Linux		\|title= How to convert documents between LibreOffice and Microsoft Office file formats on Linux
	\|accessdate=25 ~~Nov~~ 2016~~\|date=~~}}</ref> (CDF), is a [[compound document\|compound]] [[document file format]] for storing numerous files and streams within a single file on a disk. CFBF is developed by [[Microsoft]] and is an implementation of Microsoft [[COM Structured Storage]].<ref>{{cite web		\|accessdate=25 November 2016}}</ref> (CDF), is a [[compound document\|compound]] [[document file format]] for storing numerous files and streams within a single file on a disk. CFBF is developed by [[Microsoft]] and is an implementation of Microsoft [[COM Structured Storage]].<ref>{{cite web
	\|url=http://msdn.microsoft.com/en-us/library/aa378938%28VS.85%29.aspx		\|url=http://msdn.microsoft.com/en-us/library/aa378938%28VS.85%29.aspx
	\|title=Compound Files (Windows)		\|title=Compound Files (Windows)
Line 20:		Line 21:
	There are several types of sector that may be present in a CFBF:		There are several types of sector that may be present in a CFBF:

	* File Allocation Table (FAT) Sector - contains chains of sector indices much as a FAT does in the FAT/FAT32 filesystems		* File Allocation Table (FAT) Sector – contains chains of sector indices much as a FAT does in the FAT/FAT32 filesystems
	* MiniFAT Sectors - similar to the FAT but storing chains of mini-sectors within the Mini-Stream		* MiniFAT Sectors – similar to the FAT but storing chains of mini-sectors within the Mini-Stream
	* Double-Indirect FAT (DIFAT) Sector - contains chains of FAT sector indices		* Double-Indirect FAT (DIFAT) Sector – contains chains of FAT sector indices
	* Directory Sector - contains directory entries		* Directory Sector – contains directory entries
	* Stream Sector - contains arbitrary file data		* Stream Sector – contains arbitrary file data
	* Range Lock Sector - contains the byte-range locking area of a large file		* Range Lock Sector – contains the byte-range locking area of a large file

	More detail is given below for the header and each sector type.		More detail is given below for the header and each sector type.
Line 83:		Line 84:
	When taken together as a single stream the collection of FAT sectors define the status and linkage of every sector in the file. Each entry in the FAT is 4 bytes in length and contains the sector number of the next sector in a FAT chain or one of the following special values:		When taken together as a single stream the collection of FAT sectors define the status and linkage of every sector in the file. Each entry in the FAT is 4 bytes in length and contains the sector number of the next sector in a FAT chain or one of the following special values:

	* FREESECT (0xFFFFFFFF) - denotes an unused sector		* FREESECT (0xFFFFFFFF) – denotes an unused sector
	* ENDOFCHAIN (0xFFFFFFFE) - marks the last sector in a FAT chain		* ENDOFCHAIN (0xFFFFFFFE) – marks the last sector in a FAT chain
	* FATSECT (0xFFFFFFFD) - marks a sector used to store part of the FAT		* FATSECT (0xFFFFFFFD) – marks a sector used to store part of the FAT
	* DIFSECT (0xFFFFFFFC) - marks a sector used to store part of the DIFAT		* DIFSECT (0xFFFFFFFC) – marks a sector used to store part of the DIFAT

	===Range Lock Sector===		===Range Lock Sector===
Line 94:		Line 95:

	===Glossary===		===Glossary===
	* ''FAT'' - File Allocation Table, also known as: ''SAT'' - Sector Allocation Table		* ''FAT'' – File Allocation Table, also known as: ''SAT'' – Sector Allocation Table
	* ''DIFAT'' - Double-Indirect File Allocation Table		* ''DIFAT'' – Double-Indirect File Allocation Table
	* ''FAT Chain'' - a group of FAT entries which indicate the sectors allocated to a Stream in the file		* ''FAT Chain'' – a group of FAT entries which indicate the sectors allocated to a Stream in the file
	* ''Stream'' - a virtual file which occupies a number of sectors within the CFBF		* ''Stream'' – a virtual file which occupies a number of sectors within the CFBF
	* ''Sector'' - the unit of allocation within the CFBF, usually 512 or 4096 Bytes in length		* ''Sector'' – the unit of allocation within the CFBF, usually 512 or 4096 Bytes in length

	==See also==		==See also==
Line 106:		Line 107:

	==References==		==References==
	{{Reflist\|2}}		{{Reflist}}

	==External links==		==External links==
	* {{cite web		* {{cite web
	\| accessdate = 2019~~-07-06~~		\| accessdate = 6 July 2019
	\| url = https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-cfb/53989ce4-7b05-4f8d-829b-d08d6148375b		\| url = https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-cfb/53989ce4-7b05-4f8d-829b-d08d6148375b
	\| title = [MS-CFB]: Compound File Binary File Format		\| title = [MS-CFB]: Compound File Binary File Format
Line 116:		Line 117:
	}}		}}
	* {{cite web		* {{cite web
	\| accessdate = ~~2006-05-~~22		\| accessdate = 22 May 2006

	\| format = PDF
	\| url = http://sc.openoffice.org/compdocfileformat.pdf		\| url = http://sc.openoffice.org/compdocfileformat.pdf
	\| title = Microsoft Compound Document File Format		\| title = Microsoft Compound Document File Format
Line 123:		Line 124:
	}}		}}
	* {{cite web		* {{cite web
	\| accessdate = ~~2006-05-~~22		\| accessdate = 22 May 2006
	\| format = PDF
	\| url = http://www.amwa.tv/downloads/specifications/aafcontainerspec-v1.0.1.pdf		\| url = http://www.amwa.tv/downloads/specifications/aafcontainerspec-v1.0.1.pdf
	\| title = Advanced Authoring Format Low-Level Container Specification		\| title = Advanced Authoring Format Low-Level Container Specification
Line 133:		Line 133:
	}}		}}
	* {{cite web		* {{cite web
	\| accessdate = 2019~~-07-06~~		\| accessdate = 6 July 2019
	\| format = HTML
	\| url = https://www.loc.gov/preservation/digital/formats/fdd/fdd000380.shtml		\| url = https://www.loc.gov/preservation/digital/formats/fdd/fdd000380.shtml
	\| title = Microsoft Compound File Binary File Format, Version 3		\| title = Microsoft Compound File Binary File Format, Version 3
	\| publisher = Library of Congress, Digital Formats web site		\| publisher = Library of Congress, Digital Formats web site
	}}		}}
⚫	{{Use dmy dates\|date=~~November~~ ~~2011~~}}

	[[Category:Computer file formats]]		[[Category:Computer file formats]]

Monkbot: Task 16: replaced (2×) / removed (0×) deprecated |dead-url= and |deadurl= with |url-status=;

2019-10-02T10:18:01Z

Task 16: replaced (2×) / removed (0×) deprecated |dead-url= and |deadurl= with |url-status=;

← Previous revision		Revision as of 10:18, 2 October 2019
Line 1:		Line 1:
	'''Compound File Binary Format''' (CFBF), also called '''Compound File''', '''Compound Document format''',<ref>{{cite web\|url=http://poi.apache.org/poifs/index.html\|title=Apache POI - POIFS~~\|work=~~\|publisher=POI Project\|accessdate=10 May 2011~~\|date=~~\|archive-url=https://web.archive.org/web/20110426150340/http://poi.apache.org/poifs/index.html\|archive-date=26 April 2011\|~~dead-~~url=~~yes~~}}</ref> or '''Composite Document File V2 Document'''<ref>{{cite web		'''Compound File Binary Format''' (CFBF), also called '''Compound File''', '''Compound Document format''',<ref>{{cite web\|url=http://poi.apache.org/poifs/index.html\|title=Apache POI - POIFS\|publisher=POI Project\|accessdate=10 May 2011\|archive-url=https://web.archive.org/web/20110426150340/http://poi.apache.org/poifs/index.html\|archive-date=26 April 2011\|url-status=dead}}</ref> or '''Composite Document File V2 Document'''<ref>{{cite web
	\|url=https://linuxconfig.org/how-to-convert-documents-between-libreoffice-and-microsoft-office-file-formats-on-linux		\|url=https://linuxconfig.org/how-to-convert-documents-between-libreoffice-and-microsoft-office-file-formats-on-linux
	\|title= How to convert documents between LibreOffice and Microsoft Office file formats on Linux		\|title= How to convert documents between LibreOffice and Microsoft Office file formats on Linux
Line 130:		Line 130:
	\| archive-url = https://web.archive.org/web/20110809045600/http://www.amwa.tv/downloads/specifications/aafcontainerspec-v1.0.1.pdf		\| archive-url = https://web.archive.org/web/20110809045600/http://www.amwa.tv/downloads/specifications/aafcontainerspec-v1.0.1.pdf
	\| archive-date = 9 August 2011		\| archive-date = 9 August 2011
	\| ~~dead-~~url = ~~yes~~		\| url-status = dead
	}}		}}
	* {{cite web		* {{cite web

InternetArchiveBot: Rescuing 2 sources and tagging 0 as dead. #IABot (v2.0beta15)

2019-07-08T04:34:52Z

Rescuing 2 sources and tagging 0 as dead. #IABot (v2.0beta15)

← Previous revision		Revision as of 04:34, 8 July 2019
Line 1:		Line 1:
	'''Compound File Binary Format''' (CFBF), also called '''Compound File''', '''Compound Document format''',<ref>{{cite web		'''Compound File Binary Format''' (CFBF), also called '''Compound File''', '''Compound Document format''',<ref>{{cite web\|url=http://poi.apache.org/poifs/index.html\|title=Apache POI - POIFS\|work=\|publisher=POI Project\|accessdate=10 May 2011\|date=\|archive-url=https://web.archive.org/web/20110426150340/http://poi.apache.org/poifs/index.html\|archive-date=26 April 2011\|dead-url=yes}}</ref> or '''Composite Document File V2 Document'''<ref>{{cite web
	\|url=http://poi.apache.org/poifs/index.html
	\|title= Apache POI - POIFS
	\|work=\|publisher=POI Project\|accessdate=10 May 2011\|date=}}</ref> or '''Composite Document File V2 Document'''<ref>{{cite web
	\|url=https://linuxconfig.org/how-to-convert-documents-between-libreoffice-and-microsoft-office-file-formats-on-linux		\|url=https://linuxconfig.org/how-to-convert-documents-between-libreoffice-and-microsoft-office-file-formats-on-linux
	\|title= How to convert documents between LibreOffice and Microsoft Office file formats on Linux		\|title= How to convert documents between LibreOffice and Microsoft Office file formats on Linux
Line 131:		Line 128:
	\| title = Advanced Authoring Format Low-Level Container Specification		\| title = Advanced Authoring Format Low-Level Container Specification
	\| work = Microsoft Structured Storage version 3 specification (PDF)		\| work = Microsoft Structured Storage version 3 specification (PDF)
			\| archive-url = https://web.archive.org/web/20110809045600/http://www.amwa.tv/downloads/specifications/aafcontainerspec-v1.0.1.pdf
			\| archive-date = 9 August 2011
			\| dead-url = yes
	}}		}}
	* {{cite web		* {{cite web

← Previous revision		Revision as of 17:46, 5 January 2024
Line 1:		Line 1:
			{{Short description\|Compound document file format}}
	{{Use dmy dates\|date=December 2019}}		{{Use dmy dates\|date=December 2019}}
	'''Compound File Binary Format''' (CFBF), also called '''Compound File''', '''Compound Document format''',<ref>{{cite web\|url=http://poi.apache.org/poifs/index.html\|title=Apache POI – POIFS\|publisher=POI Project\|accessdate=10 May 2011\|archive-url=https://web.archive.org/web/20110426150340/http://poi.apache.org/poifs/index.html\|archive-date=26 April 2011\|url-status=dead}}</ref> or '''Composite Document File V2'''<ref>{{cite web		'''Compound File Binary Format''' (CFBF), also called '''Compound File''', '''Compound Document format''',<ref>{{cite web\|url=http://poi.apache.org/poifs/index.html\|title=Apache POI – POIFS\|publisher=POI Project\|accessdate=10 May 2011\|archive-url=https://web.archive.org/web/20110426150340/http://poi.apache.org/poifs/index.html\|archive-date=26 April 2011\|url-status=dead}}</ref> or '''Composite Document File V2'''<ref>{{cite web