---------
There seems to be a zope bug with XML parsing where if you make a bad
call (I saw it trying to use DateTime() object) then it reports an
XML problem with and or something like that on line 13,
though there was no line 13. Maybe a bug that's been fixed in a later
version.
--- Bill Andrews wrote:
> From: Bill Andrews
> To: zope-xml@zope.org
> Subject: [Zope-xml] TAL namespace errors generating XML in Zope
> with TAL statements
> Date: Thu, 12 Jun 2003 15:20:36 -0700 (PDT)
>
> Hi there,
>
> I'm trying to generate simple XML from a Zope DTML Document.
> Getting
> this error:
>
> Reference to undeclared namespace prefix: 'tal'. Error processing
> resource 'http://localhost/test2.xml'. Line 4, Position 37
>
>
>
> I have this in the DTML doc:
>
> ------------
>
>
>
>
>
>
>
> ------------
>
> What do I need to do differently to get this to work? Already using
> TAL within DTML docs in Zope to generate HTML.
>
> Need to get this working for my job - appreciate any leads/tips.
>
> Zope 2.6.0 (source release, python 2.1, linux2), python 2.1.3,
> freebsd4)
>
> Thanks,
> Bill
>
>
__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
From lists at elvix.com Fri Jun 13 03:09:18 2003
From: lists at elvix.com (=?ISO-8859-15?B?R2VpciBC5mtob2x0?=)
Date: Sun Aug 10 16:54:53 2008
Subject: [Zope-xml] TAL namespace errors generating XML in Zope with TAL statements
In-Reply-To: <20030612235924.80285.qmail@web11105.mail.yahoo.com>
References: <20030612235924.80285.qmail@web11105.mail.yahoo.com>
Message-ID: <52126306499.20030613090918@elvix.com>
On Thu, 12 Jun 2003 16:59:24 -0700 (PDT) GMT (..1:59 where i live(GMT+2) )
Bill Andrews asked the Zope-XML mailinglist about the following:
>
> There seems to be a zope bug with XML parsing where if you make a bad
> call (I saw it trying to use DateTime() object) then it reports an
> XML problem with and or something like that on line 13,
> though there was no line 13. Maybe a bug that's been fixed in a later
> version.
actually, that is just internet explorer trying to parse the
error-message as xml, while it is actually quite badly-formed HTML.
In most cases, an HTML errormessage is just fine, but IE, expecting
XML returns a local (on the client) parsing error..
Someone should probably come up with a neat solution to that problem..
:)
--
Geir B?kholt