Well, yeah -- except as I said in my original post, I can't stick with
what we've been using due to the objections of our IT department who do
not want JVM installed, and JVM appears to be a prerequisite for running
I've asked our IT guy to look at the documentation for 6.5.5 and if it
passes muster with them we'll use that one and yeah, problem will be
solved. But I'd still like to know where the weirdness with v.18.104.22.168
is coming from. I hate to leave a puzzle unsolved, I'm just that kind
of person :)
From: Encoded Archival Description List [mailto:[log in to unmask]] On Behalf
Of Mark Carlson
Sent: Monday, October 13, 2008 2:10 PM
To: [log in to unmask]
Subject: Re: EAD to HTML, Saxon, and meta tags
I was suggesting 6.5.5 because you are using a version 1.0 stylesheet,
so there is no real benefit to using Saxon 8+. So if the later version
is causing a problem and the earlier one isn't then stick with the
earlier version - problem solved.
Michele R Combs wrote:
> Hi Mike --
> I downloaded and tried 6.5.5 as well and yep, it works fine with that
> one too. Were you suggesting 6.5.5 because it doesn't need the JVM?
> read the documentation section for 6.5.5 on Java prerequisites but I'm
> not by any stretch a java programmer so it was pretty much all Greek
> me, but if that's the case then that would indeed solve my problem and
> make my IT people happy!
> -----Original Message-----
> From: Encoded Archival Description List [mailto:[log in to unmask]] On Behalf
> Of Mark Carlson
> Sent: Friday, October 10, 2008 6:21 PM
> To: [log in to unmask]
> Subject: Re: EAD to HTML, Saxon, and meta tags
> You could try parsing it with an earlier version of Saxon, like 6.5.5
> see if that will work for you.