DO NOT REPLY [Bug 6637] New: - full paths don't work for -c, -x in runConfigure

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: DOM_Document problem...HELP REQUIRED URGENTLY

> Hi All > I am passing reference of DOM_Document to a function where I am modifying > the DOM_Document and hence the DOM_Document change is reflected in my main > program I have tried same by first copying original DOM_document instance to another variable and passed this variable to my

DO NOT REPLY [Bug 6605] - link error while complie the samples

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 DOM API: to NS or not to NS?

>But in that case, the serializer will have to be aware of the >hierarchy Yep. But since folks _can_ constuct entirely legitimate DOM trees with namespaced nodes and without namespace declarations, the serializer really doesn't have much choice about this, unless it wants to throw exceptions or

Re: xerces DOM API: to NS or not to NS?

> When you serialize the document out to XML syntax, it is the serializer's > responsibility to recognize this situation and automagically create any > namespace declaration attributes which may be required. > > So if anything, this is easier for you than it would be using the old > calls. But i

RE: C0 control characters - U+0000 through U+001F

Yes, they are really forbidden.  The check is definitely done post expansion.  I even tried setCreateEntityReferenceNodes(true).  This, of course, creates the entity reference node and adds the expanded entity as a text node child of the entity reference node.  When it does that, we get the Invali

RE: C0 control characters - U+0000 through U+001F

>Can you use XML's &#xx; notation to represent the characters? Might be nice if it did, but that's not the way XML works. The forbidden characters really are completely forbidden, and have to be represented some other way. -

Re: C0 control characters - U+0000 through U+001F

At 08:10 AM 21-02-02 -0500, Thomas Bentley (Thom) wrote: >I have existing data that contains these ASCII control characters and I >need to represent them in XML. Xerces complains about them (because they >are less the 0x20), but I need to represent them in a standard way so they >can be recrea

Re: C0 control characters - U+0000 through U+001F

This is something of an XML FAQ... Most of these characters are not legal in XML, and there really is no way to represent them directly. Even numeric character references won't get you past this restriction. The standard workaround is to replace them with some other representation. There really

Re: C0 control characters - U+0000 through U+001F

You know, though I wrote that code, I cannot remember how it would react if you did this. It depends on whether the character validity checking is pre-expansion or post-expansion. If its pre-expansion, you'd be ok, because the converted char would would just get turned into Unicode chars internall

RE: C0 control characters - U+0000 through U+001F

Can you use XML's &#xx; notation to represent the characters? Samar Lotia -Original Message- From: Thomas Bentley (Thom) [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 21, 2002 07:10 To: [EMAIL PROTECTED] Subject: C0 control characters - U+ through U+001F Importance: High I ha

C0 control characters - U+0000 through U+001F

I have existing data that contains these ASCII control characters and I need to represent them in XML. Xerces complains about them (because they are less the 0x20), but I need to represent them in a standard way so they can be recreated at a later time, correctly. Has anyone solved this one?

Re: xerces DOM API: to NS or not to NS?

>It seems that both sets of API can lead to *exactly* the same output >when the DOM was converted back into XML. Yes, because XML Namespaces were made to fit into the pre-existing XML syntax. If all you're going to with the DOM is write it out, you can get away with this. However, if you're goi

Re: Using 1.6.0 compiled under xlC_r 3.6.6 under AIX

Steve, Chances are you will be fine, especially as the samples seem ok. Previously, Xerces-C also used xlc_r and xlC_r to do their production builds, and they worked fine. I think an effort has been made to avoid using constructs that are compiler- version-specific. For example, that's the reas

Re: Building error on HPUX 10.20

Jorge, While I haven't tried to build Xerces-C on HPUX 10.2, I have built it on HPUX 11.00, with no problems. One of my own programs ran into this problem on HPUX 11.00 but it was due to the object files requiring too much memory during linking. We were on a server that had only 1GB of ram, and

Re: xerces DOM API: to NS or not to NS?

Dave, Thanks for the clarification - I guess I misled you (unintentionally) when I said I needed to generate namespace aware XML, I did not mean that I needed a namespace aware DOM - but that the serialized output had namespace references. Thanks, Keyur - Original Message - From: "David

Re: xerces DOM API: to NS or not to NS?

If you create an element with createElement(), when you call getNamespaceURI() on that element it will return a null string. So even if you get the same output when you serialize the DOM, it doesn't mean the element is identical to an element created with createElementNS(). Some differences in

Re: xerces DOM API: to NS or not to NS?

I did not know that the non-NS API were at one point considered for deprecation. Given that - there is no question on which one I will use. My problems with the NS API are minor : 'xmlns' attributes can only belong to one explicit namespace, but I still have to mention which one it happens to be.

Re: xerces DOM API: to NS or not to NS?

It seems that both sets of API can lead to *exactly* the same output when the DOM was converted back into XML. I was only wondering if the NS API offered any advantages in a situation where XML was being generated and not parsed or validated... especially since creating a NS element would not nece

Re: xerces DOM API: to NS or not to NS?

For new code, use the DOM's -NS calls. Period. (The DOM WG would have deprecated the old calls, if we could. Unfortunately, it's sometimes desirable to pass a Level 2 document to old Level 1 code, eg using a modern parser with a pre-existing application. But they were retained _ONLY_ for this pu

Re: xerces DOM API: to NS or not to NS?

If you want to create a document with the correct namespaces, you must use createElementNS and createAttributeNS. Isn't that obvious from their names and the DOM recommendation? Dave

xerces DOM API: to NS or not to NS?

I need to create the following namespace aware XML document:         enUS     someuser     If I use the DOM API to generate element nodes and append attributes, what advantages are there in using createElementNS and createAttributeNS over createElement and createAttribute?   Regards,  

DO NOT REPLY [Bug 6605] New: - link error while complie the samples

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: VC7 Compatability

Add my vote to this - for what its worth :-(. We use xerces for a project that compiles for both PC(VC) & Mac(CodeWarrior) - both of which have wchar_t, however, since XMLCh on PC == wchar_t and on Mac !=, I've altered the Mac code to allow compatability (plue for open source - I could do it, neg

Re: Imlementation

XMLFormatter is a Class. As so, u need to instantiate an object of that class before using it. First declare a pointer to the XMLFormatter class, and then create a new instance of it using that pointer. Remember to free it afterwards.   ...{ gFormatter* XMLFormatter; gFormatter = new XMLF