Hi folks,
I got no reply to this email, hopefully you can fill me in on some details.
Will setNewLine() work without the following method call to the serializer?
setFeature(XMLUni::fgDOMWRTFormatPrettyPrint, true);
TIA!
==
Oliver White
Software Engineer
Product
lizer->writeNode(&out, *parser.getDocument());
// cleanup
}
What comes out is a file with each existing 0x0D0A converted into an 0x0A!
How can we stop this happening?
==========
Oliver White
Software Engineer
Product Development
We
Hi folks,
not sure if I'm barking up the wrong tree here, but is there an API to
extract nodes from a file (or DOM) using XPath strings? This would be a
really powerful feature for manipulating trees.
==
Oliver White
Software Engineer
Product Development
Westing
nt to think about maintaining older versions
with bug fix releases.
==
Oliver White
Software Engineer
Product Development
Westinghouse Signals Aust
Should have mentioned... I'm using version 2.1.0.
==
Oliver White
Software Engineer
Product Development
Westinghouse Signals Australia
==
-
To unsubscribe, e-mail: [
Error handling code goes here.
}
======
Oliver White
Software Engineer
Product Development
Westinghouse Signals Australia
==
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Great, thanks for your help. :-)
--
Oli White
David N
Ok... strange one...
Is there any constraints regarding linking the debug Xalan libraries to the
release Xerces libraries? I changed xerces to use the debug library,
matching xalan, and all was well.
Cheers,
Oli White
Actually, I get the same problem when I rebuild Xalanexe.cpp, which has
those parentheses.
--
Oli White
Alberto
Memory access violation.
Gareth Reakes
I should have mentioned... I'm running under NT 4.0.
--
Oli White
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi folks. I've got a strange error that keeps cropping up, using Xalan. The
code below crashes on the transform line, and the error seems to be deep in
the bowels of Xerces, according to the stack trace. I'm using xalan 1.4.0
with xerces 2.1.0.
If you have any ideas as to what might be causing the
Hi folks,
apologies for spamming the list with userland questions...
I'm developing an editor for XML data, and I'd like to be able to present
the user with useful information about where errors occured, so they can go
back and change the data as appropriate.
The error messages received by the h
13 matches
Mail list logo