[
https://issues.apache.org/jira/browse/OFBIZ-4915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13292339#comment-13292339
]
Taher Alkhateeb commented on OFBIZ-4915:
----------------------------------------
Well, I'm still investigating this issue. It seems jQuery + AJAX + unicode may
misbehave sometimes. Now the solutions I saw are quite nasty digging to the
heart of code (e.g.
http://stackoverflow.com/questions/2178935/jquery-ajax-call-with-unicode-proper-way-to-post-unicode-data)
My objective is not to touch a single line of jQuery anywhere, It should simply
be some declaration in CommonScreens.xml of the common component to add unicode
support using "layoutSettings.javaScripts[+0]=YourFixHere". However, I'm just
not sure what happens after declaring these lookup fields, where the code is
executed and what is exactly called. I tried tracing ConfigXMLReader but got
lost quickly into it.
I will continue to work some more, but appreciate any push I can get on this.
> Lookup Form not working with Arabic characters
> ----------------------------------------------
>
> Key: OFBIZ-4915
> URL: https://issues.apache.org/jira/browse/OFBIZ-4915
> Project: OFBiz
> Issue Type: Bug
> Components: ALL COMPONENTS
> Affects Versions: Release Branch 11.04, Release Branch 12.04
> Reporter: Taher Alkhateeb
> Assignee: Jacques Le Roux
> Priority: Minor
> Labels: form, jQuery, javascript, lookup
> Attachments: search_party_after_submit.png,
> search_party_before_submit.png
>
>
> Any field in a form that uses the <lookup target-form-name="WhateverForm"/>
> would not return results when searching in Arabic. I suspect the main
> offender is javascript/jQuery when parsing user input.
> For example, if I go to https://localhost:8443/ordermgr/control/findorders
> and click on "Party ID", and search the firstname or lastname in arabic, no
> values are returned and the value in the search box changes from arabic to
> some weird encoding ( e.g. "حسن" becomes Øس٠)
> Also, after some investigation, I came to the realization that this only
> happens when the lookup field has presentation="layer", if however, the
> presentation="window" then it works normally which leads me to conclude
> definitely that this is javascript/jQuery issue of parsing input data. More
> specifically, this is javascript not processing with the correct encoding
> (unicode in this case). I know this because if I paste the unicode
> representation directly to the input box then it searches correctly
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
