DO NOT REPLY [Bug 27270] - Xerces cannot open file whose name includes UTF8 characters

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: Thread Safety Requirements on Xerces Transcoders?

On Feb 27, 2004, at 4:03 AM, Jeroen N. Witmond wrote: Yes, I always assumed this (and usually, the LCP transcoder is just a wrapper for some OS-specific API, with no fields defined in the class definition). Yes, but this is based on the assumption that the implementation of the OS-specific API is

RE: optimizing the xerces libraries

Visual Studio 6 doesn't seem to have any sort of "Project Defaults" setting on the General tab, or any other tab. Adam Heinz Senior Software Developer Exstream Software -Original Message- From: Erik Rydgren [mailto:[EMAIL PROTECTED] Sent: Friday, February 27, 2004 2:34 AM To: [EMAIL PROT

RE: Not able to make XercesDOMParser Schema Validation working

At 19.56 26/02/2004 +0100, Borislav Stoyanov wrote: 10nx SchemeLocation value was not complete (namespace was missing). I cannt still get it validated though. One thing is still unclear: all the elements in the file have the prefix XX:Element which in normal situation is given by xmlns:XX="http://

Re: Thread Safety Requirements on Xerces Transcoders?

> At 16.21 26/02/2004 -0800, James Berry wrote: >>Since a single global LCP transcoder is used by XMLString (and another by >>DOMString) it would appear that LCP transcoders, anyway, must be >> re-entrant. >> >>Can somebody backup my assertion? > > Yes, I always assumed this (and usually, the LCP t

Re: Problem with release()

Hey, take a look in the archives for a detailed response from me about why this is (would have been [EMAIL PROTECTED] then). Only some things are recycled (like DOMElements). If the DOMElement news something that is not an object that is recycled (eg like the new of the attibute list in the

Problem with release()

This code gives me a memory leck: XMLCh *tmpCh=transcode("OK"); DOMNode* m_idRoot; while(1) { m_idRoot= m_idDocument->createElement(tmpCh); //**Not correctly released m_idRoot->release(); Sleep(10); } Why? Is it a bu

Re: Thread Safety Requirements on Xerces Transcoders?

At 16.21 26/02/2004 -0800, James Berry wrote: Since a single global LCP transcoder is used by XMLString (and another by DOMString) it would appear that LCP transcoders, anyway, must be re-entrant. Can somebody backup my assertion? Yes, I always assumed this (and usually, the LCP transcoder is jus

RE: Unicode with MFC (was MemBufInputSource with CString)

Hi, Lei (ant others).   Meanwhile I was able to handle the problem. The solution does not look nice, but serves my needs:   I create a DOMTextNode with my text, then have Xerces DOMWriter serialize it to a memory buffer, and finally write that to my log file. So Xerces takes care for the co

DO NOT REPLY [Bug 27287] New: - Add support for ISO-8859-15

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