-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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. It would also be worth fixing Python's urllib.quote and urllib.unquote methods, but that is an issue for a seperate mailing list... - -- Stuart Bishop <stuart@stuartbishop.net> ☞ http://www.stuartbishop.net/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (Darwin) iD8DBQE/sFP1AfqZj7rGN0oRAhGGAJ9dGMyhxFhG6GFr877qNx5+GP/S3wCghcOy T6lXZz60sR1VJLWjK76BmVk= =rQ0I -----END PGP SIGNATURE-----