# \[F\] v2.38 Unicode bugs with Amazon/Discogs
**URL:** https://community.mp3tag.de/t/f-v2-38-unicode-bugs-with-amazon-discogs/5171
**Category:** Fixed Bugs
**Tags:** bug-fixed
**Created:** [July 21, 2007, 6:04pm UTC](https://community.mp3tag.de/t/f-v2-38-unicode-bugs-with-amazon-discogs/5171 "2007-07-21T18:04:40Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@amp26](https://community.mp3tag.de/u/amp26)
#### Post date: [July 21, 2007, 6:04pm UTC](https://community.mp3tag.de/t/f-v2-38-unicode-bugs-with-amazon-discogs/5171/1 "2007-07-21T18:04:40Z")
There exist multiple bugs in v2.38 when attempting to look up albums in Amazon/Discogs. I'll spell them out here:
**1) HTTP requests are not being URL encoded.** The text entered in the GUI is being put directly into the HTTP request, which fails because the server expects proper URL encoding. An example is this artist:
[http://www.discogs.com/artist/S%C3%A9bastien+L%C3%A9ger](http://www.discogs.com/artist/S%C3%A9bastien+L%C3%A9ger)
Sébastien Léger
If you type that name into the Discogs Artist dialog box, mp3tag makes a request to the server:
70.103.226.22 HTTP GET /artist/S\351bastien+L\351ger HTTP/1.1
This is clearly wrong. If, instead, you type "S%C3%A9bastien+L%C3%A9ger" into the dialog box, it correctly locates the artist.
**2) Amazon/Discogs responses are not being correctly handled as UTF-8.** If you make a request to fetch an album which has non-ASCII UTF-8 encoded characters in it, the dialog shows you garbage in place of the real characters because they are not being translated from UTF-8 back into UTF-16 before being used in Windows and the mp3 tags.
An example album is:
[http://www.discogs.com/release/6439](http://www.discogs.com/release/6439)
If you type in the Discogs search "Isol%C3%A9e" to get around the first bug, and then select the "Rest (CD)" album, you will see garbage in the track listing where it should display "Démon"
---
### Author:  [@micronaut](https://community.mp3tag.de/u/micronaut)
#### Post date: [August 7, 2007, 8:56am UTC](https://community.mp3tag.de/t/f-v2-38-unicode-bugs-with-amazon-discogs/5171/2 "2007-08-07T08:56:36Z")
i encountered the same problem, starting with v2.38, as well as 2.39
basically the search doesnt work with some unicode characters.
example:
Discogs search for _Trentemøller_ = works in 2.37, does not work in 2.38/39
Discogs search for _Pär Grindvik_ = works in 2.37, does not work in 2.38/39
also, the second problem that andrew described happens in the new versions, too.
i switched back to 2.37 now, although it tells me to upgrade everytime i run the program ("the message will not be shown again"..yeah right 😉
is there any chance of getting this fixed, because basically the program is useless for any non-english searches (french accentuation, german umlauts etc.) now.
cheers.
---
### Author:  [@micronaut](https://community.mp3tag.de/u/micronaut)
#### Post date: [August 7, 2007, 9:15am UTC](https://community.mp3tag.de/t/f-v2-38-unicode-bugs-with-amazon-discogs/5171/3 "2007-08-07T09:15:28Z")
i must say, however, that accentuations do not work in 2.37 either
example: _Sébastien Léger_ = does not work in any version.
---
### Author:  [@dano](https://community.mp3tag.de/u/dano)
#### Post date: [August 7, 2007, 12:25pm UTC](https://community.mp3tag.de/t/f-v2-38-unicode-bugs-with-amazon-discogs/5171/4 "2007-08-07T12:25:15Z")
For discogs, it seems to work if you add [Encoding]=utf-8 to the script.
I've changed my scripts, please try it:
[/t/1992/1](https://community.mp3tag.de/t/1992/1)
---
### Author:  [@micronaut](https://community.mp3tag.de/u/micronaut)
#### Post date: [August 7, 2007, 3:13pm UTC](https://community.mp3tag.de/t/f-v2-38-unicode-bugs-with-amazon-discogs/5171/5 "2007-08-07T15:13:27Z")
you're right, that works for the search, but I still get wrong characters displayed when i try to fetch a release containing those characters
> [@dano](#):
>
> For discogs, it seems to work if you add [Encoding]=utf-8 to the script.
> I've changed my scripts, please try it:
> [/t/1992/1](https://community.mp3tag.de/t/1992/1)
---
### Author:  [@dano](https://community.mp3tag.de/u/dano)
#### Post date: [August 7, 2007, 4:29pm UTC](https://community.mp3tag.de/t/f-v2-38-unicode-bugs-with-amazon-discogs/5171/6 "2007-08-07T16:29:33Z")
Yes there's something wrong with the decoding detection.
I hope Florian can find the problem.
---
### Author:  [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [August 19, 2007, 10:16am UTC](https://community.mp3tag.de/t/f-v2-38-unicode-bugs-with-amazon-discogs/5171/7 "2007-08-19T10:16:03Z")
This should be fixed with the latest [Development Build](http://developer.mp3tag.de).
Thanks for reporting!
Kind regards,
Florian
---
### Author:  [@micronaut](https://community.mp3tag.de/u/micronaut)
#### Post date: [September 1, 2007, 9:26am UTC](https://community.mp3tag.de/t/f-v2-38-unicode-bugs-with-amazon-discogs/5171/8 "2007-09-01T09:26:53Z")
seems to be working...thanks!
---
### Author:  [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [December 28, 2018, 1:57pm UTC](https://community.mp3tag.de/t/f-v2-38-unicode-bugs-with-amazon-discogs/5171/9 "2018-12-28T13:57:16Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.