Re: ERD2WEditToOneRelationship popup issue with umlauts
Re: ERD2WEditToOneRelationship popup issue with umlauts
- Subject: Re: ERD2WEditToOneRelationship popup issue with umlauts
- From: Chuck Hill <email@hidden>
- Date: Mon, 20 Aug 2012 09:08:10 -0700
Hi Markus,
On 2012-08-20, at 12:46 AM, Markus Ruggiero wrote:
> I seem to have a problem with umlauts and ERD2WEditToOneRelationship with displayStyle = "popup". One of the selections has an umlaut in the name ("Zürich"). The generated code looks like this:
>
> <select _componentname="er.extensions.components.ERXToOneRelationship" name="0.3.5.1.2.3.0.1.0.0.3.1.5.0.1.0.1.3.2.1.3.1.1.0.0.1">
> <option value="- none -">- none -</option>
> <option value="CH-4000 Basel">CH-4000 Basel</option>
> <option selected="selected" value="CH-8000 Zürich">CH-8000 Zürich</option>
> </select>
>
> The problem is that the value also contains the umlaut. The wizard page then complains that the attribute is mandatory. Selecting an entry without umlaut sets the relationship correctly. Changing "Zürich" to "Zuerich" also fixes the problem. However this is not an option for the customer. Is this a bug? Anyone else seen this behaviour? Any work around?
That is a strange problem. Definitely a bug, but I am not sure where. You have set the Wonder encoding properties to use UTF-8? I'd start by logging out the form values from the request to see if it is arriving correctly. Then you can step through WOToOneRelationship (ERD2WEditToOneRelationship subclasses this) and see if you can see why the value is not getting set.
Chuck
--
Chuck Hill Senior Consultant / VP Development
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/gvc/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