diff --git a/src/documentation/content/xdocs/book.xml b/src/documentation/content/xdocs/book.xml
index 37d664d29a..f7a1247b15 100644
--- a/src/documentation/content/xdocs/book.xml
+++ b/src/documentation/content/xdocs/book.xml
@@ -28,35 +28,8 @@
Apache POI releases are available under the Apache License, Version 2.0.
@@ -81,15 +81,6 @@
-
- Only current recommended releases are available on the main distribution site and its mirrors.
- Older releases are available from the
- archive
- download site.
-
diff --git a/src/documentation/content/xdocs/faq.xml b/src/documentation/content/xdocs/faq.xml
index 8a5d51bb3f..a0cd7b8b80 100644
--- a/src/documentation/content/xdocs/faq.xml
+++ b/src/documentation/content/xdocs/faq.xml
@@ -22,13 +22,13 @@
You almost certainly have an older version of POI earlier
+ You almost certainly have an older version of POI
on your classpath. Quite a few runtimes and other packages
will ship an older version of POI, so this is an easy problem
- to hit without realising. The best way to identify the offending earlier jar file is
with a few lines of java. These will load one of the core POI
classes, and report where it came from. You almost certainly have an older version earlier on your
- classpath. See the answer to the similar question above for
- how to track this down.
You've probably enabled logging. Logging is intended only for
- autopsie style debugging. Having it enabled will reduce performance
+ autopsy style debugging. Having it enabled will reduce performance
by a factor of at least 100. Logging is helpful for understanding
why POI can't read some file or developing POI itself. Important
errors are thrown as exceptions, which means you probably don't need
@@ -68,10 +67,10 @@ System.out.println("Core POI came from " + path);
What is the HSSF "eventmodel"?
The HSSF eventmodel package is a new API for reading XLS files more efficiently. It does
+ The SS eventmodel package is an API for reading Excel files without loading the whole spreadsheet into memory. It does
require more knowledge on the part of the user, but reduces memory consumption by more than
tenfold. It is based on the AWT event model in combination with SAX. If you need read-only
- access to a given XLS file, this is the best way to do it.
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.
+It's possible your spreadsheet contains a feature that is not currently supported by POI. + If you encounter this then please create the simplest file that demonstrates the trouble and submit it to + Bugzilla.
Protecting a spreadsheet encrypts it. We wont touch encryption because we're not legally educated - and don't understand the full implications of trying to implement this. If you wish to have a go - at this feel free to add it as a plugin module. We wont be hosting it here however.
-Excel stores dates as numbers therefore the only way to determine if a cell is actually stored as a date is to look at the formatting. There is a helper method - in HSSFDateUtil (since the 1.7.0-dev release) that checks for this. + in HSSFDateUtil that checks for this. Thanks to Jason Hoffman for providing the solution.
- Yes. This is a built-in format for excel that you can get from HSSFDataFormat object using the format string "@". Also, the string "text" will alias this format. + Yes. This is a built-in format for excel that you can get from DataFormat object using the format string "@". Also, the string "text" will alias this format.
By default HSSF uses cell values and sheet names as compressed unicode, - so to support localization you should use Unicode. - To do it you should set it manually:
- -- Make sure you make the call to setEncoding() before calling setCellValue(), otherwise what you pass in won't be interpreted properly. -
-Make sure you have fix pack 4 installed.
-POI is not guanteed to read the contents of any spreadsheet. - Certain features may cause spreadsheets to fail to read. More - problematic is rewriting spreadsheets. POI tried hard to - preserve the records of the original spreadsheet but some - features may cause problems. We advise that you limit the - formatting of spreadsheets you process so as to not be - unpleasantly suprised at a later stage.
-Most users of the source code probably don't need to have day to day access to the source code as it changes. For these users we - provide easy to unpack source code downloads via our - download pages. + provide easy to unpack source code from releases via our + download page.
NOTE: See this - Subversion - information page for a brief description of the relationship be - tween URL tuples such as trunks-proper and proper.
-