These are not necessarily deemed to be high enough quality to be included in the
core distribution, but they have been tested under
@@ -32,18 +31,18 @@
listed below will eventually migrate to the "contributed components" level, and
then maybe even into the main distribution.
-
+
-
+
Submissions of modifications
to Poi which are awaiting review. Anyone can
comment on them on the dev mailing list - code reviewers are needed!
Use these at your own risk - although Poi has no guarantee
either, these patches have not been reviewed, let alone accepted.
-
+
-
+
The other extensions listed here are not endorsed by the Poi
project either - they are provided as a convenience only. They may or may not work,
they may or may not be open source, etc.
@@ -63,6 +62,6 @@
-
The POI Project is an Open Source
@@ -48,9 +48,9 @@
we have work for you! And we'll be very available to you for any questions!
-
+
-
+
The rest of this document is mainly about
contributing new or improved code and/or documentation, but we would also be glad to have
@@ -81,10 +81,10 @@
-
+
-
+
An overview of how to use CVS to participate in POI development.
Do not be afraid - you cannot accidently destroy the actual code repository,
because you are working with a local copy as an anonymous user.
@@ -105,9 +105,9 @@
repository, how to keep it up-to-date, and how to generate the differences
to create a patch. (The commands are for Linux.)
-
+
-
+
After a developer has consistently provided contributions (code,
documentation and discussion), then the rest of the dev community
may vote to grant this developer commit access to CVS.
@@ -125,10 +125,10 @@
- See the bottom of the page for links to tips for UNIX and Windows.
Even if you are on UNIX, the Windows page will also help.
-
+
-
+
There are two methods for discussing development and submitting patches.
So that everyone can be productive, it is important to know which method
@@ -178,10 +178,10 @@
posting - perhaps it was not clear enough
and the readers' eyes glazed over.
-
+
-
+
This is a collection of tips for contributing to the project in a manner
that is productive for all parties.
@@ -273,7 +273,7 @@
see the way other people do things. Follow the leading examples.
-
+
diff --git a/src/documentation/xdocs/faq.xml b/src/documentation/xdocs/faq.xml
index 79b63a6b38..7934dfd6e8 100644
--- a/src/documentation/xdocs/faq.xml
+++ b/src/documentation/xdocs/faq.xml
@@ -32,9 +32,10 @@
Why am I getting an exception each time I attempt to read my spreadsheet?
+
It's possible your spreadsheet contains a feature that is not currently supported by HSSF.
For example - spreadsheets containing cells with rich text are not currently supported.
+
HDF will be the name of OUR port of the Microsoft Word 97(-2002) file format to
pure Java.
@@ -20,6 +20,6 @@
follow development on the poi-dev mailing list.
-
+
diff --git a/src/documentation/xdocs/historyandfuture.xml b/src/documentation/xdocs/historyandfuture.xml
index ae26b195ce..3855480f69 100755
--- a/src/documentation/xdocs/historyandfuture.xml
+++ b/src/documentation/xdocs/historyandfuture.xml
@@ -12,7 +12,7 @@
-
+
The POI project was dreamed up back around April 2001, when
Andy Oliver landed a short term contract to do Java-based
@@ -76,9 +76,9 @@ already started making waves.
looks like everything turned out since you're reading this!
-
+
-
+
First we'll tackle this from a project standpoint: Well, we
made an offer to Microsoft and Actuate (tongue in cheek
... well mostly) that we'd quit the project and retire if
@@ -120,7 +120,7 @@ already started making waves.
that new blood will join the team and allow us to tackle this
even faster (in part because POIFS is already finished). But
maybe what we need most is you!