Colin, Can you describe in more details what is not working?
I've tried the DOMPrint from the nightly build by specifying a folder name as the file name for LocalFieFormatTarget, and I can get the following error: E:\xmltest>dir Volume in drive E is New Volume Volume Serial Number is 0CA3-37F0 Directory of E:\xmltest 01/23/2003 02:04p <DIR> . 01/23/2003 02:04p <DIR> .. 01/23/2003 01:48p <DIR> results E:\xmltest>domprint -wfile=results e:\xerces_c_dev\samples\data\personal.xml An error occurred during creation of output transcoder. Msg is: Could not open file: results Tinny ----- Original Message ----- From: "Colin Paul Adams" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, January 23, 2003 6:31 AM Subject: Bug 15928 not fixed in latest nightly builds > I noticed today that my code using LocalFileFormatTarget with > DOMWriter::writeNode was apparently working (writeNode returns true), but the file was empty. > Inspecting the source code (nightly build of 11th Jan), I see there is > a comment about a bug (15928) for this very problem. Well, it appears > not to be fixed. I reverted to 2.1.0 and my code works again. > > If I can remember, I shall go to Bugzilla tonight, when I can get > online again. But I'm posting this message just in case I forget. > -- > Colin Paul Adams > Preston Lancashire > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
