• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: UTF-8 multilingual form input
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: UTF-8 multilingual form input


  • Subject: Re: UTF-8 multilingual form input
  • From: Chuck Hill <email@hidden>
  • Date: Thu, 8 Dec 2005 11:05:44 -0800


On Dec 8, 2005, at 3:11 AM, Ralph Scheuer wrote:

Hi everybody,

we have an application with UTF-8 HTML encoding where we input multilingual form data (Czech, Polish, English, German, Slovenian, Russian, Bulgarian, Turkish, etc.). This works in almost every case. It _always_ works for cyrillic input and in most cases, for all other languages.

However, in some cases, special latin characters in some languages are not displayed correctly. In these cases, the string values are already stored in the database in the wrong manner.

It sounds like it is guessing the encoding and getting it wrong on some cases. Are you setting the form value encoding on the request when it arrives using
setFormValueEncodingDetectionEnabled(false) and setDefaultFormValueEncoding("UTF-8")?


"public String defaultFormValueEncoding()
Returns the default string encoding the WORequest object uses for converting form values from ASCII to Unicode. It uses the default encoding only when it can detect no encoding from the ASCII form values or if encoding detection is disabled. The current set of encodings supported is detailed in http://java.sun.com/j2se/1.3/docs/ guide/intl/encoding.doc.html If no default form-value encoding is set, WOMessage's defaultEncoding is used."




The strange thing about this is that this is not always reproducible - certain special characters (such as accented characters in slawic languages) are sometimes stored correctly and sometimes not. For that reason, I cannot be more specific here...

The browsers used for the input are Safari and Firefox on the Mac. Both browsers behave identically in cases where the input is not stored correctly. The application itself is deployed on OS X, the database we use is Frontbase.

Any general hints?

It still sounds like it is guessing the encoding and getting it wrong.


Chuck

--
Coming in 2006 - an introduction to web applications using WebObjects and Xcode http://www.global-village.net/wointro


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@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >UTF-8 multilingual form input (From: Ralph Scheuer <email@hidden>)

  • Prev by Date: Switching to document style...
  • Next by Date: Re: Request for feedback on proposed project
  • Previous by thread: UTF-8 multilingual form input
  • Next by thread: How to install JavaMail
  • Index(es):
    • Date
    • Thread