Hi everybody !!
Thank you very much for your answers. I was
checking what Gareth recommend me. I downloaded
the "xerces-c-current.zip" distribution and tried
to compile by myself but I could not see the
error messages.
However, with this new pre-compiled version I can
read them.
Thank you both
This is what I see with xercesc 2.5.0 binaries from distribution
file xerces-c_2_5_0-windows_nt-msvc_60.zip:
=
E:\DOMPrint\Debug>DOMPrint -v=always -n -s x1.xml
Error at file "E:\DOMPrint\Debug/x1.xml", line 5, column 34
Message: Required attri
Hi,
the first does cause an error message about the required attribute.
The only change I met was to put the schema in the same directory as
the xml file and referenced it with a relative path. Try this. If this
does not do it then try updating to cvs head - thats what I use.
Whatever the resu
Hello Gareth !!
Thank you very much for your reply.
I have this schema:
--
--
http://www.w3.org/2001/XMLSchema";
elementFormDefault="qualified"
attributeFormDefault="unqualified">
Hi,
thats certainly not expected behavior. Can you post a minimal xml
document and schema that demonstrates this?
Cheers,
Gareth
elsa lizette wrote:
Hello everybody !!
I am trying to validate an xml using a schema.
I compiled DOMPrint example and run it:
DOMPrint -v=always -n -s x1.xml
However,
Hi Alberto,
Some OS's return UTF-8, EUC-JP, but some return utf8,
eucJP. If you have the xml encoding in either way, it
seem to work.
Regards
Prakash
--- Alberto Massari <[EMAIL PROTECTED]> wrote:
> At 03.32 12/04/2004 -0700, P M S Prakash wrote:
> >Hi Alberto,
> >
> >Yes, the original XML docume
At 03.32 12/04/2004 -0700, P M S Prakash wrote:
Hi Alberto,
Yes, the original XML document had UTF-16 encoding.
After changing it to appropriate encoding, it worked.
Also, in my application, I am setting the encoding
using setEncoding, by determining the character set of
the local system. The foll
Hi Alberto,
Yes, the original XML document had UTF-16 encoding.
After changing it to appropriate encoding, it worked.
Also, in my application, I am setting the encoding
using setEncoding, by determining the character set of
the local system. The following is the sample code. Is
it the right way t
Did you specify an encoding when you ran the program? If you specified a
Unicode encoding like UCS-2 or UTF-16, the getRawBuffer() method will
return a pointer to an XMLCh* buffer, not a char*.
Alberto
At 04.31 08/04/2004 -0700, P M S Prakash wrote:
Hi Alberto,
I just changed the DOMPrint.cpp
Dear Frank!
I sent You mail. I have found this error, now work
all well.
Thank You , Susanna Harutyunyan
- Original Message -
From:
Frank
Balluffi
To: '[EMAIL PROTECTED]'
Sent: Monday, October 15, 2001 5:53
PM
Subject: RE: DOMPrint
Susanna
--- Original Message -
From:
Frank
Balluffi
To: '[EMAIL PROTECTED]'
Sent: Monday, October 15, 2001 5:53
PM
Subject: RE: DOMPrint
Susanna,
It
sounds like your program just can not find the DLL. If your program is a
console application, you will nee
Susanna,
It
sounds like your program just can not find the DLL. If your program is a console
application, you will need to restart command.com after setting PATH. If you are
debugging via Visual Studio, you will need to restart Visual Studio after
setting PATH. One solution is to copy the
list of children. Hence the output you received.
-Original Message-
From: Chaim Koshizky [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 25, 2001 10:14 AM
To: '[EMAIL PROTECTED]'
Subject: RE: DOMPrint: Declaration and Document Type
Here is the code i use
m_Doc = m_Impl.createDo
Wednesday, July 25, 2001 3:32 PM
> To: '[EMAIL PROTECTED]'
> Subject: RE: DOMPrint: Declaration and Document Type
>
> You need to use DOM_Document::createXMLDecl() to create a non-null
> XMLDecl:
>
> DOM_XMLDecl domDecl = m_Doc.createXMLDecl ("1.0&
, July 25, 2001 5:35 AM
To: '[EMAIL PROTECTED]'
Subject: RE: DOMPrint: Declaration and Document Type
I tried creating DOM_XMLDecl and insert before.
It does not work the way you describe.
here is the code :
DOM_XMLDecl domDecl;//
hild);
I can not find any documentation on DOM_XMLDecl, but the hpp file.
Any help will be grateful
> --
> From: Jesse Pelton
> Reply To: [EMAIL PROTECTED]
> Sent: Friday, July 13, 2001 6:01 PM
> To: '[EMAIL PROTECTED]'
> Subject:
"Jason E. Stewart" wrote:
>
> "Murray Cumming" <[EMAIL PROTECTED]> writes:
>
> > I'm trying to use the DOMPrint code to ouput the text of a DOM_Document
> > that was constructed entirely in memory by adding nodes. Unlike the
> > DOMPrint example, this DOM_Document was never parsed from XML text.
"Murray Cumming" <[EMAIL PROTECTED]> writes:
> I'm trying to use the DOMPrint code to ouput the text of a DOM_Document
> that was constructed entirely in memory by adding nodes. Unlike the
> DOMPrint example, this DOM_Document was never parsed from XML text.
>
> I find that the declaration text
To set the docType, you have to do something like:
DOM_Document doc;
DOM_DOMImplementation impl;
DOM_DocumentType docType = impl.createDocumentType(...);
doc = impl.createDocument(NULL, // root element namespace
URI
"MyRoot"// root element n
The XML standard says is that various common combinations of CR and LF are
converted to newline as the document is parsed. What they're converted back
to on output is not specified, but any of those combinations is acceptable;
generally, you'd pick whichever line break sequence is recommended by
> On Thu, 28 Jun 2001, "Kent" == Kent Dahl wrote:
Kent> I don't remember the reference, anyone care to confirm or
Kent> unconfirm?
The following is from: http://www.w3.org/TR/REC-xml
2.11 End-of-Line Handling
XML parsed entities are often stored in computer files
which, f
Stefan Berglund wrote:
> static const XMLCh gXMLDecl4[] =
> {
> chDoubleQuote, chQuestion, chCloseAngle
> , chCR, chLF, chNull
> };
>
> Couldn't this be a problem in Unix ? CR/LF can cause a ^M character in some
> cases? Is the XML standard saying that there should be a new line
> after
Its probably just a simple bug in DOMPrint most likely.
--
Dean Roddey
Software Geek Extraordinaire
Portal, Inc
[EMAIL PROTECTED]
-Original Message-
From: Jiwoon Jeon [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 11, 2001 8:38 AM
To: [EMAIL PROTECTED]
Subject: DOMPrint p
Jiwoon Jeon wrote:
> The following XML shows the problem.
> [snip]
>
> I found that the default #FIXED value at line 4 was missing.
> What's wrong with me or DOMPrint?
>
I think you found a bug. I have checked in the fix which should be available in
tomorrow nightly build.
Regards,
Tinny Ng
Those catches outside of the parse() calls are just to catch something that
might go catastrophically wrong before the parsing can really get started.
Its very unlikely to happen, and in any particular release might not ever
happen. But you should be prepared to handle them if they do. If they do,
ssage -
From:
Emma
Towey
To: [EMAIL PROTECTED]
Sent: Wednesday, March 28, 2001 1:34
PM
Subject: Re: Domprint and overwriting
files
Hi,
Thanks a million for your help I have taken your
suggestions.
At the moment I am opening a file inserting new data and
s
ply-To: [EMAIL PROTECTED]
>To: <[EMAIL PROTECTED]>
>Subject: Re: Domprint and overwriting files
>Date: Mon, 26 Mar 2001 15:34:09 -0600
>
>Emma
>
>I might be able to get you in the right direction. I needed to write out to
>a file instead of to stdout. Here is what I c
<< DOMString(e.getMessage()) << endl;
retval = 3;
}
delete formatTarget;
delete gFormatter;
It is neither pretty nor 100% tested, but it is giving me the right answers
so far.
Good luck
Todd Firsich
USAA Bank Applications
- Original Messa
I havent looked at the DOMPrint code myself for a while but I am fairly
sure it does not provide the functionality you require. You will need to
modify it with an extra command line parameter and insert some io code
into the DOMPrint itself. If you do not know how to do this then have a
look in yo
I need to be able to call DOMPrint with a filepath/filename as the parameter, manipulate data ie append new data within DOMPrint and have the new file saved and returned back to me. I dont want to have to set the filepath inside the settings of the project or on the command line.
Any suggesti
What do you mean by it will not save? Have you changed the code so it
outputs to a file? If so then it could be a problem with permissions. If
not, well its doing what its supposed to do. If you just want to save to a
file on the command line then you could redirect the output
./DOMPrint param >
How are you saving
the file?
-Original Message-From: Emma Towey
[mailto:[EMAIL PROTECTED]]Sent: Friday, March 23, 2001 2:39
PMTo: [EMAIL PROTECTED]Subject: Domprint and
overwriting files
I'm taking a file into DOMPrint manipulating it and printing it out onto
the screen. This is w
Hi, Emma,
You may paste the follow code into DOMPrint.cpp
/***testing code start ***/
DOM_Document docu = parser->getDocument();
DOM_NodeList nodeList = docu.getElementsByTagName("Event");
DOM_Node tempNode = nodeList.item(0);
DOM_Element newElem = do
I haven't worked with the C++ version much, but in general the concept
ought to be much the same from one version of the DOM to another. In Java,
it would be roughly as follows. For more detail, see the DOM specification
and/or the XML-DEV mailing list.
parse your document into the DOM, ob
34 matches
Mail list logo
