Re: NSMacOSRomanStringEncoding UnsupportedEncodingException
Re: NSMacOSRomanStringEncoding UnsupportedEncodingException
- Subject: Re: NSMacOSRomanStringEncoding UnsupportedEncodingException
- From: Ramsey Lee Gurley <email@hidden>
- Date: Tue, 18 Nov 2008 15:07:16 -0500
I'm in the midst of upgrading my dev environment and I'm actually
seeing a bit of weirdness related to this. I'm using wonder source
and for some reason all my WOO files automatically converted in
Eclipse from MacRoman to UTF-8... but only in ERExtensions build
8627. In ERDirectToWeb, all the NSMacOSRomanStringEncoding stuff
stayed set to mac roman. Even though I'd prefer it all be UTF-8, the
whole thing was not too helpful because practically every component
shows itself as updated. If I made any changes myself, it would be
next to impossible to see them.
I'm just curious if anyone knows why this would happen or how I can
manipulate that behavior. I just did an update/revert to the latest
(8636) and the UTF-8 is gone from ERExtensions and back to mac roman.
Ramsey
On Nov 18, 2008, at 5:19 AM, Cheong Hee (Datasonic) wrote:
Hi David
If you could check your Component woo file e.g. Main.woo,
NSMacOSRomanStringEncoding is probably coded. I
I noticed that if the component file is created under Eclipse/
Windows, the woo file will be as such:
{"WebObjects Release" = "WebObjects 5.0"; encoding = "UTF-8"; }
However, if the component file I imported from Wonder(e.g.
AjaxExampleComponent.woo from WOAjaxExample), the woo file will be
as such:
{
"WebObjects Release" = "WebObjects 5.0";
encoding = NSMacOSRomanStringEncoding;
}
Not sure if this is the cause, just a hint to check. I did
encounter similar NSMacRomanStringEncoding in Windows but can't
recall if resolved. HTH.
Cheers
Cheong Hee
Message: 4
Date: Mon, 17 Nov 2008 18:17:34 -0500
From: Dov Rosenberg <email@hidden>
Subject: Re: NSMacOSRomanStringEncoding UnsupportedEncodingException
To: Q <email@hidden>, David Avendasora
<email@hidden>
Cc: WebObjects-Dev Mailing List List <email@hidden>
Message-ID: <C54765BE.1C569%email@hidden>
Content-Type: text/plain; charset="us-ascii
You still need to use the localized JDK if you are on Windows
Dov Rosenberg
On 11/17/08 5:26 PM, "Q" <email@hidden> wrote:
Launch tomcat using the JDK instead of the JRE.
On 18/11/2008, at 6:21 AM, David Avendasora wrote:
Okay, I'm stumped.
I'm getting the "java.io.UnsupportedEncodingException:
NSMacOSRomanStringEncoding" error when I load some of my new
Components, but
only the first time the page is requested after a restart.
I've double-checked all my components properties (and verfied in
the .woo
files) that the encoding is set to UTF-8 (or in properties that
it inherits
from the container, which is UTF-8).
Everything I've found with on the lists says that these settings
should fix
this problem, but they don't. I'm running Java 1.6.0_07 on
Windows 2000
Server though Tomcat.
I can't figure out where it's getting something other than UTF-8
in the first
place.
Dave
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
@mac.com
This email sent to email@hidden
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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