On Tuesday 11 November 2003 14:23, Tres Seaver wrote: > On Mon, 2003-11-10 at 22:13, Stuart Bishop wrote: > > Hi. I think the last thread on this issue was: > > http://aspn.activestate.com/ASPN/Mail/Message/zope-Dev/1843637 > > > > From my reading of RFC2396 and RFC2277, the character set encoding for > > URLs is UTF8. This is confirmed by > > http://www.w3.org/International/O-URL-code.html . > > > > Does this settle the issue on how to handle non-ascii strings in URLs?
if only browser always worked that way :-( > > If so, is their anything stopping us allowing Unicode ids in Zope? This > > would involve patching OFS.ObjectManager.checkValidId to accept strings > > not in [0-9a-zA-Z\$\-_\.\+!\*'(),], and writing replacement > > urllib.quote and urllib.unquote methods for use by HTTPRequest.py. +1 on starting a prototype now, but I cant see this landing before 2.8. This is going to break every use equivalent to getattr(some_object, id). Its not obvious to me how this can be cleanly resolved in zope 2. -- Toby Dickenson _______________________________________________ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )