I can't make use of the umlaute (äüö) when searching items. For the use in a language with special characters this is quite crucial.
A dirty workaround is to let out the umlaute and making amazon guess the 'right' therm.

CommentFileSizeAuthor
#8 AMAZONTOOLS_ISO8859.txt2.97 KBPrometheus6

Comments

Prometheus6’s picture

Prometheus6 commented

Do you mean you can't enter the characters in the search?

Prometheus6’s picture

Prometheus6 commented

I just checked at Amazon...they have an open issue where the default encoding should be UTF-8 but is ISO-8859-1. I think that's the problem, and since Amazon has it as an open issue I don't think I should mess with it

miguel’s picture

miguel commented

Thanks for your comment.
Yes it is a issue concerning encoding.

Why not create a *option* to decode the input string into ISO-8859-1 as long this issue is open @amazon?
When the issue is solved, one can turn this option off.

Prometheus6’s picture

Prometheus6 commented

Not that I can promise to do this immediately...I'm planning the next version to go with the 4.7 release right now...but I don't know enough yet to know it's necessary. That's why I asked if your problem was with input or getting search results.

I just did a search on Gödel at amazon.de and it worked fine.

miguel’s picture

miguel commented

> I just did a search on Gödel at amazon.de and it worked fine.

You did the search @amazon.de or via your drupal installation?
If you did the search via drupal did you get *any* search results (so do I!) or results with 'Gödel' in it?

Try 'Anführer' via drupal. You won't get a match if 'ä' isn't properly recognised.
In my case I don't get any results with 'Anführer'. Sometimes a get some results (e.g. in the case of Göbel) but not with the searched therm in it.
From my point of view the search query has the wrong encoding because we send it a utf-8 but amazon expects it as iso 8859-1.
If I search something with 'ä' the amazon api can't recognise it as a 'ä' but a as a 'ä' (this is the 'ä' in utf-8 displayed as iso 8859-1).

If we encode the input string which is utf-8 to iso 8859-1 before sending it to the amazon api it should work.

Just my 2cent.

Prometheus6’s picture

Prometheus6 commented
Assigned: Unassigned » Prometheus6

The wonderful thing about standards is there are so many of them.

You did the search @amazon.de or via your drupal installation?

Via a local install of Drupal...which, being Windows, uses ISO-8859-1 internally...and so apparently sends ISO-8859-1 to Amazon. Trying it via one of my public sites, which all run Linux, it fails. So that's confirmation of the problem.

And thinking about it, this all probably means Amazon data stored as ISO-8859-1 in its databases, which means it could be a while before they get to it. So. I'll be looking into this soon.

miguel’s picture

miguel commented

Thanks ;-)

Prometheus6’s picture

Prometheus6 commented
StatusFileSize
new AMAZONTOOLS_ISO8859.txt2.97 KB

Okay, I've got it working. Thing is, there's an optional PHP module that 99% of sites will have, the iconv module. If you do NOT have, the module will work as it does now...you can tell by running the famous phpinfo() script. If you DO have it, then your query strings will be converted to UTF-8 and all is golden.

Prometheus6’s picture

Prometheus6 commented
Status: Active » Needs review
Prometheus6’s picture

Prometheus6 commented
Status: Needs review » Fixed

fixed in cvs

Anonymous’s picture

(not verified) commented
miguel’s picture

miguel commented
Version: » master

I just want to inform you that I'm waiting for my hoster to fix a problem with inconv. If you like I can post again when I'm able to test your patch on my server.

Prometheus6’s picture

Prometheus6 commented

Sure. That's why I haven't closed it yet. I've tested it pretty thoroughly but confirmation is always good.

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)