Storing and validating URI's should be pretty straightforward with the RFC's, the trouble comes when you have to decide how do you the URI to *appear* to the user/developer. Obviously looking at a bunch of %XY-s or xn--es is not a pretty sight, and in case the language uses a non- latin alphabet, it becomes completely unreadable. The real question is therefore that of presentation and ease of use, and the RFC can't help much there as that's not it's subject.
On Nov 29, 3:51 pm, Jonathan Benn <[EMAIL PROTECTED]> wrote: > Here's a quote from section 1.5 of RFC 2396: > > "The URI syntax was designed with global transcribability as one of > its main concerns. A URI is a sequence of characters from a very > limited set, i.e. the letters of the basic Latin alphabet, digits, and > a few special characters." > > Here are the relevant RFCs: > > http://www.faqs.org/rfcs/rfc2396.htmlhttp://www.faqs.org/rfcs/rfc2616.html > > 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 -~----------~----~----~----~------~----~------~--~---