moparisthebest/poi
1
0
Fork 0
Code Issues Pull Requests Releases 1 Wiki Activity

Made it explicit that you need J2SE 1.4 or better for a reasonable codepage support.

Browse Source 
git-svn-id: https://svn.apache.org/repos/asf/jakarta/poi/trunk@353580 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Rainer Klute 2004-08-13 20:42:04 +00:00
parent 7bfd22842b
commit e6d500243c
1 changed files with 7 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
src/documentation/content/xdocs/hpsf/how-to.xml
View File

@ -849,14 +849,17 @@ No property set stream: "/1Table"</source>
receive a document from another region of the world and the codepage is
undefined, you are in trouble.</p>
<p>HPSF's codepage support is as good as the character encoding support of
the Java Virtual Machine (JVM) the application runs on. If HPSF
encounters a codepage number it assumes that the JVM has a character
<p>HPSF's codepage support is only as good as the character encoding
support of the Java Virtual Machine (JVM) the application runs on. If
HPSF encounters a codepage number it assumes that the JVM has a character
encoding with a corresponding name. For example, if the codepage is 1252,
HPSF uses the character encoding "cp1252" to read or write strings. If
the JVM does not have that character encoding installed or if the
codepage number is illegal, an UnsupportedEncodingException will be
thrown.</p>
thrown. This works quite well with Java 2 Standard Edition (J2SE)
versions since 1.4. However, under J2SE 1.3 or lower you are out of
luck. You should install a newer J2SE version to process codepages with
HPSF.</p>
<p>There are some exceptions to the rule saying that a character
encoding's name is derived from the codepage number by prepending the