Re: problems with "carriage return" and "line feed"

> Rather than using a text node won't a section protect > the \r? Nope. Line-break processing does occur in CDATA sections. >Also adding a xml:space="preserve" attribute should work, too, >shouldn't it? Nope. Line-break processing occurs before space preservation, though setting preserve will

Testing the library on UNIX

I've built the library myself on HP_UX 10.20. I need to test the quality, but haven't found any document on how to test the library. I've did a gmake in tests directory. Could you please point me to the document on this matter? Thank you very much. ---

Re: problems with "carriage return" and "line feed"

"Fred Eisele" <[EMAIL PROTECTED]> writes: > Rather than using a text node won't a section protect > the \r? Also adding a xml:space="preserve" attribute should work, too, shouldn't it? jas. - To unsubscribe, e-mail: [EMAIL PR

Re: Newbie Schema Validation Question

First of all the Xerces 1.5 Schema support is a subset of the w3c current recommendation. If you need to validate the schema to a w3c current recommendation there are others tools around there, some public domain, some NOT. I have used XML Spy 4.0 but it cost some $. Anyway, if you have a vali

[DO NOT REPLY: Bug 3126] -

Spaces following PI name and before any character are deleted. PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SO

[DO NOT REPLY: Bug 3126] New: -

Spaces following PI name and before any character are deleted. PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SO

[DO NOT REPLY: Bug 3122] New: -

IDOM_Parser losing Text data PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SOMEWHERE. http://nagoya.apache.org

RE: problems with "carriage return" and "line feed"

Hi all, I have a XML file with a text section inside. The text section contains \r\n characters. I parsed the file with a DOMParser object and than convert the DOM_Document I got, back to text. The text I got was without \r, just \n. I know that the problem is in the DOMParser. For some reason i

Re: problems with "carriage return" and "line feed"

The XML spec says explicitly that CR, LF, and CRLF must be converted to "newline" (encoded as LF) when an XML file is parsed. You can scan for the newlines and convert them back while generating the text... - To unsubscribe, e

[DO NOT REPLY: Bug 3094] -

StdInInputSource class is broken and StdInParse sample no longer works PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE

RE: problems with "carriage return" and "line feed"

This is required by the specification. See http://www.w3.org/TR/2000/REC-xml-20001006#sec-line-ends. -Original Message- From: Shlomi Afia [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 14, 2001 1:13 PM To: '[EMAIL PROTECTED]' Subject: problems with "carriage return" and "line feed" Hi

RE: problems with "carriage return" and "line feed"

That behavior is explicitly prescribed by the XML Recommendation http://www.w3.org/TR/REC-xml#sec-line-ends for all XML processors to maximum interoperability in the face of different line-ending conventions. I do not believe there is a way to disable conformance with this required behavior and

problems with "carriage return" and "line feed"

Hi all, I have a XML file with a text section inside. The text section contains \r\n characters. I parsed the file with a DOMParser object and than convert the DOM_Document I got, back to text. The text I got was without \r, just \n. I know that the problem is in the DOMParser. For some reason it

[DO NOT REPLY: Bug 3094] -

StdInInputSource class is broken and StdInParse sample no longer works PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE

StdInInputSource

It seems like StdInInputSource has been broken in 1.5.1. I have already logged a bug with Bugzilla. The StdInParse sample doesn't work and aborts with:   Fatal Error at (file , line 0, char 0): An exception occured! Type:XMLPlatformException, Message:Could not read data from file stdin: 3

RE: Problem understanding characters() callback in SAX2 parser

Or you get a processing instruction, or a comment, etc... Dave "Prior, Chris"

Re: Problem understanding characters() callback in SAX2 parser

>Is there a way to only get one call to characters or do I have to >concatenate the contents? The latter. SAX explicitly does _not_ promise that all adjacent text will be delivered as a single call to characters(), for reasons having to do with buffer management inside parsers. Entities are one

RE: Problem understanding characters() callback in SAX2 parser

I forgot that you should concat until either endElement or startElement. Thanks what I do anyways. Good luck, Chris -Original Message- From: Benoît Desmeules [mailto:[EMAIL PROTECTED]] Sent: 14 August 2001 16:53 To: [EMAIL PROTECTED] Subject: Problem understanding characters() callback

RE: Problem understanding characters() callback in SAX2 parser

Hi, You have to concat the contents until you get endElement. Chris -Original Message- From: Benoît Desmeules [mailto:[EMAIL PROTECTED]] Sent: 14 August 2001 16:53 To: [EMAIL PROTECTED] Subject: Problem understanding characters() callback in SAX2 parser I don't fully know the internal

Problem understanding characters() callback in SAX2 parser

I don't fully know the internals of Xerces so maybe my problem is caused by a misunderstanding. Although, I'd need some advice about something. I'm using SAX2 to parse an XML file and retrieve its content. It's been running fine for a while until someone used < and > codes in the XML file. Whe

Serialization in Xerces-c

Hi there, Does Xerces-C DOM APIs support any serialization API for DOM Document which will also handle the special XML characters. Right now we have written our own API to serialize DOM Document and handle special XML characters. If anyone has got some knowledge on this and can enlighten me on t

Newbie Schema Validation Question

Hi everyone, I've been working with the sample programs, and have gotten them to work validating personal-schema.xml against personal.xsd, and also validating xml documents against schemas that I have written myself. However, what I need to be able to do, is validate the schema itself-- in othe

Re: [Fwd: Changing include to include/xercesc]

Tinny Ng wrote: > > > > Subject: Re: Changing include to include/xercesc > Date: Thu, 09 Aug 2001 08:01:07 -0700 > From: Tinny Ng <[EMAIL PROTECTED]> > Reply-To: [EMAIL PROTECTED] > Organization: IBM Toronto Laboratory >

Re: Changing include to include/xercesc

Still waiting. Murray Cumming wrote: > > Still waiting: > > Murray Cumming wrote: > > > > I'm still waiting on a maintainer's go-ahead on this. I'm not going to > > do this work only to have it rejected later. > > > > Murray Cumming wrote: > > > > > > "Jason E. Stewart" wrote: > > > > > > > > "