[Zope-dev] Re: Non-ASCII characters in URLs

[Tres Seaver]

-----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          tseaver at palladion.com
Palladion Software   "Excellence by Design"    http://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-----