[Zope-dev] Re: Non-ASCII characters in URLs
Tres Seaver wrote at 2008-4-12 21:43 -0400: ... Dieter Maurer wrote: Wichert Akkerman wrote at 2008-4-7 20:45 +0200: ... Almost surely, Alexander wants to ask why Zope does not allow non-ASCII characters in ids. And, in fact, there are only two reasons: * lazyness of the Zope developpers: without the restriction to ASCII characters careful quoting (and unquoting) is necessary in order to adhere to RFC 2396 (the modern uri syntax specification) This is becoming increasingly painful I will soon have a patch against Zope 2.11b1 which gets rid of this restriction. If there is consense, I can add it to the Zope repository. +1 from my side. Saves me the work to cleanup my own dirty patch :-)) - -1 without *careful* analysis of how the patch is going to break existing applications which rely on the fact that IDs are only ASCII (and therefore don't need to be quoted). At a minimum, this kind of change is going to require documenting the risks, and getting soem feedback, before any merge to a production release. Please check the patch in on a private branch and ask for comments here. Implemented on http://svn.zope.org/Zope/branches/dm-arbitrary-ids/;. -- Dieter ___ Zope-Dev maillist - Zope-Dev@zope.org 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 )
Re: [Zope-dev] Re: Non-ASCII characters in URLs
--On 12. April 2008 21:43:40 -0400 Tres Seaver [EMAIL PROTECTED] wrote: This is becoming increasingly painful I will soon have a patch against Zope 2.11b1 which gets rid of this restriction. If there is consense, I can add it to the Zope repository. +1 from my side. Saves me the work to cleanup my own dirty patch :-)) - -1 without *careful* analysis of how the patch is going to break existing applications which rely on the fact that IDs are only ASCII (and therefore don't need to be quoted). At a minimum, this kind of change is going to require documenting the risks, and getting soem feedback, before any merge to a production release. Please check the patch in on a private branch and ask for comments here. @Dieter: please create a branch for this (and not as patch for Launchpad) The patch is working for long time (possibly several years) within our private Zope. So I would not expect much problems. Of course it needs testing and documentation. Andreas pgp33OXmU7CcU.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org 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 )
[Zope-dev] Re: Non-ASCII characters in URLs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tino Wildenhain wrote: Dieter Maurer wrote: Wichert Akkerman wrote at 2008-4-7 20:45 +0200: ... Almost surely, Alexander wants to ask why Zope does not allow non-ASCII characters in ids. And, in fact, there are only two reasons: * lazyness of the Zope developpers: without the restriction to ASCII characters careful quoting (and unquoting) is necessary in order to adhere to RFC 2396 (the modern uri syntax specification) This is becoming increasingly painful I will soon have a patch against Zope 2.11b1 which gets rid of this restriction. If there is consense, I can add it to the Zope repository. +1 from my side. Saves me the work to cleanup my own dirty patch :-)) - -1 without *careful* analysis of how the patch is going to break existing applications which rely on the fact that IDs are only ASCII (and therefore don't need to be quoted). At a minimum, this kind of change is going to require documenting the risks, and getting soem feedback, before any merge to a production release. Please check the patch in on a private branch and ask for comments here. Tres. - -- === Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIAWVM+gerLs4ltQ4RAhsAAKDCLcUAb+ZzzYBJZ2OdoZeDKQ49MwCbBpNH r7gkEMLDz/mzfyCoyMoHgZc= =/p2I -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org 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 )
[Zope-dev] Re: Non-ASCII characters in URLs
On Mon, 07 Apr 2008 05:32:17 -0700, Jonathan [EMAIL PROTECTED] wrote: IDNA (http://www.ietf.org/rfc/rfc3490.txt) and Punycode (http://www.faqs.org/rfcs/rfc3492.html) may be of some use. I'm not looking for non-ASCII domain names, just object IDs. :) -- Alexander Limi · http://limi.net ___ Zope-Dev maillist - Zope-Dev@zope.org 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 )
[Zope-dev] Re: Non-ASCII characters in URLs
On Mon, 07 Apr 2008 12:45:00 -0700, Dieter Maurer [EMAIL PROTECTED] wrote: Wichert Akkerman wrote at 2008-4-7 20:45 +0200: This is becoming increasingly painful I will soon have a patch against Zope 2.11b1 which gets rid of this restriction. If there is consense, I can add it to the Zope repository. I would love to see support for non-ASCII object IDs, +1. (obviously not based on any technical understanding from my side :) -- Alexander Limi · http://limi.net ___ Zope-Dev maillist - Zope-Dev@zope.org 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 )
