DO NOT REPLY [Bug 21990] - ICULCPTranscoder::transcode memory leak

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

DO NOT REPLY [Bug 22760] - Invalid schema is reported to be valid

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: upgrade from xerces C 2.1 to 2.2

At 18.38 27/08/2003, Vincent Finn wrote: Hi, I have upgraded from xerces C v2.1 to v2.2 and a strange thing is happening The xerces namespace was added between the 2 versions so I put using namespace XERCES_CPP_NAMESPACE; globally The strange thing is that even with the using statement I still ha

upgrade from xerces C 2.1 to 2.2

Hi, I have upgraded from xerces C v2.1 to v2.2 and a strange thing is happening The xerces namespace was added between the 2 versions so I put using namespace XERCES_CPP_NAMESPACE; globally The strange thing is that even with the using statement I still have to scope any use of DOMDocument all

Xalan1.5 built with VisualStudio 6 SP5.

Hi all, We have built Xalan1.5 with Visual Studio 6 SP5. Sporadically call to XalanTransformer::transform is failing by returning -1. This is noticed only on twin CPU machines and if the tracing is enabled in the calling executable the fault is not reproducible(May be the tracing will introsuce so

Re: Japanese file Names cant be resolved by SAX on Mac OS X

Birinder, Here are some answers that would be helpful either to you or to me: - Are you running on Mac OS X or Mac OS 9? - Does your call to FSMakeFSSpec return an error code? - Does your call to FSMakeFSSpec return to you a valid FSSpec? - What is the path that is returned by XMLCreateFullPathFr

Re: Japanese file Names cant be resolved by SAX on Mac OS X

Birinder, I'm puzzled if you can make a round-trip through XMLCreateFullPathFromFSSpec/XMLParsePathToFSSpec, unless perhaps our final decode back into utf-8 isn't providing the proper form of decomposed unicode desired by the file system. Please put a breakpoint at XMLMacPosixFile::open (note tha

RE: Japanese file Names cant be resolved by SAX on Mac OS X

Hi James I mentioned the OS in my subject OS X FSMakeFSSpec doesnt return an error code (returns 0) and i think that fsspec is hence valid or is there any other way to see this XMLCreateFullPathFromFSSpec converts the passed string to unicode If i pass the path returned by XMLCreateFullPathFromFS

DO NOT REPLY [Bug 22760] - Invalid schema is reported to be valid

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

DO NOT REPLY [Bug 22760] New: - Invalid schema is reported to be valid

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

Japanese file Names cant be resolved by SAX on Mac OS X

Hi all I am passing a file path having some japanese named folders in the path to the SAX Parser to parse the file I do the following stuff on Mac -- FSMakeFSSpec(0,0,filePath,&fsspec); XMLCh *newPathPtr =

Error when using entity resolver

Hi, I have the following problem: I have a DTD in a MemoryBuffer that the parser (SAX) should use when it is parsing many xml files. The first problem is that the parser doesn't remember the DTD (perhaps loadGrammar does not work correctly?), so I use an entity resolver to return my membuffer-DTD

RE: xerces parser cant parse or open files with Japanese Name?

i got the solution I should have used the call to the parser that takes unicode string as input parameter of fileName thx -Original Message- From: Birinder Singh [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 27, 2003 10:40 AM To: [EMAIL PROTECTED] Subject: xerces parser cant parse or

xerces parser cant parse or open files with Japanese Name?

Hi all I am trying to pass the SAXParser a fileName that is in Japanese and it gives me the following error Runtime Exception : The Primary Document entity could not be opened : Id = "the file path" I am indeed passing it the full path Is it that the parser cant open the files with names other