On Feb 3, 2009, at 6:23 PM, David LeBer wrote:
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.
I'll just piggy back on David's thoughts. If you are doing something
for the web, UTF-8 is the right choice. MacRoman, clearly, is not.
Wonder goes to a bit of trouble to ensure that everything is
consistently UTF-8.
Chuck
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
