cleaned up typos mostly

git-svn-id: https://svn.apache.org/repos/asf/jakarta/poi/trunk@352098 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
mjohnson 2002-02-16 15:57:08 +00:00
parent fda6778596
commit 20edc3af50
1 changed files with 38 additions and 42 deletions

View File

@ -1,46 +1,42 @@
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.0//EN" "../dtd/document-v10.dtd"> <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.0//EN" "../dtd/document-v10.dtd">
<document> <document>
<header> <header>
<title>PoiFS</title> <title>PoiFS</title>
<subtitle>Overview</subtitle> <subtitle>Overview</subtitle>
<authors> <authors>
<person name="Andrew C. Oliver" email="acoliver@apache.org"/> <person name="Andrew C. Oliver" email="acoliver@apache.org"/>
<person name="Nicola Ken Barozzi" email="barozzi@nicolaken.com"/> <person name="Nicola Ken Barozzi" email="barozzi@nicolaken.com"/>
</authors> </authors>
</header> </header>
<body>
<body> <s1 title="Overview">
<s1 title="Overview"> <p>POIFS is a pure Java implementation of the OLE 2 Compound
Document format.</p>
<p>POIFS is a pure Java implementation of the OLE 2 Compound Document format.</p> <p>By definition, all APIs developed by the POI project are
<p> based somehow on the POIFS API.</p>
By very definition, all APIs developed by the POI project are based somehow <p>A common confusion is on just what POIFS buys you or what OLE
on the POIFS API. 2 Compound Document format is exactly. POIFS does not buy you
</p> DOC, or XLS, but is necessary to generate or read DOC or XLS
<p> files. You see, all file formats based on the OLE 2 Compound
A common confusion is on just what POIFS buys you or what OLE 2 Compound Document Format have a common structure. The OLE 2 Compound
Document format IS exactly. POIFS does not buy you DOC, or XLS Document Format is essentially a convoluted archive
but is necessary to generate DOCs or XLS files. You see all file format. Think of POIFS as a "zip" library. Once you can get
formats based on the OLE 2 Compound Document Format have a common the data in a zip file you still need to interpret the
structure. The OLE 2 Compound Document Format is essentially a data. As a general rule, while all of our formats <b>use</b>
convoluted archive format. Think of POIFS as a "zip" library. So once POIFS, most of them attempt to abstract you from it. There
you can get at the data in a zip file you still need to interperate the are some circumstances where this is not possible, but as a
data. As a general rule, while all of our formats USE POIFS, most of general rule this is true.</p>
them attempt to abstract you from it. There are some circumstances <p>If you're an end user type just looking to generate XLS
where this is not possible, but as a general rule this is ture. files, then you'd be looking for HSSF not POIFS; however, if
</p> you have legacy code that uses MFC property sets, POIFS is
<p> for you! Regardless, you may or may not need to know how to
If you're an enduser type just looking to generate XLS files, then you'd use POIFS but ultimately if you use technologies that come
be looking for HSSF not POIFS; however, if you have legacy code that from the POI project, you're using POIFS underneith. Perhaps
uses MFC property sets. POIFS is for you! Regarless, you may or may we should have a branding campaign "POIFS Inside!". ;-)</p>
not need to know how to use POIFS but ultimately if you use technologies <p>TODO: copy POIFS docs and port to XML (in progress). For now
that come from the POI project, you're using POIFS underneith. Perhaps please reference <link href="http://poi.sourceforge.net">old
we should have a branding campaign "POIFS Inside!". ;-) site</link>.</p>
</p> </s1>
<p> TODO: copy POIFS docs and port to XML. For now please reference <link href="http://poi.sourceforge.net">old site</link>. </body>
</p>
</s1>
</body>
</document> </document>