search

nekohayo / specto

Automatically exported from code.google.com/p/specto
0 stars 0 forks source link

Using '&' in a watch's name results in it being displayed incorrectly #52

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Create a new web page watch, naming it Something & Something

What is the expected output? What do you see instead?
Expected 'Something & Something' to show up, instead it uses the name of a
nearby watch instead

What version of the product are you using? On what operating system?
0.2, Fedora Core 6

Please provide any additional information below.

Original issue reported on code.google.com by vfi...@gmail.com on 18 Mar 2007 at 4:48

GoogleCodeExporter commented 9 years ago 
Yeah, ampersands are the big annoying characters (like in html). You don't even 
have
to actually create the watch to reproduce the bug, you can simply type "joy &
happiness" in the watch name and it will fail setting the label7 properly, 
outputting
errors. I wonder how to fix that, any ideas folks?

add_watch.py:83: GtkWarning: Failed to set text from markup due to error parsing
markup: Error on line 1: Unfinished entity reference
  self.wTree.get_widget("label7").set_label(new_name)

add_watch.py:83: GtkWarning: Failed to set text from markup due to error parsing
markup: Error on line 1: Character ' ' is not valid at the start of an entity 
name;
the & character begins an entity; if this ampersand isn't supposed to be an 
entity,
escape it as &
  self.wTree.get_widget("label7").set_label(new_name)

Original comment by nekoh...@gmail.com on 18 Mar 2007 at 2:46

GoogleCodeExporter commented 9 years ago 
Before I reported issue #52, I was a good little monkey and did a search to 
make sure
there wasn't already an open issue for it and ran across this one.

Since I (think I) managed to figure out how to solve that one, I figured this 
one
couldn't be too much different.  Sure enough, it wasn't.  Have a look at the 
attached
patch.

Original comment by bkei...@gmail.com on 9 May 2007 at 1:08

Attachments:

GoogleCodeExporter commented 9 years ago 
Sorry, the issue referenced in the previous comment should be issue #56.

Original comment by bkei...@gmail.com on 9 May 2007 at 1:10

GoogleCodeExporter commented 9 years ago 
I modified slightly your patch and it now works for me. I'll commit that in SVN 
114.

Original comment by nekoh...@gmail.com on 1 Jul 2007 at 12:12

GoogleCodeExporter commented 9 years ago

Original comment by nekoh...@gmail.com on 18 Mar 2008 at 2:10