Posted on Feb 23, 2009 by
Helpful Rhino
What steps will reproduce the problem? 1. Receive or send a tweet with " foo # bar " 2. 3.
What is the expected output? What do you see instead? Expected: " foo # bar " Actual: " foo bar "
What version of the product are you using? On what operating system? 2.1.2 clickonce on vista x64
Please provide any additional information below.
- 2009-02-23_1256.png 41.31KB
Comment #1
Posted on Oct 11, 2009 by Quick RabbitI fixed this in the patch that I submitted for issue 264.
-Mike
Status: New