After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 619280 - do not escape display_name, it is already encoded in UTF-8
do not escape display_name, it is already encoded in UTF-8
Status: RESOLVED FIXED
Product: tracker
Classification: Core
Component: Miners
unspecified
Other All
: Normal normal
: ---
Assigned To: tracker-general
Jamie McCracken
Depends on:
Blocks:
 
 
Reported: 2010-05-21 11:55 UTC by Frederic Crozat
Modified: 2010-05-27 10:28 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
do not escape display_name, it is already encoded in UTF-8 (1.75 KB, patch)
2010-05-21 11:55 UTC, Frederic Crozat 		none Details | Review

Description Frederic Crozat 2010-05-21 11:55:17 UTC 
on a non-UTF8 locale system, when renaming a file with a ascii name to a filename with non-ascii characters, sparql queries was rejected (and file name changes wasn't reflected in Tracker. 

There is no point in escaping filename, since display_name always returns an UTF-8 filename.
Comment 1 Frederic Crozat 2010-05-21 11:55:19 UTC 
Created attachment 161634 [details] [review]
do not escape display_name, it is already encoded in UTF-8
Comment 2 Carlos Garnacho 2010-05-21 16:47:01 UTC 
This is now in master, thanks!
Comment 3 Martyn Russell 2010-05-27 10:28:34 UTC 
Hmm, just been speaking to Juergbi about this on IRC. We should still be escaping for SPARQL. It is entirely possible the display name has characters in it not agreeable to SPARQL. See bug #619801 for this.