From e18843de6d53ec2aa327ec00077fb3f3c64b6615 Mon Sep 17 00:00:00 2001 From: Nicola Ken Barozzi Date: Sat, 23 Mar 2002 16:33:26 +0000 Subject: [PATCH] no message git-svn-id: https://svn.apache.org/repos/asf/jakarta/poi/trunk@352264 13f79535-47bb-0310-9956-ffa450edef68 --- src/java/org/apache/poi/hdf/hdf.xml | 295 ---------------------------- 1 file changed, 295 deletions(-) delete mode 100644 src/java/org/apache/poi/hdf/hdf.xml diff --git a/src/java/org/apache/poi/hdf/hdf.xml b/src/java/org/apache/poi/hdf/hdf.xml deleted file mode 100644 index 1ed43fa031..0000000000 --- a/src/java/org/apache/poi/hdf/hdf.xml +++ /dev/null @@ -1,295 +0,0 @@ - - - - HDF Horrible Document File Format - - - - - - - A word docfile consists of a main stream, a summary information stream, - a table stream, a data stream, and 0 or more object streams which contain - private data for POI-FS 2.0 objects embedded within the Word document. - The summary information stream is described in the section immediately - following this one. The object storages contain binary data for embedded - objects. Word has no knowledge of the contents of these storages; - this information is accessed and manipulated though the POI-FS 2.0 APIs. - - -
- - - Stored at beginning of page 0 of the file. fib.fComplex will be set to zero. - The FIB contains a "magic word" and pointers to the various other parts of - the file,as well as information about the length of the file. - The FIB starts at the beginning of the file. - - - - - text of body, footnotes, headers - Text begins at the position recorded in fib.fcMin. - The text of the file starts at fib.fcMin. fib.fcMin is usually set to the - next 128 byte boundary after the end of the FIB. The text in a Word document - is ASCII text with the following restrictions (ASCII codes given in decimal):\ - - Paragraph ends are stored as a single Carriage Return character (ASCII 13). - No other occurrences of this character sequence are allowed. - Hard line breaks which are not paragraph ends are stored as ASCII 11. Other - line break or word wrap information is not stored. - Breaking hyphens are stored as ASCII 45 (normal hyphen code); Non-required - hyphens are ASCII 31. Non-breaking hyphens are stored as ASCII 30. - Non-breaking spaces are stored as 160. Normal spaces are ASCII 32. - Page breaks and Section marks are ASCII 12 (normal form feed); if there's - an entry in the section table, it's a section mark, otherwise it's a page - break. - Column breaks are stored as ASCII 14. - Tab characters are ASCII 9 (normal). - The field begin mark which delimits the beginning of a field is ASCII 19. - The field end mark which delimits the end of a field is ASCII 21. The field - separator ,which marks the boundary between the preceding field code text - and following field expansion text within a field, is ASCII 20. The field - escape character is the '\' character which also serves as the formula mark. - The cell mark which delimits the end of a cell in a table row is stored as - ASCII 7 and has the fInTable paragraph property set to fTrue - (pap.fInTable == 1). - The row mark which delimits the end of a table row is stored as ASCII 7 - and has the fInTable paragraph property and fTtp paragraph property set - to fTrue (pap.fInTable == 1 && pap.fTtp == 1). - - - - - FKPs for CHPs, PAPs and LVCs - The first FKP begins at a 512-byte boundary after the last byte text written.. - The remaining FKPs are recorded in the 512-byte pages that immediately follow. - The FKPs for CHPs PAPs and LVCs are interleaved. Previous versions of Word - wrote them in contiguous chunks. The hplcfbte's of the three flavors - (CHP, PAP and LVC) are used to find the relevant FKP of the appropriate type. - group of SEPXs - - - - - SEPXs immediately follow the FKPs and are concatenated one after the other. - SEPXs are no longer guaranteed to start on a page boundary if it would span a - boundary if placed immediately after the preceding SEPX. - - -
- - - The summary information for a Word document is stored in two structured storage - streams, SummaryInformation and DocumentSummaryInformation. Information on the - layout of the SummaryInformation stream can be found in Appendix B of the POI-FS 2 - Programmers Reference. - - - - - Word stores various plcfs and tables with the stream named either "0Table" or - "1Table". Ordinarily a file will contain only one table stream. However, in - some unusual circumstances (e.g. crash during file save) a file might have two - table streams. In that case the bit field fWhichTblStm in the FIB should be used - to determine which table stream to read. If fWhichTblStm is 0, then the FIB refers - to the stream named "0Table", and if fWhichTblStm is 1, then the FIB refers to - the stream name "1Table". - - - - - Undocumented undo / versioning data - - - - - - Undocumented undo / versioning data - - - - - - Undocumented undo / versioning data - - - - - - Undocumented undo / versioning data - - - - - - (style sheet) Written immediately after the previous table. - This is recorded in all Word documents. - - - -
- - - - - - - - \ No newline at end of file