Am Mittwoch, den 09.11.2005, 07:25 -0500 schrieb [EMAIL PROTECTED]: > We should be universally handling the issues mentioned here: > http://en.wikipedia.org/wiki/Windows-1252 by intercepting character > differences and writing them out properly. Thus HSSF should force > 8859-1 encoding but should then kind of do a replace on the characters. > If someone wants to contribute I can point them in the right direction.
Um, no. Enforcing ISO 8859-1 as character code would be of limited use
only. These reason is that like Windows Codepage 1252 it represents only
a limited set of characters. UTF-8 is the preferred character encoding.
However, POI should not forbid to create strings in other character
encodings, be it ISO 8859-1, cp1252 or whatever.
By the way, HPSF does a nice job of supporting a lot of different
character encodings. At least there are no problems I am aware of. I
suggest you have a look at it.
Best regards
Rainer Klute
Rainer Klute IT-Consulting GmbH
Dipl.-Inform.
Rainer Klute E-Mail: [EMAIL PROTECTED]
Körner Grund 24 Telefon: +49 172 2324824
D-44143 Dortmund Telefax: +49 231 5349423
Public key fingerprint: E4E4386515EE0BED5C162FBB5343461584B5A42E
signature.asc
Description: This is a digitally signed message part
