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
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 encoding for
--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
Hi all:
I have downloaded Zope-2.6.2-linux2-x86 and I have created a page
template with xml content, but when I try to test it the next message
appears:
Error Type: ImportError
Error Value: cannot import name expat
Is this a bug?
El lun, 10-11-2003 a las 18:08, Sidnei da Silva escribió:
On
Thanks, now I am happy.
What is runzope for ?
should that not be eliminated ?
Robert
Am Dienstag, 11. November 2003 00:25 schrieb Chris McDonough:
runzope never detaches from the terminal... use zopectl start
instead. Unlike previous versions of Zope, 2.7 doesn't handle its own
daemonizing.
No, it lets you run nondaemonized. That's still useful.
On Tue, 2003-11-11 at 11:03, robert wrote:
Thanks, now I am happy.
What is runzope for ?
should that not be eliminated ?
Robert
Am Dienstag, 11. November 2003 00:25 schrieb Chris McDonough:
runzope never detaches from the
