You can clone with
HTTPS or Subversion.
Using twittering-mode 2.0.0 on GNU Emacs 23.1.1 (x86_64-redhat-linux-gnu, GTK+ Version 2.18.9) on CentOS 6.2. Screenshot here: http://pic.twitter.com/lWx44fN
I cannot see the picture because it is private.
Do you mean & is converted into &?
It is not due to twittering-mode, which only renders a received tweet as is.
From a certain time, the server seems to convert & into & when storing a tweet.
You can confirm that the character in the tweet at 2012-03-06 21:01:18 UTC is not converted.
This problem had been fixed at 2012-03-28, but it appeared again at May
and has been reported as an issue https://dev.twitter.com/issues/339 .
If the conversion is a firm rule, I will fix twittering-mode but such a rule is not stipulated.
I will wait for actions by Twitter because the issue has been marked as acknowledged.
Go ahead and request to follow so you can see my tweets. I dunno if it's a conversion issue; BitlBee seems to handle it OK.
I saw your image.
I think it is caused by the mixture of XML encoding and the unexpected conversion
In XML documents, the character & should be escaped as & because
the strings following & denote special characters. For example, < and >
mean < and >, respectively.
Differently from the ordinary escape method, the Twitter server escapes such
characters doubly as I had mentioned in the docstring of the function
(You can see it by M-x describe-function and specifying the function on Emacs.)
The redundant escape method may interfere the unexpected conversion of &.
The latest version of the master branch on github retrieves JSON instead of XML if
possible. How about using it?
You will see the tweet as This is a test tweet with an ampersand: &.
This is a test tweet with an ampersand: &