Re: Validity of leading whitespace

At 04:05 PM 07-06-02 -0400, you wrote: >Using 1.7.0, if I have a document in which whitespace appears before the >initial prolog, I get the error: > > The XML or Text declaration must start at line/column 1/1 > >Where is this required in the XML specification >(http://www.w3.org/TR/2000/REC-xml-2

DO NOT REPLY [Bug 9707] - config.guess out of date

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 9707] New: - config.guess out of date

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: Xerces bogus Memory Leak Errors ?

Please don't post HTML to the list! Your code is broken. The memory from DOMString::transcode() is allocated using new []. It can only be deleted using delete []: void foo(const DOMString& str) { const char* localStr = str.transcode(); ... delete [] localStr; } In addition to

Re: Validity of leading whitespace

See the XML Recommendation. ___NOTHING___ may preceed the declaration except the optional Byte Order Mark. That means no whitespace. Fix your document. __ Joe Kesselman / IBM Research

Xerces bogus Memory Leak Errors ?

Hi All,    Iam trying to run a memory leak checker (Purify) with an XML Processing application linked against Xerces. Iam getting lot of Purify errors while calling transcode() on DOMStrings, even after freeing the pointer returned. I checked the FAQ and it mentioned that such reports *might*

Validity of leading whitespace

Using 1.7.0, if I have a document in which whitespace appears before the initial prolog, I get the error: The XML or Text declaration must start at line/column 1/1 Where is this required in the XML specification (http://www.w3.org/TR/2000/REC-xml-20001006)? According to Appendix F.1: "...ea

Re: XML Decl ?

I can't vouch for Xerces' plans. I can only tell you that the XMLDecl node isn't part of the DOM's standard API, has never been, and isn't currently expected to be in the future. __ Joe Kesselman / IBM Research

DO NOT REPLY [Bug 9697] New: - Make GrammarResolver to be exportable

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: XML Decl ?

Joseph,   Thanks for refs! I just wanted to be sure the XMLDecl node will no longer be supported to modify the existing code accordingly.   Regards, Peter       --- Additional Comments From [EMAIL PROTECTED]  2002-06-07 13:40 ---(DOM Level 3 does plan to add fields to store the data

DO NOT REPLY [Bug 2546] - DOM_Node::XML_DECL_NODE is not imported

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 2546] - DOM_Node::XML_DECL_NODE is not imported

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 7051] - "hash" argument clashes with STL's hash

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 9639] - enum_mem clashes with constant

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: What's the difference...

XML4C 4.0.1 is based on Xerces-C++ 1.6 plus selected high severity fixes and is built with ICU. Tinny - Original Message - From: "Markku Pirila" <[EMAIL PROTECTED]> To: "xercess discuss" <[EMAIL PROTECTED]> Sent: Thursday, June 06, 2002 7:42 AM Subject: What's the difference... > ...be

DO NOT REPLY [Bug 9691] New: - Memory leak when setCreateEntityReferenceNodes is true

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: Surrounding spaces illegal in the dateTime type?

On Wed, Jun 05, 2002 at 04:28:58PM -0700, Stewart, Daniel J wrote: > The following XML snippet validates fine against the xs:dateTime built-in > schema type using Xerces: > >2001-01-01T08:38:22 > > However, it fails validation in XML Spy v4.3. I sent a bug report to > Altova, and their