I am new to this mailing list (and new to Saxon), so forgive me if this
question has already been answered, but I didn't find an FAQ and Google
turned up nothing.
I am attempting to use Saxon through the TraX interface, and the
transformation works, but I always get an error message before the
transformation that says "Failed to load ISO8859_1".
Any clues to what the problem might be? As far as I know I am not
specifying ISO8859_1 anywhere. It prints out this message regardless of
the output encoding of the stylesheet.
If I run the same transformation using the Saxon command line interface,
I do not get the message.
I am using Saxon 6.5 with JDK 1.2.2 on Linux.
Thanks,
Chris
--
Chris P. McCabe - Senior Software Systems Architect
Choice Hotels International - Information Technology
chris_mccabe@... 602-953-4416

When I use the EXSLT date-time function as implemented in SAXON, the
time returned appears to be a local time, but it is returned with a
trailing 'Z' indicating UTC time.
It seems to me that either the time value returned should be UTC time
and contain the suffix 'Z' (preferred), or the time value returned
should be local time and contain a suffix representing the offset from
UTC time of the form '-05:00'. (I'm in the U.S. eastern time zone and so
am 5 hours behind UTC).
Am I misunderstanding something basic, or is this behavior of the
date-time function in SAXON incorrect?
-- Details follow --------------------
I'm running SAXON 6.5 using Java 1.3.1 on Windows 2000.
I've checked to make sure my system's clock and time zone (GMT-05:00
Eastern Time) settings are correct.
The following XSLT is my test case:
<xsl:stylesheet
version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform";
xmlns:date="http://exslt.org/dates-and-times";
extension-element-prefixes="date"
>
<xsl:output method="xml" omit-xml-declaration="yes"/>
<xsl:template match="/">
<dateTime><xsl:value-of select="date:date-time()"/></dateTime>
</xsl:template>
</xsl:stylesheet>
When I processed this stylesheet with SAXON 6.5 at 1:44 P.M. today
(eastern standard time), it resulted in:
<dateTime>2002-01-23T13:44:49Z</dateTime>
But I expected either:
<dateTime>2002-01-23T18:44:49Z</dateTime>
or
<dateTime>2002-01-23T13:44:49-05:00</dateTime>
or
<dateTime>2002-01-23T13:44:49</dateTime>
Pete
--------
Pete Beazley mailto:pete@...
ClearlyOnline, Inc. http://www.clearlyonline.com
XML and XSLT Training & Consulting
1-724-942-1912
1-724-941-3698 fax

No, sorry, there is no way to achieve this in XSLT 1.0 (I find it
frustrating too!)
The circumvention I have used is to edit the file before transformation to
replace all "&" characters by something like "###", and then edit them back
at the end; you also need to reinsert the internal DTD subset into the
result document at the end.
There's a possible solution to the problem (or you might describe it as a
workaround) in Appendix F (IIRC) of the XSLT 2.0 WD, and I hope I might get
round to implementing that in Saxon some day.
Mike Kay
-----Original Message-----
From: saxon-help-admin@...
[mailto:saxon-help-admin@...]On Behalf Of Thom Kuhn
Sent: 22 January 2002 16:35
To: saxon-help@...
Subject: [saxon] Entity references
I wish to go from XML to XML using the same DTD. The point is to make some
minor structural changes throughout a set of documents. Everything works
fine except that the named entity references get converted. We use ISO names
for all characters above 128, and want them to stick in the output file. The
entity references for characters between 128 and 255 get converted to the
actual character, and those above 255 get converted to numeric entities. I
realize that this is correct behavior according to the specification. I
examined the Saxon extensions, but I couldn't find anything that helps if
the output is XML. I hope that I am missing something here. Is there any way
to suppress all entity reference conversions?
Thanks,
Thom
Thomson Kuhn
ACP-ASIM

>I wish to go from XML to XML using the same DTD. The point is to make some
>minor structural changes throughout a set of documents. Everything works
>fine except that the named entity references get converted. We use ISO
>names for all characters above 128, and want them to stick in the output
>file. The entity references for characters between 128 and 255 get
>converted to the actual character, and those above 255 get converted to
>numeric entities. I realize that this is correct behavior according to the
>specification. I examined the Saxon extensions, but I couldn't find
>anything that helps if the output is XML. I hope that I am missing
>something here. Is there any way to suppress all entity reference
>conversions?
The saxon:character-representation attribute on the xsl:output element
allows explicit control of how SAXON translates non-ascii characters in
the output stream.
The default is "entity;decimal" which should produce exactly what you
nee.idea, why this is not the case. Maybe this is only the default in
HTML mode?
Tim
---
If organized religion is the opium of the masses then
disorganized religion is the marijuana of the lunatic fringe.
---
Tim Pritlove, Discordian Evangelist, <tim@...>
PGP Fingerprint: 0588 53A1 B0EF 0C43 B6F9 A7A7 0777 36CD