> I'd agree if this were a violation of am specification, but it's not.
> CUT
I agree, but it is violation of ordinary common sense.
>
>... If not, and if it would be committed, I'd be
> happy to make a patch that gets rid of them.
>
It will be nice. This save my time and allow me focus to anot
Am Dienstag, 29. März 2005 15:30 schrieb Jesse Pelton:
> I'd agree if this were a violation of am specification, but it's not.
> If you have read the thread I referred to, you know that
> pretty-printing is only loosely specified. This means, in essence,
> that implementations can do whatever they
in their
pretty-printed output? If not, and if it would be committed, I'd be happy to
make a patch that gets rid of them.
From: Lumir Vanek [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 29, 2005 1:06 AMTo:
xerces-c-dev@xml.apache.orgSubject: Re: fgDOMWRTFormatPrettyPrint
c
ED]]
Sent: Sunday, March 27, 2005 3:04 PM
To: xerces-c-dev@xml.apache.org
Subject: fgDOMWRTFormatPrettyPrint causes double 0A in output
Hi,
when I use DOMWriter::setFeature(
XMLUni::fgDOMWRTFormatPrettyPrint, true );
after each element, there is 0A 0A (2 x line feed), instead
of 0A what I
expe
rces-c-dev@xml.apache.org
> Subject: fgDOMWRTFormatPrettyPrint causes double 0A in output
>
> Hi,
>
> when I use DOMWriter::setFeature(
> XMLUni::fgDOMWRTFormatPrettyPrint, true );
> after each element, there is 0A 0A (2 x line feed), instead
> of 0A what I
> expect. This
Hi,
when I use DOMWriter::setFeature( XMLUni::fgDOMWRTFormatPrettyPrint, true );
after each element, there is 0A 0A (2 x line feed), instead of 0A what I
expect. This is bug or feature ? I use Xerces-C 2.6.
Regards,
Lumir Vanek,
KXML Editor developer
http://www.valachnet.cz/lvanek
