I think it is the way that .Net handles encoding of the diacritics. I don't think it's a Twitter api issue. I was hoping that another .Net developer had run into this issue and had fixed it.
Ryan On Tue, Feb 23, 2010 at 2:07 PM, Raffi Krikorian <ra...@twitter.com> wrote: > this would be news to me - if you have a way to replicate this, and you are > confident its not your oauth libraries, then please let me know. > > > On Tue, Feb 23, 2010 at 11:04 AM, Ryan Alford <ryanalford...@gmail.com>wrote: > >> I believe it has been fixed in some libraries in other programming >> languages, but I can't figure out how to do it in .Net. >> >> Ryan >> >> >> On Tue, Feb 23, 2010 at 12:38 PM, Aral Balkan <aralbal...@gmail.com>wrote: >> >>> Ooh, if this is the case then it will definitely stop me from using oAuth >>> for Feathers (http://feathersapp.com) since diacritics are an essential >>> part of Unicode art. >>> >>> Very interested in hearing what you find out. >>> >>> All the best, >>> Aral >>> >>> >>> On Tue, Feb 23, 2010 at 1:44 PM, eclipsed4utoo >>> <ryanalford...@gmail.com>wrote: >>> >>>> I am getting an error message when posting accent marks and other >>>> diacritics in a status update. >>>> >>>> I saw that there was an issue [1] posted in April of last year about >>>> this problem. It seems to be with the signature generation for OAuth >>>> with the encoding of accent marks. >>>> >>>> I am using .Net(C#), and I can't figure out how to fix this. Do I use >>>> a different encoding? Anybody have any ideas on how to fix this >>>> in .Net? >>>> >>>> [1] - http://code.google.com/p/twitter-api/issues/detail?id=433 >>>> >>>> Ryan >>>> >>> >>> >> > > > -- > Raffi Krikorian > Twitter Platform Team > http://twitter.com/raffi >
