wchar_t is messy. For the platforms you mentioned, if sizeof(wchar_t) ==
2 wchar_t will be utf-16. If the size is 4 bytes and __STDC_ISO_10646__
is defined, wchar_t is UCS4. I think. But this definitely does not cover
all possible platforms.
If you know that your Unicode data has no code poin
That is a fairly huge topic and not specific to Xerces-C. I would
recommend "Unicode: A Primer" by Tony Graham when you are ready to get
into all the gore.
For an quick overview, XML.com had a article last year:
http://www.xml.com/pub/a/2000/04/26/encodings/index.html
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1605
*** shadow/1605 Wed May 2 14:53:48 2001
--- shadow/1605.tmp.12166 Wed May 2 14:53:48 2001
***
*** 0
--- 1,40
+ ++
+ | Null attribute nam
Hi,
This might be a hair off track but not much...
I was courious about multi-lingual support, many of you must program for multilingual
support, and I was courious about how you encoded your XML/data etc. Is UTF-8 the
most common and readily used form of encoding? and are there standard C/C+
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1601
*** shadow/1601 Wed May 2 08:53:55 2001
--- shadow/1601.tmp.8691Wed May 2 08:53:55 2001
***
*** 0
--- 1,76
+ ++
+ | DOMString bug
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1599
*** shadow/1599 Wed May 2 07:50:02 2001
--- shadow/1599.tmp.8484Wed May 2 07:50:02 2001
***
*** 0
--- 1,20
+ ++
+ | Memory Exception i
Hi Bill,
Basically in Xerces, Exceptions are organized into couple of groups,
as shown below:
1. DOM_DOMException
2. SAXException
3. XMLException
4. EndOfEntityException (internal only)
From application perspective, only the first three exception need to be
taken care.
Hi all,
Any reason why the classes in Xerces that can be thrown as exceptions aren't all
derived from soem common base classs? This would make life a lot easier for programs
that don't need detailed error information, and just handle parser errors in a more
general way. It would probably not b
