James,
Do you know if anyone is (or has attempted) creating an Objective-C
wrapper for Xerces? Until there's an Objective-C++ compiler again,
building a wrapper seems like the only way to get Xerces into a
Cocoa app.
--Bill
On Wednesday, May 30, 2001, at 09:13 AM, Tinny Ng wrote:
> I would like to propose that Pei Yong Zhang be given CVS commit access
> for the Xerces-C project.
+1
--Bill Schindler
-
To unsubscribe, e-mail: [EMAIL PRO
> I have attempted to utilize VisualAge C++ 4.0 to build this parser
> on NT.
> As it stands, the current configuration file (XML4C2X.ICC) that
> came with
> the download (XML4CSRC3_3_1.zip) is nothing close to being correct
> for the
> source provided.
You can try using the .icc files I creat
> It seems as though the cleaner way to solve this problem is to
> provide a
> function from within the .DLL which de-allocates the memory
> allocated by the
> .DLL. This gets rid of compiler run-time errors such as threading,
> debugging, statically dynamically built libraries, etc.
The clea
On Wednesday, April 18, 2001, at 10:43 AM, Ideshini Naidoo wrote:
> Does anyone know how to extract an entire structure from a DOM tree
> and return the structure in XML format in a char *.
You can do that by editing the DOMPrintFormatTarget class in the
DOMPrint sample. (Look in the DOMPrint.c
Just to be sure of a few things...
Which version of Xerces are you using?
>> table.removeChild(row);
The node "row" is going out of scope or being set to NULL after
this, right?
It appears as though cloneNode() goes through all the right
gyrations. I'm not entirely convinced that a node
On Friday, April 13, 2001, at 11:33 AM, Day, Evan wrote:
> Code snippet begins here:
>
> DOM_Element row = thePage.getElementById("template");
>
> DOM_Node table = user_row.getParentNode();
>
> for(int i = 0; i < len; i++) {
>
> setTextById("cell1", cell1_da
On Thursday, April 5, 2001, at 11:49 PM, [EMAIL PROTECTED] wrote:
> has anyone done any work to build xerces-c underneath mac os x?
Look in the c/Projects/MacOS/ProjectBuilder directory.
It looks like the project may need some changes to work with Mac OS
X 10.0 (versus the PB). (But that could
See [2] under 2.2 Characters:
"... Legal characters are tab, carriage return, line feed, and the
legal characters of Unicode and ISO/IEC 10646. ...
Character Range
[2] Char ::= #x9 | #xA | #xD | [#x20-#xD7FF] |
[#xE000-#xFFFD] | [#x1-#x10] "
On Tuesday, April 3, 2001, at
> 1. Does xerces-c_1_1 support encoding="UTF-16" ?
>Because I tried this encoding and results were
> negative.
Try adding the endian -- "UTF-16LE" (for little endian) or "UTF-16BE"
(for big endian).
If I remember correctly, some UTF-16 related bugs were fixed recently.
Xerces 1.4 is probab
On Friday, March 23, 2001, at 09:57 AM, Williams Roger wrote:
>
>
>
>
If you checked the type of the first node of you would
discover that it is not an element node. The DOM tree that's created
from your XML above would produce something lik
11 matches
Mail list logo
