• 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 forms and database, still some special characters get through as things like fi Why?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: UTF-8 forms and database, still some special characters get through as things like fi Why?


  • Subject: Re: UTF-8 forms and database, still some special characters get through as things like fi Why?
  • From: Pascal Robert <email@hidden>
  • Date: Sun, 10 Jan 2010 20:28:22 -0500


Le 10-01-10 à 20:12, Ramsey Lee Gurley a écrit :


On Nov 13, 2009, at 4:04 AM, Pascal Robert wrote:


----- "Johan Henselmans" <email@hidden> a écrit :

Op 12 nov 2009, om 14:44 heeft Pascal Robert het volgende geschreven:


6) Localizable.strings should be encoded in UTF-16

And to be more specific, they should be in UTF-16LE



What happens if you use UTF-16 or UTF-16BE?

In my case, WO wasn't able to find the strings, they only load if I use UTF-16LE with BOM (I do my encoding conversion in BBEDit, I don't trust Eclipse for this task).

I wonder what version of WO you are using Pascal. I'm running 5.4.3 and I'm getting the opposite here... If I use UTF-16BE with no BOM on my .strings files, everything works fine.

We are on 5.3.3/WOLips 3.3 at work, but I'm pretty sure that I tried it for the wocommunity.org stuff on 5.4.3.


If I try to use LE with or without BOM, I'm getting a partially translated page and plist parsing errors (once for each .strings file in UTF-16LE) like the stack trace at the end of this email. Only UTF-16BE with no BOM works for me. If I insert a bom using hexedit for either format, I get "At line number: 1, column: 0" instead of column 1. So, it appears to choke on the bom itself too.

Yes, my mistake, we don't use a BOM, if we do, we get the same problem as you described. So the only difference seems to be LE versus BE. I will try to test it this week with BE.



WARN (ERXLocalizer.java:531) - Exception loading: Localizable.strings - app - ("English"):java.lang.IllegalArgumentException: Property list parsing failed while attempting to read unquoted string. No allowable characters were found. At line number: 1, column: 1.
java.lang.IllegalArgumentException: Property list parsing failed while attempting to read unquoted string. No allowable characters were found. At line number: 1, column: 1.
at com.webobjects.foundation.NSPropertyListSerialization $ _ApplePList ._readUnquotedStringIntoStringBuffer (NSPropertyListSerialization.java:1257)
at com.webobjects.foundation.NSPropertyListSerialization $ _ApplePList ._readObjectIntoObjectReference(NSPropertyListSerialization.java:1241)
at com.webobjects.foundation.NSPropertyListSerialization $ _ApplePList ._readDictionaryContentsIntoDictionary (NSPropertyListSerialization.java:1437)
at com.webobjects.foundation.NSPropertyListSerialization $ _ApplePList ._readObjectIntoObjectReference(NSPropertyListSerialization.java:1237)
at com.webobjects.foundation.NSPropertyListSerialization $_ApplePList.parseStringIntoPlist(NSPropertyListSerialization.java: 1069)
at com .webobjects .foundation .NSPropertyListSerialization .propertyListFromString(NSPropertyListSerialization.java:1669)
at com .webobjects .foundation .NSPropertyListSerialization .propertyListFromString(NSPropertyListSerialization.java:1646)
at er .extensions .foundation .ERXFileUtilities .readPropertyListFromFileInFramework(ERXFileUtilities.java:775)
at er .extensions .foundation .ERXFileUtilities .readPropertyListFromFileInFramework(ERXFileUtilities.java:735)
at er .extensions .ERXExtensions .readPropertyListFromFileInFramework(ERXExtensions.java:826)
at er.extensions.localization.ERXLocalizer.load(ERXLocalizer.java: 509)
at er.extensions.localization.ERXLocalizer.<init>(ERXLocalizer.java: 482)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun .reflect .NativeConstructorAccessorImpl .newInstance(NativeConstructorAccessorImpl.java:39)
at sun .reflect .DelegatingConstructorAccessorImpl .newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at er .extensions .localization .ERXLocalizer.createLocalizerForLanguage(ERXLocalizer.java:424)
at er .extensions .localization.ERXLocalizer.localizerForLanguage(ERXLocalizer.java:301)
at er .extensions .localization.ERXLocalizer.localizerForLanguages(ERXLocalizer.java: 280)
at er.extensions.appserver.ERXSession.setLanguages(ERXSession.java: 238)
at com.webobjects.appserver.WOSession.languages(WOSession.java:1198)
at er.extensions.appserver.ERXSession.localizer(ERXSession.java:175)
at er.extensions.appserver.ERXSession.awake(ERXSession.java:418)
at com.example.app.Session.awake(Session.java:54)
at com.webobjects.appserver.WOSession._awakeInContext(WOSession.java:838)
at com .webobjects .appserver .WOApplication._initializeSessionInContext(WOApplication.java:2120)
at com .webobjects .appserver ._private .WOComponentRequestHandler ._dispatchWithPreparedApplication(WOComponentRequestHandler.java:319)
at com .webobjects .appserver ._private .WOComponentRequestHandler ._handleRequest(WOComponentRequestHandler.java:369)
at com .webobjects .appserver ._private .WOComponentRequestHandler .handleRequest(WOComponentRequestHandler.java:442)
at com .webobjects .appserver.WOApplication.dispatchRequest(WOApplication.java:1687)
at er .extensions .appserver .ERXApplication.dispatchRequestImmediately(ERXApplication.java:1915)
at er .extensions .appserver.ERXApplication.dispatchRequest(ERXApplication.java:1880)
at com .webobjects .appserver._private.WOWorkerThread.runOnce(WOWorkerThread.java:144)
at com .webobjects .appserver._private.WOWorkerThread.run(WOWorkerThread.java:226)
at java.lang.Thread.run(Thread.java:637)





_______________________________________________ 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: 
 >Re: UTF-8 forms and database, still some special characters get through as things like &#64257; Why? (From: Ramsey Lee Gurley <email@hidden>)

  • Prev by Date: Re: UTF-8 forms and database, still some special characters get through as things like &#64257; Why?
  • Next by Date: Javaconverter where to find it?
  • Previous by thread: Re: UTF-8 forms and database, still some special characters get through as things like &#64257; Why?
  • Next by thread: Javaconverter where to find it?
  • Index(es):
    • Date
    • Thread