Once my brain re-engaged, I realized that the compare routines are, indeed,
incorrect. _And_ my fix was wrong, too. Here's a correct, working, tested
version of the comparison loop:
while ((*cptr1 != 0) && (*cptr2 != 0))
{
wint_t wch1 = towupper(*cptr1);
wint_t wch2 = towup
ok thanks. I was just curious since it seemed that even if I just wanted to
use the DOM parser, I had to include classes from org.xml.sax. I wanted to
know if maybe it would be better for some of these (like InputSource,
ErrorHandler, etc...) should be in org.apache.xerces so that it was more
obv
I mumbled:
> Both of the string compare routines in IconvTransService have problems.
Well... ignore this for right now. I'm still trying to chase down why a prefix
compares equal, but the compare routines as-written appear to be correct.
(Back to debugging...)
--Bill
There's been a nagging problem with ID/IDREF referential integrity error
reporting. If an IDREF isn't found among the declared IDs, the location of the
error is always reported as the last line in the root XML instance document.
This happens because the check isn't done until all documents have be
Pierpaolo Fumagalli wrote:
> I see a strange behaviour of the SAXParser when I parse this document:
How did this message get into this thread? ;)
Anyway, I'm not surprised that there are problems with SAX2beta
support. It has *not* been tested, yet. I posted a request on
the mailing list for some
Gregory Krasnow wrote:
> Since it seems like many of the classes one needs to use regardless
> of parser come form org.xml.sax, am I correct in assuming that
> Xerces is basically a SAX parser that has implemented a DOM tree
> from the SAX parser??
If you look at the code, you'll notice that we
"Timm, Sean" wrote:
> I've got a method that gets passed in a document object. When I
> call it the first time, the getLength call returns 4. I remove
> a node based on some criteria. Later on, this function gets
> called again and the same document is passed in. This second
> time, the get
Both of the string compare routines in IconvTransService have problems. As
written, they return equal if one string is a prefix of another. (i.e. "wxyz" is
reported as equal to "wx")
The comparison loop from compareIString() currently looks like this:
while ((*cptr1 != 0) && (*cptr2 != 0))
{
Pierpaolo Fumagalli wrote:
> Don't lie :) You forgot to update it yesterday :)
> CVS logs tell me that you uploaded the deprecated version 4 hours ago,
> so, the one I downloaded yesterday WAS NOT deprecated :) :)
At the time I made the statement, I though that it
was updated. But then I checked a
[EMAIL PROTECTED] wrote:
> Once you get them happy, definitely send them to us so
> that we can include them in the next drop...
Okay, Dean. The OS/2 port based on VAC++ 4.0 is starting to look pretty happy.
When it's ready, do I post patch files onto the list, send them to somebody,
or... ? (Som
Pierpaolo Fumagalli wrote:
>
> I found a small "bug" or a discrepancy between how the SAX parser
> behaves and how the DOM parser does:
That's not a bug. As far as the DOM Level 2 is concerned every namespace
declaration attributes is, by definition, bound to
"http://www.w3.org/2000/xmlns/";. The
Since it seems like many of the classes one needs to use regardless of
parser come form org.xml.sax, am I correct in assuming that Xerces is
basically a SAX parser that has implemented a DOM tree from the SAX parser??
- Greg
Gregory Krasnow
Senior Software Engineer
Stone Analytics, Inc.
[EMAIL
Here I come again :) For the last time tonight (I hope) :)
I see a strange behaviour of the SAXParser when I parse this document:
?xml version="1.0"?>
]>
What happens on the sax? Here is a "trace" of the combined content and
lexical handlers installed:
setDocumentLocator
startDocument
It's not nice to do it like that but you can produce text with
type of elements. That did the trick for me in a similar
case.
On Thu, Feb 10, 2000 at 09:58:53AM +0800, Mike Chan wrote:
> Hi All,
>
> I would like to transform my XML doc into a WML doc. Because the WML doc
> itself is another XML
On Wed, 9 Feb 2000 09:27:24 -0800, Paul Pitt wrote:
>if you find out how to get "unsubscribed... plze tell me. I have been
>trying for months and putting "block sender" on thousands of people.. I
>have written and tried and beggeed and pleaded and even prayed to the
>digital god. I cannot
A general XML question:
What's the most efficient way of appending data to a XML document? Let's
say I'm implementating a log file using XML. If I choose DOM, I need to
parse the file to DOM, get the document element, append the child node
and serialise back to file. I can't think of anyway using
I'm a pain... I know it :)
But I found another one
On the DOM parser, if I use:
> parser.setFeature("http://apache.org/xml/features/dom/defer-node-expansion",false);
wich is NOT the default, I get all document correctly.
If instead I leave the defer-node-expansion feature to true, instead
of
I found a small "bug" or a discrepancy between how the SAX parser
behaves and how the DOM parser does:
I have this document:
http://www.betaversion.org/2000/test";>
Test
When parsed the DOM parser reports that the attribute "xmlns:test" has
the following properties:
- namespace uri: http:
Rahul Jain wrote:
>
> +1
This lead to another problem, where does Xerces-PERL goes ?
A third project? Together with Xerces-C ?
Pier
--
- P I E R -
stable struct
+1
+1 from me on doing the separation.
- Anupam
- Original Message -
From: Ralf Pfeiffer <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, February 02, 2000 12:06 PM
Subject: separate xerces-dev into xerces-c-dev xerces-j-dev (+1)
> Dear xerces-dev community,
>
> I would like
Use:
http://www.w3.org/1999/XSL/Transform";>
http://www.wapforum.org/DTD/wml_1.1.xml";
media-type="right-type-for-wap"/>
If your XSLT Engine supports the
as per the XSLT 1.0 Recommendation, this should
produce the desired output. I know
The formatter/serializer should create the document declaration for you,
no need to specify it in the stylesheet.
arkin
Mike Chan wrote:
>
> Hi All,
>
> I would like to transform my XML doc into a WML doc. Because the WML doc
> itself is another XML doc, I have to include tag
> and the tag at
Hi All,
I would like to transform my XML doc into a WML doc. Because the WML doc
itself is another XML doc, I have to include tag
and the tag at the very beginning. However, this causes
problem when I apply the following XSL stylesheet:
http://www.w3.org/1999/XSL/Transform";>
I've got a method that gets passed in a document object. When I call it the
first time, the getLength call returns 4. I remove a node based on some
criteria. Later on, this function gets called again and the same document
is passed in. This second time, the getLength call *also* returns 4
(inst
Is there a way in Xerces-C to find-out which elements
reference an element with a given ID?
Example:
]>
Basically, I want to get a list of REFERENCES which
point to a given ITEM.
DOM_NodeList nodes = doc.getElementsWhichReference(
"ITM.1" );
// node
I have applied the following changes to the source in my attempt to
get Xerces to compile on HP/UX 11.00 with g++.
1) New config.guess and config.sub, taken from GCC. The ones in the
distribution don't recognize the OS version.
2) Added the following to Makefile.incl in the HP/UX specific s
27 matches
Mail list logo
