the former is assuming UTF-8, which is likely the correct assumption to make. %E9 is the actual unicode codepoint, whereas the %C3%A9 is the UTF-8 encoding of said codepoint. I believe the API wiki says something about requiring UTF-8 encoding (and if it doesn't, it should).
On Fri, Jul 31, 2009 at 13:14, Ney Garcia <neygar...@gmail.com> wrote: > > Thanks for the tip, Marcel. > I am trying to build my signed requests using that page, but I found > this weird thing: > > The hueniverse page converts "véio" (in Brazil most words have such > marks) to > "v%C3%A9io" > > but my C# lib UrlEncode method outputs > "v%E9io" > > So does this URL encode example page > http://www.albionresearch.com/misc/urlencode.php > > Any help ? > > Thanks. > > On 30 jul, 18:58, Marcel Molina <mar...@twitter.com> wrote: > > For those who might be struggling to ensure their OAuth signatures are > being > > generated correctly, this > > guide provides more hand holding with the process than the specification. > > It includes custom forms where you can fill out all the details of > > your request and see what the signature and > > its related data *should* be. > > > > http://www.hueniverse.com/hueniverse/2008/10/beginners-gui-1.html > > > > -- > > Marcel Molina > > Twitter Platform Teamhttp://twitter.com/noradio > -- Internets. Serious business.
