You can't really rely on a perlish 'do-what-I-mean' behaviour as it gets worse - domain names (as part of the URI) can also contain unicode in a *different* encoding, punycode. For example http://xn--tdali-d8a8w.lv/ that includes the Unicode representation of the Latvian "u with a macron", and "n with cedilla", instead of the unmarked base characters: http://tūdaliņ.lv - if you paste this 'funny char' version into firefox, it will actually convert it to punycode and load the page, although it does not display the unicode chars.
On Nov 27, 1:36 pm, "Daniel Contag" <[EMAIL PROTECTED]> wrote: > My opinion is that we should adhere to the RFCs. > > Daniel > > On Thu, Nov 27, 2008 at 13:12, Jonathan Benn <[EMAIL PROTECTED]> wrote: > > > Hi Massimo, > > > On Nov 27, 6:13 am, mdipierro <[EMAIL PROTECTED]> wrote: > > >> Does anybody have any objection to this patch? > > > I object, on the grounds that the URL standard does *not* support > > unicode. As Achipa points out, a unicode URL needs to be escaped in > > order to pass validation. > > > If we want to support unicode URLs, rather than breaking web2py's > > standards-compliance, I suggest either extending IS_URL with a new > > "mode" that automatically escapes unicode, or creating a utility > > function that escapes unicode URLs (but leaves non-Unicode URLs > > intact). > > > What does everyone else think? > > > I hope that helps, > > > --Jonathan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
