Closed (fixed)
Project:
Delicious
Version:
6.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Bug report
Reporter:
Created:
7 Feb 2008 at 19:59 UTC
Updated:
6 Feb 2009 at 14:30 UTC
Jump to comment: Most recent
Characters with umlauts aren't handled correctly in delicious link titles. This looks like an encoding problem.
If you have any questions recarding encodings you can contact me.
Comments
Comment #1
chrislb commentedI should add, that I'm using MySQL 4 which doesn't have any support for Unicode character sets. It is though possible to store everything as binary data.
Chinese characters are also rendered as complete garbage.
Comment #2
Anonymous (not verified) commentedThanks Chris ,
Apologies for not getting back to you sooner.
I don't have much experience with encoding and characters sets. Would you be interested in looking into what needs to be done and submitting patches for testing ?
Paul
Comment #3
Anonymous (not verified) commentedComment #4
chrislb commentedHey, I probably won't find the time in the near future, but knowing that somebody cares for the packet might trigger some plans on doing so.
Chris
Comment #5
chrislb commentedWhat fixed the problem for me was actually uncommenting the online line that had to do something with Unicode:
--- delicious.module_old 2008-09-23 14:14:16.000571000 +0200
+++ delicious.module 2008-09-23 14:09:01.000120000 +0200
@@ -960,6 +960,6 @@
function start_element($parser, $name, $attrs) {
if ($attrs["DESCRIPTION"] != '') {
- $desc = db_escape_string(utf8_decode($attrs["DESCRIPTION"]));
+ $desc = db_escape_string($attrs["DESCRIPTION"]);
$href = db_escape_string($attrs["HREF"]);
$tags = split(' ', $attrs["TAG"]);
if ($attrs["EXTENDED"] != '') {
It seems that delicious returns UTF-8 encoded strings here. I don't know enough about php and the delicious api and the module here to say what would be the right solution. Removing it will actually treat the string as a binary input and store it as it is into mysql. It works for me as my locale seems to be utf8, but this solution might not work for others. I don't know why a decode method is used if no encoding takes place later in the output step.
Comment #6
chandar commentedI am not sure whether what I face is also same issue. I use UNICODE (for language Tamil) for content in the story and when pre-viewed before saving, the content is displayed properly but when saved, only ??? are displayed.
I checked SQL tables and they are set with utf8_general_ci only.
Earlier, I could save and get displayed in the local laptop when working but got all files corrupted. Now when I try directly site, this does not work.
It would be helpful, if any directions are given on this to resolve this.
Need to display UNICODE based content in the story or page of drupal nodes.
Thanks in advance
Chandar
Comment #7
Anonymous (not verified) commentedIll look into this tomorrow
Comment #8
Anonymous (not verified) commentedMy expectation is that this bug should be resolved along with
http://drupal.org/node/328832 at least on the drupal 6 development branch.
Please let me know if this problem is not fixed and i will investigate further.
Best, Paul