birdie-team team mailing list archive

[Contribucious <contribucious@xxxxxxxxx>]

Strange, no problem here with the tweet you show in example.
See http://i.imgur.com/QwlZaP1.png (here by a RT by someone as the original tweet is too old to be found in Birdie now, either via profile or via a search visibly [limited about getting old tweets in the 0.2.x version at least], but no impact about the parsing logically).

Are you sure you use the version from the DAILY repository?
If yes, what is the revision you use?
If you've a Debian-based distro like Ubuntu, just type in a terminal this command:
dpkg -l | grep birdie

In my case it shows: 0.2+r268-0+pkg11~precise1 (so, revision 268).
For info, it's since the revision 246 that all problems like that must be gone, logically.
See http://bazaar.launchpad.net/~birdie-team/birdie/trunk/revision/246
=> "included Purple library for much better html entities decoding and markup escaping"

-- 
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/1194420

Title:
  HTML character encoding bug returned to life

Status in Birdie:
  New

Bug description:
  Again, characters like '<', '>' and '&' looks like '&lt;', '&gt;' and
  '&amp;'. See example in picture below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/birdie/+bug/1194420/+subscriptions