GNOME Bugzilla – Bug 608243
Bug in playlist sync functionality
Last modified: 2012-12-16 16:28:00 UTC
Created attachment 152393 [details] screenshot of extra question marks Someone (Gabriel or Alex?) has done some great work creating a "sync from playlist" functionality. Enhancement request link: https://bugzilla.gnome.org/show_bug.cgi?id=408204 At the bottom of that thread you can see a screenshot, repeated here, showing that on my system the smart quotation marks that are supposed to surround the playlist name come out as triple question marks. I'm running Karmic Ubuntu, banshee version 1.6 beta 4 from the daily ppa.
Created attachment 152548 [details] [review] Use Unicode codes for quotation marks Could you test with this patch? If it doesn't help, what is your locale and default application font?
I'm not a developer, I only installed this via a ppa. To apply the patch I think I need to check out the software and then apply the patch and build. I can get the source and build OK I think, but I'll need some help with how to apply the patch please. I'm in Hong Kong, but believe I have UK English. MY default font is Sans, the default for Ubuntu.
*** Bug 608691 has been marked as a duplicate of this bug. ***
I have downloaded and compiled the latest source tarball from banshee-project.org, and it seems to be fixed now. I didn't use the patch.
Alexander, feel free to commit your patch. I wonder if this issue is caused by during the packaging/build process on Ubuntu or wherever it not treating the source code files as utf-8. Better safe than sorry.
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.
*** Bug 608919 has been marked as a duplicate of this bug. ***
(In reply to comment #6) > This problem has been fixed in the development version. The fix will be > available in the next major software release. Thank you for your bug report. Looks like the major release (version 2.0) is out. After installing Ubuntu Natty 11.04, it's still there.
Well, can't change the status of this bug, so I hope I'm not sending my comments to nowhere. :)
(In reply to comment #9) > Well, can't change the status of this bug, so I hope I'm not sending my > comments to nowhere. :) Hi Craig, sorry for the late reply. I think you were not seeing this bug fixed because the change committed only fixed one of the two occurrences of the string. We're now tracking this in bug 639947, where I just posted a patch.