Re: Special char within an XML ï

Hi, On 30 Mar 2005, at 14:59, Orly Caduri wrote: Hi, I need to parse the following xml € this ï is a message I first place the string in a Dom and then extract the value of the tag . Then I place the return string into a Dom and parser it as well

Special char within an XML ï

Hi, I need to parse the following xml € this ï is a message I first place the string in a Dom and then extract the value of the tag . Then I place the return string into a Dom and parser it as well, everything works fine except that when I tr

How to handle special processing instuction ?

Hi, while converting my app from Qt library XML parser to Xerces-C 2.6, I am confused with spec. proc. instruction. 1) In Qt, only one way to set XML version or encoding is via creating proc. instruction . In Xerces, this possible too, but also there are functions DOMDocument:: setEncoding/V

Re: Xercesc Api Documentation: remove collaboration diagram?

Am Mittwoch, 30. März 2005 14:57 schrieb Jesse Pelton: > I can say definitively that at least one person uses the API > documentation (me).  Since I didn't raise the accessibility issue, > I'll bet there's at least one other person who uses it.  I've never > had any use for the collaboration diagra

Re: fgDOMWRTFormatPrettyPrint causes double 0A in output

> I'd agree if this were a violation of am specification, but it's not. > CUT I agree, but it is violation of ordinary common sense. > >... If not, and if it would be committed, I'd be > happy to make a patch that gets rid of them. > It will be nice. This save my time and allow me focus to anot

Re: fgDOMWRTFormatPrettyPrint causes double 0A in output

Am Dienstag, 29. März 2005 15:30 schrieb Jesse Pelton: > I'd agree if this were a violation of am specification, but it's not. > If you have read the thread I referred to, you know that > pretty-printing is only loosely specified. This means, in essence, > that implementations can do whatever they

RE: Xercesc Api Documentation: remove collaboration diagram?

I can say definitively that at least one person uses the API documentation (me). Since I didn't raise the accessibility issue, I'll bet there's at least one other person who uses it. I've never had any use for the collaboration diagrams. > -Original Message- > From: David Cargill [mailt

[jira] Closed: (XERCESC-1388) Special char within an XML ï

[ http://issues.apache.org/jira/browse/XERCESC-1388?page=history ] Alberto Massari closed XERCESC-1388: Resolution: Invalid Orly, this is a question, not a bug report, so it should be sent to the mailing list xerces-c-dev@xml.apache.org Albert

Re: Xerces Unicode

*** NOTE *** Dear Sir/Madam, Your e-mail address has not been registered previously with this incoming mailbox. Due to excessive amounts of incoming unsolicitated e-mails, Your e-mail may be filtered out. If You think that happens, or if You wish to make your e-mail address white-listed for this

Re: Xerces Unicode

Jesse, I used a hexdump utility to examine the contents of your file. It's UTF-16 with a byte-order mark (BOM). The BOM enables a parser to determine the encoding and byte order without reference to the declared encoding. (With a 16-bit encoding, you have to know whether the high-order byte come