RE: CDataSections on Linux

>If I remove any character from the string the cdata section is correctly >generated and then subsequently printed (see program below), so it looks >like a length error of some sort to me. Does anyone have any thoughts? Perhaps the string needs to be null-terminated? I experienced a problem bet

surrogate pairs

As far as I can tell surrogate pairs aren't correctly processed in attributes, PIs and comments. I filed http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2752 in July Does anyone know if there are any fundamental problems that make this difficult to implement? I would be willing to fix it un

Re: xerces-c-src1_5_1.tar.gz broken?

- Original Message - From: "Nicole" <[EMAIL PROTECTED]> Subject: Re: xerces-c-src1_5_1.tar.gz broken? > I experienced the same problem when I extracted this > tar file. I used the "i" option of the tar command to > ignore checksum errors. I believe I read somewhere in > the archive th

RE: Parse a huge file, piece by piece

Try progressive parsing. Check out the PParse sample; also check out SAXParser::parseFirst and SAXParser::parseNext. -Original Message- From: Feng Tian To: [EMAIL PROTECTED] Sent: 9/6/01 5:36 PM Subject: Parse a huge file, piece by piece Hi, I got a question when use XML4C. I got a h

Parse a huge file, piece by piece

Hi, I got a question when use XML4C. I got a huge XML file, and wonder if I can parse that file piece by piece, that is, I want to do the following char buffer[8192]; SAXParser p; while(read(fd, buffer, 8192) > 0) { // Let p parse t

XML conformance test results DTD & stylesheet

Hi! As announced, I developed a testresults.dtd and also a stylesheet to format the XML result to a HTML page. DTD & Stylesheet: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/pyxml/test/xmlconf/ Example output: http://pirxx.sourceforge.net/results.html Ciao, Jürgen ---

Re: xerces-c-src1_5_1.tar.gz broken?

I experienced the same problem when I extracted this tar file. I used the "i" option of the tar command to ignore checksum errors. I believe I read somewhere in the archive that this error is caused by overly long names. Nicole --- "Jason E. Stewart" <[EMAIL PROTECTED]> wrote: > "Steven E Lumo

Re: basic ?: case sensitivity in validating parsers

XML is case-sensitive. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

basic ?: case sensitivity in validating parsers

Hello, in validating XML parsers (xerces & major others) do they allow you a choice of validating (via a schema) XML w/ case sensitivity turned on or off, both for elements & attributes, and for their respective values (like a boolean being "True, or TRuE", instead of just "true")? thanks -

OASIS test results

Hi! I created a DTD for test results, it can be found at http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/pyxml/test/xmlconf/testresults.dtd?rev=HEAD&content-type=text/vnd.viewcvs-markup A typical result report looks like this: sax2tests 1.5 Valid

Need *effective* access to SchemaGrammar interface after parsing a document

Greetings, I'm working on the following problem. I'd like to parse an XML document and store its contents in a tree-like data structure of our company's own design. Part of that design involves storing attributes and textual content within "simpleType" elements possibly as int, float, double, e

IDOM root element has a XML declaration text node child

Team Xerces-C, After parsing an XML file with IDOMParser, IDOM_Document::getDocumentElement() returns a "root" element containing two children, the XML declaration as a text node and the true XML root element node. Is there a way to configure IDOMParser so that the XML declaration is not added to

result of Attributes::getValue

Hello, When using const XMLCh* Attributes::getValue(const XMLCh*), Who is responsible of the memory allocation of the return ? So : Do I have to XMLString::replicate the return of getValue if I want to store it ? Or Do I have to clear the memory for the pointer returned when I don't need it any

CDataSections on Linux

I seem to be having a problem with createing a CDATA section on a linux implementation of the parser. It appears to be length related, but works fine on NT. Has anyone else run across this and is it a known problem? I had this problem in an application I was porting to linux from NT, having rec

Re: XMLConf update

On 05 Sep 2001 22:20:39 -0600, Jason E. Stewart wrote: >> Makes more sense to generate XML (via a "testresults.dtd" that inherits >> "testcases.dtd") and then run it through XSLT, if you ask me. > >Ah... yes, this is a better idea. That means I really need to get >XML::Xalan working though... Le

Re: Problem initializing and terminating XMLPlatformUtils

Given that the XMLDeleterFor<> is used to released memory allocated for a pointer of global lifetime I'm not sure this is a problem. Just to make it clear, here's the change that I propose: XMLDeleterFor.hpp - 93c93 < XMLDeleterFor(T** toDelete); --- > XMLDe

RE: Problem initializing and terminating XMLPlatformUtils

It doesn't fix all cases. Take a look at gScannerMutex() in src/internal/XMLScanner.cpp: it allocates some memory, for which it registers and XMLDeleterFor, but it also sets a flag indicating that the memory was registered. There's no mechanism for resetting the flag, so the flag is set wrong once

Re: Problems using schema and namespaces

Hi Alberto, Thank you very much. That was exactly what I was looking for because all the other examples I tried before had all some certain type or what so ever that xercesc 1.5.1 doesn't support. And I can't write an example myself because if you are not familiar with things you always wonder if