This change breaks Gadfly which doesn't seem to like 'null' at all. I
poked around in ZGadflyDA/gadfly a bit, but it's not obvious to me
how to fix the parser (*.mar files anyone?).
Stefan
[snip]
File "/usr/local/Zope-2_8-branch/lib/python/Products/ZGadflyDA/
gadfly/kjParser.py", line 82
--On 8. Oktober 2005 15:41:57 +0200 "Stefan H. Holek" <[EMAIL PROTECTED]>
wrote:
This change breaks Gadfly which doesn't seem to like 'null' at all. I
poked around in ZGadflyDA/gadfly a bit, but it's not obvious to me how
to fix the parser (*.mar files anyone?).
No idea about the specif
--On 8. Oktober 2005 16:04:46 +0200 Andreas Jung <[EMAIL PROTECTED]>
wrote:
--On 8. Oktober 2005 15:41:57 +0200 "Stefan H. Holek" <[EMAIL PROTECTED]>
wrote:
This change breaks Gadfly which doesn't seem to like 'null' at all. I
poked around in ZGadflyDA/gadfly a bit, but it's not obvious
Hi All,
During complication, the XML parser that processes non-HTML mode ZPT's
decodes the string of the source into unicode instructions.
In HTML mode, the parse does no decoding and so we get string instructions.
My question as a result is: what characterset does the XML parser in
non-HTML
Hi All,
I'd like to backport the change I made to fix:
http://www.zope.org/Collectors/Zope/1490
...to the 2.8 branch, would anyone have any objections to this?
cheers,
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
___
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Withers wrote:
> During complication, the XML parser that processes non-HTML mode ZPT's
^
+- "compilation", I'm guessing, but see below ;)
> decodes the string of the source into unicode instructions.
>
> In HTML mode, the pa
--On 8. Oktober 2005 19:15:57 +0100 Chris Withers <[EMAIL PROTECTED]>
wrote:
Hi All,
I'd like to backport the change I made to fix:
http://www.zope.org/Collectors/Zope/1490
...to the 2.8 branch, would anyone have any objections to this?
The 2.8 branch is closed for new features. With th
Andreas Jung wrote:
I'd like to backport the change I made to fix:
http://www.zope.org/Collectors/Zope/1490
...to the 2.8 branch, would anyone have any objections to this?
The 2.8 branch is closed for new features. With the time-based schedule
new features should appear regularly with new ma
Andreas Jung wrote:
The 2.8 branch is closed for new features. With the time-based schedule
new features should appear regularly with new major releases. So only
bug fixes should go into minor releases.
In fact, just noticing other mails, I'd also like to merge this to the
2.7 branch, I just
Am Samstag, den 08.10.2005, 19:15 +0100 schrieb Chris Withers:
> Hi All,
>
> I'd like to backport the change I made to fix:
> http://www.zope.org/Collectors/Zope/1490
>
> ...to the 2.8 branch, would anyone have any objections to this?
Surely not, but what fix? :-)
Nice to see some movement on
--On 8. Oktober 2005 20:10:21 +0100 Chris Withers <[EMAIL PROTECTED]>
wrote:
Andreas Jung wrote:
I'd like to backport the change I made to fix:
http://www.zope.org/Collectors/Zope/1490
...to the 2.8 branch, would anyone have any objections to this?
The 2.8 branch is closed for new feat
Andreas Jung wrote:
Well, this is arguably a bug fix and I incorrectly filed it as a new
feature on the trunk.
If you can justify it as a bugfix before god and the world,go ahead :-)
Cool, will do so to the 2.7 and 2.8 branches tomorrow :-)
cheers,
Chris
PS: I'll mark it as a bug fix in th
12 matches
Mail list logo
