Norman Walsh wrote:
/ Eric Richardson [EMAIL PROTECTED] was heard to say:
| catalogs=$SHARE/doctypes/catalog
| catalogs=%SHARE%/doctypes/catalog
| catalogs=catalog
|
| Norm,
|
| I can't say I like this all that much as well. I currently using the
| old xmlcatalog code. The -D
Bradford, Denis wrote:
As noted recently, I've got the Sun resolver classes working, but
not sure it's set up optimally. Is there some way to avoid hard
coding full catalog pathnames in the CatalogManager.properties file?
All the specs I've sifted through indicate a full pathname - sure
/ Bradford, Denis [EMAIL PROTECTED] was heard to say:
| Thanks Eric - the classpath bites again! Now I'm getting a
| FileNotFoundException on the system ID in my source's DTD declaration:
|
| D:\xdm1\htmlhelpjava com.icl.saxon.StyleSheet -r
| com.sun.resolver.tools.CatalogResolver
/ Bradford, Denis [EMAIL PROTECTED] was heard to say:
| Trying to set up a catalog, I'm getting the following error with Saxon:
|
| java com.icl.saxon.StyleSheet -r com.sun.resolver.tools.CatalogResolver
| ..\xmldiffmrg.xml c:\docbookxsl\htmlhelp\xdm-htmlhelp.xsl
| Cannot find
Bradford, Denis wrote:
Trying to set up a catalog, I'm getting the following error with Saxon:
java com.icl.saxon.StyleSheet -r com.sun.resolver.tools.CatalogResolver
..\xmldiffmrg.xml c:\docbookxsl\htmlhelp\xdm-htmlhelp.xsl
Cannot find CatalogManager.properties
Cannot find
/ David Brownell [EMAIL PROTECTED] was heard to say:
| http://lists.oasis-open.org/archives/docbook-apps/200108/msg00148.html
|
| [ I don't know if docbook-apps will bounce this or not, I'm not subscribed
| and only found out about those classes through a roundabout channel ...
| if it bounces,
http://lists.oasis-open.org/archives/docbook-apps/200108/msg00148.html
[ I don't know if docbook-apps will bounce this or not, I'm not subscribed
and only found out about those classes through a roundabout channel ...
if it bounces, would you please forward this to the list? ]
If you're using
Hello
/ David Brownell [EMAIL PROTECTED] was heard to say:
| If the current AElfred software doesn't do this right, I want to know.
I don't know if the AElfred that's distributed with Saxon is either
current or unmodified. The version that comes with Saxon is the only
one that I've
/ Eric Richardson [EMAIL PROTECTED] was heard to say:
| If you don't provide a CatalogManager.properties then the following
| occurs and it just hangs.
|
| html:
| [echo] Transforming: example.xml
| [echo] Into:
|
Norm,
Briefly, what additional functionality do the sun resolver classes add
to the arbortext classes you released last April (and Zirka's Saxon
extension)?
Here're my guesses:
- support for OASIS XML Catalogs
- easier hooks for Xalan
- direct support for XP, independent of XT
What have I
/ Mark Johnson [EMAIL PROTECTED] was heard to say:
| Briefly, what additional functionality do the sun resolver classes add
| to the arbortext classes you released last April (and Zirka's Saxon
| extension)?
|
| Here're my guesses:
|
| - support for OASIS XML Catalogs
| - easier hooks for Xalan
Thanks Norm,
That's great on the future license - hope that happens soon.
Eric
Norman Walsh wrote:
/ Eric Richardson [EMAIL PROTECTED] was heard to say:
| Norman Walsh wrote:
|
| I'm pleased to announce that the set of Java classes that I wrote to
| implement the OASIS XML Catalogs
On Thu, Aug 16, 2001 at 08:42:18AM -0700, Eric Richardson wrote:
Thanks Norm,
That's great on the future license - hope that happens soon.
Hum, that reminds me I never finished my own implementation ...
Hello BTW, I just joined the docbook lists.
Daniel
--
Daniel Veillard | Red Hat
Norman Walsh wrote:
I'm pleased to announce that the set of Java classes that I wrote to
implement the OASIS XML Catalogs Committee Specification[1] for SAX
entityResolver() and JAXP URIResolver()s have been released[2].
Hi Norm,
In my docbook system, I use ant to call the parsers etc.
If you're using Saxon with these classes, beware of the following
problem: AElfred, Saxon's default XML parser, has a serious bug in
recent Saxon releases; it calculates the base URI of external entities
incorrectly.
To avoid this problem, I suggest that you use Xerces or any other JAXP
Norman Walsh wrote:
I'm pleased to announce that the set of Java classes that I wrote to
implement the OASIS XML Catalogs Committee Specification[1] for SAX
entityResolver() and JAXP URIResolver()s have been released[2].
How does this relate to the Arbortext catalog resolver code?
What's
I'm pleased to announce that the set of Java classes that I wrote to
implement the OASIS XML Catalogs Committee Specification[1] for SAX
entityResolver() and JAXP URIResolver()s have been released[2].
Be seeing you,
17 matches
Mail list logo
