google-code-export / microblog-purple

Automatically exported from code.google.com/p/microblog-purple
GNU General Public License v3.0
2 stars 0 forks source link

Hashtags puncuation is not respected in mbpurple-0.3.0 #268

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Posts with hashtags with punctuation in them are not interpreted. I 
identi.ca-d/tweeted a notice with the text “ #seamonkey’s” in it ( 
http://identi.ca/notice/99686690 , 
https://twitter.com/ohnobinki/status/303906456422465536 ). At the respective 
microblog websites, the hashtag was interpreted as “#seamonkey”. But in my 
mbpurple’s echoing back of my own tweet (I have only connected it to my 
twitter account), I get the following HTML as best as I can preserve it:

<font color="#cc0000"><a
href="http://twitter.com/ohnobinki/status/303906456422465536">(11:38:40)</a></fo
nt>
<b><i><font color="darkred"><a
href="tw:///reply?src=twitter.com&amp;to=ohnobinki&amp;account=ohnobinki@api.twi
tter.com&amp;id=303906456422465536">ohnobinki</a>:</font></i></b>
Ugh! When will &lt;textarea/&gt;s get #<a
href="http://search.twitter.com/search?q=%23readline">readline</a>
or #<a href="http://search.twitter.com/search?q=%23emacs">emacs</a>
key-binding support? That’s one too many times I’ve opened #<a
href="http://search.twitter.com/search?q=%23seamonkey%3Fs">seamonkey’s</a>
page editor… <a
href="tw:///fav?src=twitter.com&amp;account=ohnobinki@api.twitter.com&amp;id=303
906456422465536">*</a>
<a
href="tw:///rt?src=twitter.com&amp;account=ohnobinki@api.twitter.com&amp;id=3039
06456422465536">rt</a>

In there is a link to http://search.twitter.com/search?q=%23seamonkey%3Fs which 
should be a link to http://search.twitter.com/search?q=%23seamonkey

The rules for stopping on punctuation are talked about a little at 
https://support.twitter.com/articles/370610-my-hashtags-or-replies-aren-t-workin
g and http://qr.ae/TRvm6 . In my short search, I couldn’t find a method of 
determining which characters count as tag delimiters or not, unfortunately.

Original issue reported on code.google.com by ohnobinki on 19 Feb 2013 at 4:48