Mike,
> The MacOS limits filenames to 32 characters. The pathname delimiter on the
> Mac HFS filesystem is the colon ":" rather than the unix / or DOS backslash \
.
This may be a dumb question, but... Do you have the "Interpret DOS and Unix
paths" option checked in the project settings? (That s
I'm starting to work on building xerces under MacOS with Metrowerks Codewarrior.
The MacOS limits filenames to 32 characters. The pathname delimiter on the
Mac HFS filesystem is the colon ":" rather than the unix / or DOS backslash \ .
Xerces is full of #include lines that include the directory
Hi,
I know I still need to get the files to you, but is it possible to get these
into
1.1.0:
- Erik Ulevik's Win32 transcoder that uses the Win32 system API rather than the
standard library widechar functions
He submitted this a while back for 1.0.1, but I modified it to compile under
1.1.0
- Original Message -
From: Laura Neitzel <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, February 24, 2000 10:27 AM
Subject: RE: [Xerces-J] XMLSchemaValidator and errors
> Can I butt in here and ask a simple question? I've just started to use
> Xerces to validate against
Xerces-C 1.1.0 beta 2 (marked ..._d15) binaries and source archives
are available for download from the usual site
http://xml.apache.org/dist
For Windows NT, .zip archives (source and binaries) are posted for
Windows NT 4.0 SP 5 using MSVC 6.0 SP3
For Unix's .tar.gz archives (sources and bin
Done. Thank you again,
rahul
Jeff Mackay wrote:
>
> Now that's what I would call response time! The spec was released on
> 2/25/00, and the implementation is available on 2/26/00? Gee, just 11
> minutes earlier and Xerces could claim same-day conformance...
It depends on the timezone you're talking about... I got an email s
Now that's what I would call response time! The spec was released on
2/25/00, and the implementation is available on 2/26/00? Gee, just 11
minutes earlier and Xerces could claim same-day conformance...
-Original Message-
From: Pierpaolo Fumagalli [mailto:[EMAIL PROTECTED]
Sent: Saturday,
Hallo everyone... I've seen the new spec published today, and found a
very small inconsistence:
on page 21 the method SAXParser.getParser() is declared to throw a
SAXException, but later on, on page 23, that exception is not reflected
into the documentation. I believe the mistake resides on page 2
The "Java API for XML Parsing" version 1.0 is out, and I believe we're
the first ones to support it :)
http://java.sun.com/xml
Pier
PS. Since there's no reference implementation for the current JAXP spec.
-right now- I uploaded my implementation of the javax.xml.parser
package. It's not
Pierpaolo Fumagalli wrote:
>
> yep... you're right, the spec says that that feature should be true by
> default, while on xerces it's false by default... not a big deal, anyway
> :)
Here's the patch...
cvs diff XMLParser.java (in directory C:\CVS
Archive\xml-xerces\java\src\org\apache\xerces\fra
Brett McLaughlin wrote:
>
> The "http://xml.org/features/namespaces"; feature controls general Namespace
> processing: when this feature is true (the default), ...
yep... you're right, the spec says that that feature should be true by
default, while on xerces it's false by default... not a big de
> Brett McLaughlin wrote:
> >
> > I just hopped on the list (I've been offline for a while) so forgive me
in
> > advance if this has been asked and answered (possibly multiple times).
> >
> > I just pulled down the latest distribution of Xerces (1.0.2) and am
seeing
> > some strange behavior from
unsubscribe
Brett McLaughlin wrote:
>
> I just hopped on the list (I've been offline for a while) so forgive me in
> advance if this has been asked and answered (possibly multiple times).
>
> I just pulled down the latest distribution of Xerces (1.0.2) and am seeing
> some strange behavior from startElement(
Yes that is correct.
Thanks,
Jeffrey Rodriguez
IBM Cupertino
XML development
From: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [PATCH] DatatypeValidator
Date: Fri, 25 Feb 2000 18:33:17 -0500
I changed the MAXLENGTH and MINLENGTH constants to
No it is not required. From XML Schema Part 2: Datatypes, I quote:
"A Constraining facet is an optional property that can be applied to a
datatype to constrain its value space. "
length is a Constraining facet.
If you declare length facet then you can constraint or derive a SimpleType
which has
Get it at http://www.megginson.com/SAX/SAX2/
I just hopped on the list (I've been offline for a while) so forgive me in
advance if this has been asked and answered (possibly multiple times).
I just pulled down the latest distribution of Xerces (1.0.2) and am seeing
some strange behavior from startElement() using
org.apache.xerces.parsers.SAX
19 matches
Mail list logo
