Re: [xml] Differences in DOM parsing on Windows and UNIX?

On Fri, Oct 03, 2003 at 11:58:08AM -0400, Ed Day wrote:
Extra text nodes are inserted for whitespace.  Is this a configuration issue?  If not, which version is 

I used the standard out-of-the-box build procedure in both cases and built from source code instead of 
using the pre-compiled binaries.  Has anyone else observed this behavior?  It would be good to know before 
I start digging into the code. 

  Hum, sounds like xmlKeepBlanksDefaultValue is wrongly initialized to 0
on your Windows build while it should be 1 as properly compiled on Unix.
 * xmlKeepBlanksDefaultValue:
 * Global setting, indicate that the parser should keep all blanks
 * nodes found in the content
 * Activated by default, this is actually needed to have the parser
 * conformant to the XML Recommendation, however the option is kept
 * for some applications since this was libxml1 default behaviour.
int xmlKeepBlanksDefaultValue = 1;

see if your compiler miscompiled globals.c on Windows.


Daniel Veillard      | Red Hat Network
veillard redhat com  | libxml GNOME XML XSLT toolkit | Rpmfind RPM search engine

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]