Re: some queries related to xerces usage.

Hi Sandeep,

As apparently everybody else who'd know a lot better than me is in 
holiday, I (a non Xerces C developer) will try to answer a few questions:
Sandeep Shahane sandipshahane-at-yahoo.com |xerces-c-users mailing list| 
schrieb:
> Hi,
>     I am planning to use xerces library for XML
> parsing.  I have few queries related to it before
> going ahead:
> My application supports different platforms as below
> (with minimum versions)
> Sun 5.8
> HP-UX 11.00
> Red Hat Linux 8.0
> SUSE Linux 8.0
> AIX 5.1
> Does xerces supports all above OS with these minimum versions?
>   
I would suppose the binary distributions won't run on older OS versions, 
but you can build Xerces yourself:
http://xml.apache.org/xerces-c/build-winunix.html#UNIX
> What encoding is supported by default, is there any way to set xerces to be 
> used in a specific encoding say UTF-8 or UTF-16?
> Is it possible to do XML string conversions from one encoding format to other?
>   
No clue if you can reset the default, but what I've seen so far is that 
Xerces uses wide characters throughout it's API, and it has string 
conversion functions (see XMLString::transcode() in the API docs)
> During parsing an XML, can I parse a partial data for a given tag say for 
> example some node value is very huge and if I want to parse it in chunks, is it
> possible? how can I do it?
>   
I've seen API calls for incremental parsing, but I don't know details 
about that... At least for SAX there seems to be support for it (see 
SAXParser::parseFirst() and SAX2XMLReader::parseFirst() etc. in the API 
docs: http://xml.apache.org/xerces-c/api.html)
> I have used MSXML for creating XMLs, is there similiar way (APIs) to build XMLs 
> or do I need to write ones using some xerces APIs internally?
>   
I'm not sure I know what you mean here - are you asking if there's a 
wrapper for XercesC to mimic MSXML's API? (and if yes, I wouldn't know). 
Hower, the APIs will be similar in certain cases, as I'd expect MSXML to 
use a DOM for representing document trees and SAX for stream parsing. 
Xerces does that.
> Thanks in advance,
> Sandeep
>   
Hope that helped a bit!

Cheers,

Uwe