Re: [xml] Problem with xmlDocDumpMemory altering values

[Daniel Veillard <veillard redhat com>]

On Tue, Oct 19, 2004 at 05:34:51PM +0200, Erik F. Andersen wrote:
> Hi!
>
> I have a problem with xmlDocDumpMemory. My problem is that LibXML
> apparently inserts the character #10 after each line (node). This is a

  No it does not do that normally.

> problem in particular with one node that contains a x509v3 certificate
> as the node-value because this node is also signed using XMLSec. In this
> one line xmlDocDumpMemory even inserts an extra 
 before the #10 for
> every few hundred characters. This I suspect is making the signature

  I can't think of any code in the library doing this

> invalid when I try to authenticate it later on. How can I ensure that
> LibXML will not alter the node-values?

   http://xmlsoft.org/bugs.html

No reproductable test case, no platform indication, no version indication
  => report ignored, also wondering what you think our time is worth :-(

> I have tried calling xmlKeepBlanksDefault(0) without success.

  Definitely a very very wrong idea.

Daniel

-- 
Daniel Veillard      | Red Hat Desktop team http://redhat.com/
veillard redhat com  | libxml GNOME XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/