Hi All.
I'm just wondering if anyone on the list has had recent contact with the folks
at Frontbase. I have tried multiple times with no response.
Thanks!
-Kenny
___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailin
Sorry, that URL was:
http://www.surfshacksoftware.com/FreeSoftware/EncodingTest.tar.gz
-Kenny
___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update y
te:
I don't claim to be any expert in encodings, but are you sure
ISO8895_1 is a valid encoding name, or even the encoding that you
want? Are you trying to get ISO-LATIN-1 or ISO-8859-1 ?
-Ryan
On Jun 24, 2008, at 2:30 PM, Kenny Leung wrote:
Hi All.
So, after extensive testing w
e
only thing that works is to go along with the default UTF-8 behaviour.
-Kenny
On Jun 24, 2008, at 2:07 PM, Daryl Lee wrote:
Is WORequest.isFormValueEncodingDetectionEnabled() turned on? What
happens if you turn it off/on?
On Jun 23, 2008, at 10:16 AM, Kenny Leung wrote:
Hi Alan.
Setting the page's charset seems to have the side effect of setting
the default form encoding for the page. Thanks for the tip though...
-Kenny
On Jun 24, 2008, at 10:04 AM, Alan Ward wrote:
On Jun 24, 2008, at 10:56 AM, Kenny Leung wrote:
I've figured it out - y
I've figured it out - you have to stick in a meta tag to force the
browser to use UTF-8. Something like.
Some stuff...
Note that I simply cannot get it to work with ISO8859_1 encoding.
-Kenny
On Jun 23, 2008, at 10:16 AM, Kenny Leung wrote:
Hi All.
I've bump
Hi All.
I've bumped into an incompatibility between WebObjects 5.3 and 5.4.
In 5.3, I could submit a form value with non-ASCII characters, and
their encoding would be correctly interpreted. In 5.4, the encoding
is misinterpreted.
I printed out the actual request contents, and, for instanc
