Hi,
A newbie question: what does "LS" stand for?
Load Save
Another newbie question: what is the functional difference between
DOMBuilder and XercesDOMParser?
The interfaces and some of the default behaviors are different.
XercesDOMParser existed before DOM defined a parser.
Gareth
--
Gareth Rea
"LS" stands for "Load and Save."
I'm not sure about specific differences between XercesDOMParser and DOMBuilder, though
XercesDOMParser is older and more mature. Both build a DOM tree from an input
document when you call their parse methods. DOMBuild::parse() returns a document
pointer; you h
Hi Alberto, hi list members,
that's a perfect solution for me! Thanks a lot for your fast and competent
help!
Regards,
Michael
> -Ursprüngliche Nachricht-
> Von: Alberto Massari [mailto:[EMAIL PROTECTED]
> Gesendet: Mittwoch, 1. September 2004 17:23
> An: [EMAIL PROTECTED]
> Cc: Heeg, M
I hear ya, and I'm glad to provide an opportunity for you to repeat your
plea! I'd write code if I had time. I don't, so I try to contribute by
participating on the list. At the moment, it looks like it might be
more helpful if I were quiet. ;-) But I doubt I'll let that keep me
from trying.
Hi Jesse,
Jesse Pelton wrote:
Last I heard, Gareth suggested that work might start on DOM 3 Core, at least, following the release of 2.6, but I don't recall any further discussion.
I was looking for some volenteers :) No one has replied as yet. As I
said in my previous mail its quite a lot of work
Hi Michael,
if createDOMInputSource doesn't work, try with
LocalFileInputSource file(XMLString::transcode(m_xmlPath.data()));
file.setEncoding(XMLString::transcode("iso-8859-1"));
Wrapper4InputSource wis(&file, false);
m_domBuilder->parse(wis);
Alberto
At 16.12 01/09/2004 +0200, Heeg, Michael wrote
Hi Jesse,
> Umm, well, after reviewing the source, I imagine that the
> exception you're seeing is DOMException::NOT_SUPPORTED_ERR.
Yes, exactly!
> Apparently DOMBuilder doesn't do what you want. This is
> probably because it's an experimental (and incomplete)
> implementation. Maybe it'l
Umm, well, after reviewing the source, I imagine that the exception you're seeing is
DOMException::NOT_SUPPORTED_ERR. Apparently DOMBuilder doesn't do what you want.
This is probably because it's an experimental (and incomplete) implementation. Maybe
it'll get better when the final specificat
Hi Jesse,
thanks for your advice. I tried, but I failed. Please see below the code
fragment.
The part which creates the pointer to the DOMImplementation succeeds (impl
!= NULL),
but the line
"DOMInputSource* myDOMSource = impl->createDOMInputSource ();"
throws an exception.
Any idea?
Regards,
Mi
Looking at the documentation, it appears that DOMBuilder::parse(const DOMInputSource
&source) should allow you to do what you want. You'll need to construct the input
source first, of course. As part of that process, you can call
DOMInputSource::setEncoding().
> -Original Message-
> F
Hi everybody,
I have a problem with parsing a local file into a DOM. I found out that the
reason is the encoding the DOMBuilder uses (UTF-8 by default?), but I did
not find a way how to change it.
The problem is, that the local file has NO header line which sets the
encoding like
""
If I add this
11 matches
Mail list logo
