gwibber-bugs team mailing list archive
-
gwibber-bugs team
-
Mailing list archive
-
Message #03140
[Bug 656496] Re: Twitter message text should not be unescaped
[Expired for Gwibber because there has been no activity for 60 days.]
** Changed in: gwibber
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Gwibber
Bug Heros, which is subscribed to Gwibber.
https://bugs.launchpad.net/bugs/656496
Title:
Twitter message text should not be unescaped
Status in Gwibber:
Expired
Bug description:
Currently in microblog/twitter.py in Client._common , the m['text']
field is constructed by unescaping the text field in the data. But
Twitter messages retrieved via JSON are not XML-escaped. This means
that messages containing ampersands are sometimes mangled. E.g., the
tweet "I like M&Ms" would be converted to "I like M". Note that this
only applies to the m['text'] field, so it is not visible in the main
UI (which uses m['content'], which isn't unescaped), but it is visible
in notifications.
To manage notifications about this bug go to:
https://bugs.launchpad.net/gwibber/+bug/656496/+subscriptions