Re: Opinions Please - WebObjects JVM Encoding Strategies
Re: Opinions Please - WebObjects JVM Encoding Strategies
- Subject: Re: Opinions Please - WebObjects JVM Encoding Strategies
- From: David LeBer <email@hidden>
- Date: Tue, 3 Feb 2009 21:23:46 -0500
On 3-Feb-09, at 8:23 PM, Gaastra Dennis - WO Lists wrote:
Dear List,
cc: Piere Frish - WebObjects Visionary
We noticed that our PDFkit does not work properly with the newest
Eclipse/WOLips 3.4.
It turns out that when applications launch from the newest Eclipse,
they have the property:
file.encoding=UTF-8 - Our PDFkit produces special characters
incorrectly
previously with Eclipse 3.3.X, and still case with deployment:
file.encoding=MacRoman - All OK
Now what is the best strategy going forward?
- Force the property to always be MacRoman with System.setProperty
or -Dfile.encoding=; or
- Force the property to always be UTF-8 + redo all our PDF fonts for
UTF-8; or
- any ideas?
Please advice, as we want to announce the newest PDFkit 5.4.3 soon!
Thanks.
Dennis,
I can only speak from our experience, and we currently have no
requirement for a PDF framework, so take this in that light, but we
have been using UTF-8 encoding exclusively for all WO apps and DBs for
several years now. Knowing the grief it caused before we standardized
and got everything aligned, I think we would be hesitant to use any
third party framework that didn't fully support UTF-8.
;david
--
David LeBer
Codeferous Software
'co-def-er-ous' adj. Literally 'code-bearing'
site: http://codeferous.com
blog: http://davidleber.net
profile: http://www.linkedin.com/in/davidleber
twitter: http://twitter.com/rebeld
--
Toronto Area Cocoa / WebObjects developers group:
http://tacow.org
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden