• 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: Is this an encoding problem???
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Is this an encoding problem???


  • Subject: Re: Is this an encoding problem???
  • From: Theodore Petrosky <email@hidden>
  • Date: Tue, 10 Mar 2009 11:30:06 -0700 (PDT)

thank you ,  thank you....

you were correct, the first section was in my pagewrapper.... so I added the lines to the properties file, restarted the app and it's good to go...

so I didn't need the change to the Application.java.

Ted

--- On Tue, 3/10/09, David Holt <email@hidden> wrote:

> From: David Holt <email@hidden>
> Subject: Re: Is this an encoding problem???
> To: "Theodore Petrosky" <email@hidden>
> Cc: email@hidden
> Date: Tuesday, March 10, 2009, 1:55 PM
>
> Hi Theodore, 
> My answer to your question is inline below.
>
> A question for WOnderers: is there any good
> reason for not setting encoding to UTF-8 in the WOnder
> project templates? Does it slow down performance compared to
> the current default?
>
> On
> 10-Mar-09, at 10:22 AM, Theodore Petrosky
> wrote:
>
> I
> never had to do anything special in the past to account for
> accented characters  
> (ñ é) ...
> I
> just started a new Wonder project and I am testing data
> input and I notice that instead of seeing  Señor, I see in the
> database 
> Señor (this also shows on the screen when I read
> the data into a web page).
> My
> database (postgresql) is set up with UTF-8 encoding and as I
> said this always worked (correctly) in the past.
> Do
> I need to turn on something or change a configuration so the
> user can type a option-n followed by an n to lget an enyay
> on the mac?
> I believe if you take the following steps you will be
> good to go:
> I make sure that this is in the head of all my
> HTML pages (easiest place to put it is in a PageWrapper
> component)
> <meta http-equiv = "Content-Type"
> content = "text/html;
> charset=UTF-8" />
> This should be in your properties file:
> # Project Encodingpackage.name.Application.setDefaultMessageEncoding=trueer.extensions.ERXApplication.DefaultEncoding=UTF-8
>
> and I have this in my Application.java (it might
> be redundant after setting the properties, you'd have to
> check)
> 	// to have the
> web pages display foreign characters	private boolean enableUTFEncoding = false;
> 	public void enableUTFEncoding()
> {		enableUTFEncoding = true;		WOMessage.setDefaultEncoding(_NSUtilities.UTF8StringEncoding);	}
> David
>
>
> Ted
>
>
>  _______________________________________________Do
> not post admin requests to the list. They will be
> ignored.Webobjects-dev
> mailing list     
> (email@hidden)Help/Unsubscribe/Update
> This
> email sent to email@hidden
>
>



 _______________________________________________
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

  • Follow-Ups:
    • Re: Is this an encoding problem???
      • From: Amedeo Mantica <email@hidden>
  • Prev by Date: Re: AjaxUpdateLink's action not getting called
  • Next by Date: Re: Is this an encoding problem???
  • Previous by thread: Re: Is this an encoding problem???
  • Next by thread: Re: Is this an encoding problem???
  • Index(es):
    • Date
    • Thread