Thank you -- I have submitted a new "ugreport (#32650) hope this will
be fixed anytime... ;)
On 10.12.2004, at 18:33, Joerg Heinicke wrote:
On 10.12.2004 15:13, Thomas Alexnat wrote:
I also think, that this behaviour is a bug. To me it renders the
usage of the cocoon view concept absol
ig bug.
Where can I add this bug? Or to whom can I talk?
Thanks in advance,
Thomas
On 10.12.2004, at 14:09, Vadim Gritsenko wrote:
Sylvain Wallez wrote:
Thomas Alexnat wrote:
are resulting in a corrupt XML tree after calling them with the
default pretty-print view. As expected,
Joerg,
thank you for your response. It seems that my problem seems not to be
solved with the current version of cocoon. Is this correct? I am
wondering if this is a bug or a feature. As a cocoon user I would say
this is a MAJOR bug in the view concept or implementation. Should I add
this bug to
comments wanted,
Thomas
PS: OS X and G5 rock!
On 07.12.2004, at 21:37, Sylvain Wallez wrote:
Thomas Alexnat wrote:
Dear Developers,
I was asking in the cocoon user mailing list why my content is not
being transformed correctly, when using the cocoon default
pretty-print view. The answers so far
Dear Developers,
I was asking in the cocoon user mailing list why my content is not
being transformed correctly, when using the cocoon default pretty-print
view. The answers so far pointed me to the developer list, because
there seems to be a misbehaviour or misunderstanding in using the
cocoon
