[EMAIL PROTECTED] wrote:
>
> > Okay, it's time for a 1.0.2 release. I'd like to have a 1.0.2 binary
> > release
> > by the middle of next week. Any objections? Again, IBM is volunteering
> > to do the build unless someone else wants to do it.
>
> Java or C++, or both?
I was thinking about Ja
Ted Leung wrote:
>
> Okay, it's time for a 1.0.2 release. I'd like to have a 1.0.2 binary
> release
> by the middle of next week. Any objections? Again, IBM is volunteering
> to do the build unless someone else wants to do it.
I'm currently using what's in the CVS right now, and I found no bu
Entities (external and internal) work like C++ macros in that they are kind
of expanded in place and parsed as though they were literally part of the
enclosing entity. So they don't require a new parser to handle them.
Dean Roddey
Software Weenie
IBM Cen
Do you think that large tables are being made per instance?
What do you do for external parsed entities? Is there a way I could fake
it out into thinking xsl:include & xsl:import is a parsed entity?
-scott
We have functionality like this on the wishlist -- see
the STATUS file. But we are probably going to do it
after Schema support so that the functionality works for
both DTD's and Schema.
Ted
- Original Message -
From: "Steve Ball" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday,
You definitely cannot re-enter the same parser instance while
another thread is executing inside it. I don't see an easy solution
other than new'ing a separate parser instance.
- Original Message -
From: "Scott Boag/CAM/Lotus" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, Ja
I'd like to see it fixed, but I can't promise that we'll use it this time
around.
We have to jigger our distributed build and test system to switch to ant,
and
I'd rather have the build sooner. If you can do it in time, that'd be great
because I think people really want to try ant. But don't kill
Ted Leung wrote:
>
> Java only
Ted, I'll fix Ant on javadoc2 for you tonight so that you can switch to
ant-only build process if you like.
what do you think?
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<[E
Java only
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, January 21, 2000 2:10 PM
Subject: Re: Xerces 1.0.2 release plan
>
> Java or C++, or both?
>
>
> >Okay, it's time for a 1.0.2 release. I'd like to have a 1.0.2 binary
> >release
> >by the m
Java or C++, or both?
>Okay, it's time for a 1.0.2 release. I'd like to have a 1.0.2 binary
>release
>by the middle of next week. Any objections? Again, IBM is volunteering
>to do the build unless someone else wants to do it.
Okay, it's time for a 1.0.2 release. I'd like to have a 1.0.2 binary
release
by the middle of next week. Any objections? Again, IBM is volunteering
to do the build unless someone else wants to do it.
Ted
Well, no one has complained, so I'll check this change in today.
Dean Roddey
Software Weenie
IBM Center for Java Technology - Silicon Valley
[EMAIL PROTECTED]
"Abhijit Savarkar" <[EMAIL PROTECTED]> on 01/20/2000 08:21:37
PM
Please respond to [EMAIL P
Davanzo Luca <[EMAIL PROTECTED]> asks
> If I understand correctly the documentation for xerces-c 1.0.0.d01 for
win32
> systems, it is stated that there is not built-in parsing for ISO-8859-1
> caracters; infact i get errors if I try to parse with a DOMParser these
> characters; however in the FAQ
For xerces-c there are perl scripts under /c/scripts directory that
will build/package the xerces code to desired target directory. These
scripts were made to ease the distribution of the code. However, we do not
support any technical questions on the usage of these scripts
Please feel free to
Hello!
I don't shure that this list is right place, but
- Original Message -
From: Stefano Mazzocchi <[EMAIL PROTECTED]>
To: Dmitry Melekhov <[EMAIL PROTECTED]>
Sent: Friday, January 21, 2000 8:59 PM
Subject: Re: 8 bit
> Dmitry Melekhov wrote:
> >
> > Hello!
> >
> > How can I fo
I'm looking into porting Xalan to Macintosh. If I'm successful I'd like to
get the changes into the source base. The first thing I noticed is that in
several places you're using size_t instead of std::size_t. I'm guessing its
just a slip-up since in many other places you are using the std namespace
Michael Burbidge wrote:
>
> Is someone working on a C++ version of Xalan? If so, what's the time frame
> for its release?
>
> Mike-
Yes, see
http://xml.apache.org/xalan/xslt4c.html
for details. It's for windows only at the time.
Axel
Is someone working on a C++ version of Xalan? If so, what's the time frame
for its release?
Mike-
Hi,
I was looking into building Xalan-C++ on Solaris and therefor
Xerces-C++.
I found the build system of Xerces a bit harsh to get along, at least
for people new to it.
Has there been any discussion about whether to use libtool, and stay a
bit closer to the directory-standards in autoconf-automa
Dear Sir:
I need to build Xcerces-C on VxWorks. I am using Tornado 2. Could you please
give some suggestion?
Thank you very much and look forward to hearing form you.
Yours truly,
Guanglin Shen
Guanglin Shen
Mitel Corporation
350 Legget Drive, P.O.
If I understand correctly the documentation for xerces-c 1.0.0.d01 for win32
systems, it is stated that there is not built-in parsing for ISO-8859-1
caracters; infact i get errors if I try to parse with a DOMParser these
characters; however in the FAQ you state that in the binary drop there is a
/b
new code fyi; pasted directly from cpp file without formatting.
thanks
unsigned int
XMLPlatformUtils::readFileBuffer( FileHandle theFile
, const
unsigned inttoRead
surprise ! surprise !!
it got built on my m/c today with void* and
with long it gave the compilation error.
I had actually uninstalled Microsoft Web & Internet samples yesterday.!!!
So rests the case.
Thanks everybody for your kind participation!!
Abhijit Savarkar
> -Original Messag
The file 'winbase.h' in the January 2000 Platform SDK is the place.
It's usually a good idea to install the latest Platform SDK. They have
updates and corrections to the SDK subset included with Visual C++.
Regards,
Eric Ulevik
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL
> unless the document is just
> pathologically deeply nested
The DocBook stylesheets are pretty pathologically nested.
> (or circular of course :-) Do you try to catch
> circular references?
Yes. (Unless there is a bug...)
We need to do more analysis on this to see how many parsers are parsin
For the C++ version, this should be ok. You can just create new parsers to
handled nested parses. You are only limited by the virtual memory on the
machine. Definitely you cannot reuse the parser at that point though, so
you will have to create new parsers for each nested include. They aren't
al
never mind. Sorry for the noise.
(1) I discovered the createDocumentType() method in
DocumentImpl (I was misled by looking at the create*
methods in Document).
(2) putting the doctype declaration is less important
to me, now that I have realized that it wont modify my
DOM tree. (please correct me
27 matches
Mail list logo