• 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: WOResourceManager and localization issue
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: WOResourceManager and localization issue


  • Subject: Re: WOResourceManager and localization issue
  • From: Jean-François Veillette <email@hidden>
  • Date: Thu, 8 Dec 2005 14:23:13 -0500

WOResourceManager try to 'guess' the encoding of the file.
For all 8bits encoding, it cannot guess it and revert to ISO-Latin1.
The only way for WOResourceManager to guess it properly is to use UTF-16.


- jfv


Le 05-12-08, à 14:15, Miguel Arroz a écrit :

Hi!

I'm reading a string from a .strings file that contains accentuated characters. The code is the following:

public static String portugueseLanguageName() {
return Application.application().resourceManager().stringForKey(Session.PORTUG UESE_LANGUAGE_KEY,
Application.RESOURCES_DEFAULT_TABLE_NAME,
"PT",
null,
new NSArray(new Object[] {"Portuguese"}));
}


The file is in XML format and was created with Property List Editor. Any attempt to create the file using a normal text editor results in parsing error at the first character. Even opening and saving the file without modifications in TextWrangler originates an error (anyone knows why?).

Well, but my problem is far more serious. I'm using that string to fill one of the items of a pop up menu on a page. I have followed all the UTF-8 related precautions, overloadings, etc, explained on Chuck's book. Still, instead of Português, I get some strange characters (like russian or greek) instead of the accentuated ê.

I try to write some accentuated text on a component, and save it has UTF-8. WebObjects builder 5.3.1 appears to always save those characters using escape characters, like &eacute; instead of é. Nevertheless, I edited the .woo file to set the right encoding, and editied the .html file in TextWrangler, restoring the real accentuated characters. It works! That appear on the browser as they should. The only problem is the pop-up menu made with strings that come from a .strings file, so my guess is that the problem is related to the file reading/decoding.

I find this strange, as the .strings method is mentioned on chuck's book, so I guess it should work... what the heck is going on here?

  Yours

Miguel Arroz

"The world lies in the hands of evil
 And we pray it would last" -- Apocalyptica, Life Burns!

Miguel Arroz
http://www.ipragma.com




_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden


This email sent to email@hidden


http://www.freeiPods.com/?r=21419063

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
_______________________________________________
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: WOResourceManager and localization issue
      • From: Chuck Hill <email@hidden>
References: 
 >WOResourceManager and localization issue (From: Miguel Arroz <email@hidden>)

  • Prev by Date: WOResourceManager and localization issue
  • Next by Date: Help deciphering SocketException, (anchor problem)
  • Previous by thread: WOResourceManager and localization issue
  • Next by thread: Re: WOResourceManager and localization issue
  • Index(es):
    • Date
    • Thread