This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: Xalan Encoding Problems - RETRACTION
- To: <xsl-list at lists dot mulberrytech dot com>
- Subject: Re: [xsl] Xalan Encoding Problems - RETRACTION
- From: Jörg Heinicke <joerg dot heinicke at gmx dot de>
- Date: Wed, 31 Oct 2001 12:01:51 +0100
- References: <F136CkWHZqYW8BYXifW0000038a@hotmail.com>
- Reply-To: xsl-list at lists dot mulberrytech dot com
> I'm not sure hot to interpret what you are saying but does this mean with
> these two fixes, it works?
>
> BTW, check out bug #1639 which is about Xalan escaping characters for ISO
> encodings.
No, it's not a problem with the encoding. Xerces is completely working for
me, also in the current version 1.4.3.
But there is a bug in Xalan. It mixes the values of the params $code-type
and $height in the template 'barcode-EAN-cleaned' line 213 when calling the
template 'draw-barcode-EAN' in line 256.
<xsl:call-template name="draw-barcode-EAN">
<!-- many with-param's -->
...
<!-- the first with inner call-template (line 271): still correct value
of $code-type -->
<xsl:with-param name="bar-and-space-widths">
<xsl:call-template name="get-bar-space-width">
<xsl:with-param name="value" select="$value"/>
<xsl:with-param name="code-type" select="$code-type"/>
</xsl:call-template>
</xsl:with-param>
<!-- the second with inner call-template (line 279): incorrect value of
$code-type -->
<!-- it has the value of $height now -->
<xsl:with-param name="bar-heights">
<xsl:call-template name="get-bar-height">
<xsl:with-param name="code-type" select="$code-type"/>
</xsl:call-template>
</xsl:with-param>
<!-- more with-params with inner call-template, all with wrong
$code-type -->
</xsl:call-template>
Because of this wrong value of $code-type in the template 'get-bar-height'
(line 549) nothing matches there. Only the values 'EAN13', 'UPC-A', 'EAN-8'
and 'UPC-E' are possible as you can see, but not '70'. You can add an
<xsl:otherwise> below the 4 <xsl:when>. For example
<xsl:otherwise>||.....</xsl:otherwise>. So you will get a 'half' barcode.
The 2 things in bartest-FO.xsl are completely different. FOP doesn't work
with the wrong XSL-FO namespace and Xalan doesn't work with <xsl:import>,
but <xsl:include>, what I do not understand.
Regards,
Joerg
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list