← Back to team overview

birdie-team team mailing list archive

[Bug 1185031] Re: URL parsing problem

 

Ahah, I saw recently this commit by browsing the new stuff done:
http://bazaar.launchpad.net/~birdie-team/birdie/trunk/revision/238?start_revid=239

And thought I had already this revision as updated very recently (few minutes before I saw this bug and report it).
So I thought it still had a parsing problem (even with this commit done so) but no!

I checked and... I have the r237(!):
=> "Preparing to replace birdie 0.2+r231-0+pkg7~precise1 (using .../birdie_0.2+r237-0+pkg7~precise1_amd64.deb) ..."

And the commit that seems to resolve that is the r238! :^)
So, visibly, the (auto-)build is not done yet for this revision. Just need to wait then. :-)

** Description changed:

  URL parsing problem:
    => See this screenshot: http://i.imgur.com/NfF8d4y.png
    => Tweet concerned: https://twitter.com/MKERone/status/339364094786285568
- 
- I suppose it's the "greater than" character (>), the problem, in this case.
- Need to parse all special characters so.
  
  N.B.: Also note that, visibly, when 1 tweet only is returned in search
  results, its shown 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 &

** Description changed:

- URL parsing problem:
+ 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, its shown 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 &

** Summary changed:

- URL parsing problem
+ Tweet parsing problem

-- 
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:
  New

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, its shown 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