-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/Internati
--On Dienstag, 11. November 2003 14:13 Uhr +1100 Stuart Bishop
<[EMAIL PROTECTED]> wrote:
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 ac
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
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 enco
--On Dienstag, 11. November 2003 14:41 Uhr + Toby Dickenson
<[EMAIL PROTECTED]> wrote:
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-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/11/2003, at 1:41 AM, Toby Dickenson wrote:
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.
Your right - this is the killer :-(
I had naively assumed seta
