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 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. > > If this is deemed a sane plan, I'd like to try getting this into Zope > 2.7.
-1 for 2.7, as each introduction of new Unicode features has historically been accompanied by a whole raft of new bugs, which are mostly not reproducible (or at least hide) on the system where the feature was developed. We are trying hard to get to stability for 2.7, with a beta planned for this week. +1 for 2.7.1 and 2.8. > It would also be worth fixing Python's urllib.quote and urllib.unquote > methods, but that is an issue for a seperate mailing list... ROIGHT! Tres. -- =============================================================== Tres Seaver [EMAIL PROTECTED] Zope Corporation "Zope Dealers" http://www.zope.com _______________________________________________ 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 )
