birdie-team team mailing list archive
-
birdie-team team
-
Mailing list archive
-
Message #00555
[Bug 1185031] Re: Tweet parsing problem
I would say that you better to use a quality parsing library to do that stuff, rather than manually .replace...
Because it's the better method to forget many entities in the parsing list. :^)
By the way, two new tweets with problem detected (even with the last revision r244, which includes the fix so):
1/ http://i.imgur.com/OBjSixI.png -> https://twitter.com/iVerger/status/339683424216428544 (seems to be the " at the end, which becomes part of the URL)
2/ http://i.imgur.com/xnBVznt.png -> https://twitter.com/MagaliPernin/status/339690878882959360 (same remark)
--
You received this bug notification because you are a member of Birdie
Developers, which is subscribed to Birdie.
Matching subscriptions: Birdie
https://bugs.launchpad.net/bugs/1185031
Title:
Tweet parsing problem
Status in Birdie:
Fix Committed
Bug description:
Tweet parsing problem:
=> See this screenshot: http://i.imgur.com/NfF8d4y.png
=> Tweet concerned: https://twitter.com/MKERone/status/339364094786285568
N.B.: Also note that, visibly, when 1 tweet only is returned in search
results, it appears at the bottom of the window, rather than at the
top. I'll report that in a separate bug report.
OS: Ubuntu 12.04.2 LTS (with XFCE)
Birdie version used: the last one available in the DAILY repository (did an "apt-get install birdie" to update it few minutes ago).
*EDIT*
In fact, I suppose it's the "greater than" character (>), the problem, in this case.
From the text of the tweet. Not the & from the URL.
Need to parse all special characters so.
*EDIT 2*
Problem already resolved in the next revision visibly, cf. my comment below.
--
Related log lines (I think):
--
[_LOG_LEVEL_WARN 15:40:37.564540] [Gtk] Failed to set text from markup due to error parsing markup: Error on line 1: Entity did not end with a semicolon; most likely you used an ampersand character without intending to start an entity - escape ampersand as &
To manage notifications about this bug go to:
https://bugs.launchpad.net/birdie/+bug/1185031/+subscriptions
References