character "&" bugs track editor

[gring0]

If some tag contains the "&" character, it bugs the value of the tag at the track editor. Instead, it shows correctly at the playlist.

[picpak (k-belding)]

I have this same problem. However, going to "Tags From Path" and adding the tags through there works perfectly.

[gring0 (ggring00)]

still not working rev 1557
actually, it edits the tag, but it shows wrong at the gui

terminal shows me that (portuguese)
/usr/local/lib/exaile/xl/gui/editor.py:296: GtkWarning: Failed to set text from markup due to error parsing markup: Erro na linha 1: Caractere ' ' não é válido no início do nome da entidade; o caractere & inicia uma entidade; se este 'e' comercial não é suposto ser uma entidade, mascare-o como &

that means something like that in english:
/usr/local/lib/exaile/xl/gui/editor.py:296: GtkWarning: Failed to set text from markup due to error parsing markup: Error on line 1: Character ' ' is not valid at the beggining of an entity; the character & starts an entity; if that comercial 'e' is suposed to be an entity, mask it as &

[Luis Díaz (piponazo)]

Yes, I have the same problem. When I edit a tag with a string that constains a & character, the value is showed incorrectly in the editor but in the tracklist is showed correctly.

[shiftless (shiftless)]

This is confirmed in the latest version. Could we please get a fix for this? The problem appears to be because Exaile is putting "markup" text in the in the taglist column, and the ampersand sign is being interpreted as HTML markup instead of being passed through. The fix is to grep through each string for &'s and replace them with "&".

At the same time, it'd be a great idea to also ensure that any markup code is stripped OUT of the id3 tag before being displayed, anyhow, so this would be a good time to take care of that as well.

Now, I'm not sure why the developers specifically chose to put markup instead of plain text into this box. Perhaps they use markup to accomplish highlighting, strikethrough, etc. If so then the following solution wont work. Otherwise an easy fix to both issues would be just to put the information in the box in as plain text.