On Sun, Nov 06, 2005 at 07:33:19PM -0500, Rob Richards wrote:
Geert Jansen wrote:
See the attached patch. I took your original suggestion and used the
original prototype for xmlSaveToBuffer(). I now create an
xmlOutputBuffer from the xmlBuffer. This is done by a new function in
xmlIO.c:
Hi,
On Sat, 2005-11-05 at 20:23 -0500, Sir Woody Hackswell wrote:
Hello, all! I believe I've come across a problem with Schema validation.
Here's my scenario:
I have a custom type (in this example, pricetype. My Element is
nillable, but the validator always bombs on it, because the item
When validating with a schema against an empty document,
xmlSchemaFormatNodeForError crashes because the document node, passed in
from xmlSchemaValidateDoc, does not have node-ns and passes the if
(node-ns != NULL) test resulting in a crash when node-ns-href is
accessed for the error message.
Hi,
On Mon, 2005-11-07 at 08:08 -0500, Rob Richards wrote:
When validating with a schema against an empty document,
xmlSchemaFormatNodeForError crashes because the document node, passed in
from xmlSchemaValidateDoc, does not have node-ns and passes the if
(node-ns != NULL) test resulting
Daniel Veillard wrote:
Any reason why this couldn't or shouldn't be done the same way
xmlNewTextWriterMemory is done?
Would only require the addition of write and close callbacks and not
require any of the other new stuff from the patch.
Right, while Geert patch is correct, an approach
Wow! You're right! I respectfully disagree with the standard, but it's
what we must follow. Nillable to me meant that it could have a null
value. It seems silly to me to declare that it's empty... because you
can just check if it is or not. =shurg= It's like those manuals that
have THIS
On Tue, Nov 08, 2005 at 12:44:19AM +0100, Kail wrote:
I've a problem with an old SGLM.
This have many format error, the 2 most annoing are:
1- Have more than 1 element as root child
//Start of file
reuters /reuters
reuters /reuters
etc.
This file is 7
