[
https://issues.apache.org/jira/browse/OFBIZ-4661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux closed OFBIZ-4661.
----------------------------------
Resolution: Fixed
Fix Version/s: SVN trunk
Release Branch 11.04
Thanks Christoph,
Post uses ISO-8859-1 as default encoding. But as we set a charset=UTF-8 in our
header all characters should be handled correly (i18n concern)
Your (modified format) patch is in
trunk r1232053
R11.04 r1232055
The reason I had to modify the patch is:
can't find file to patch at input line 4
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff -r 4ad21eb7c9ae -r d04a701f13c6
framework/images/webapp/images/selectall.js
|--- a/framework/images/webapp/images/selectall.js Mon Jan 16 15:27:47
2012 +0100
|+++ b/framework/images/webapp/images/selectall.js Mon Jan 16 16:17:46
2012 +0100
--------------------------
Then after removing the a/ /b, I got this
patching file framework/images/webapp/images/selectall.js
Hunk #1 succeeded at 411 (offset 4 lines).
Not sure what the problem with the format was (and not much time to think about
it ;o)
> Autocomplete / Suggest does not work with umlauts
> -------------------------------------------------
>
> Key: OFBIZ-4661
> URL: https://issues.apache.org/jira/browse/OFBIZ-4661
> Project: OFBiz
> Issue Type: Bug
> Components: framework
> Affects Versions: SVN trunk
> Reporter: Christoph Neuroth
> Assignee: Jacques Le Roux
> Fix For: Release Branch 11.04, SVN trunk
>
> Attachments: ofbiz-4661.patch
>
>
> Steps to Reproduce:
> * Change the internal_name of a product to "Kochlöffel" (that's German for
> cooking spoon. Just in case you ever need one while in a German-speaking
> country and don't have a dictionary handy).
> * Go to the catalog and use the product search box to the left to search for
> "Koch", you should see the product as a suggestion
> * Clear the input field and search for "löffel" instead -> the product is
> not found.
> The reason for this is that the special characters have to be url encoded for
> the GET request, but are never decoded. Easiest way to fix this is just to
> use a POST request instead.
--
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