[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Xalan Encoding Problems - RETRACTION

Subject: Re: Xalan Encoding Problems - RETRACTION
From: Jörg Heinicke <joerg.heinicke@xxxxxx>
Date: Wed, 31 Oct 2001 02:12:18 +0100
xalan force iso 8859 1
Hello Raul,

sorry, but I must disappoint you, but it's working for me with the current
Xerces version 1.4.3

But then ... I get only one vertical line too. I tested and searched and
tested and searched the stylesheets. At the end I can say, there is a bug in
Xalan. It's in the file barcode-EAN-logic.xsl. The value of $code-type (e.g.
'EAN-13') gets lost from the line 280 to the line 550. The value in my
testcase was '70' and not more 'EAN-13'. But that's the value of
$real-height in line 161 ('EAN-13' uses the value of <xsl:otherwise> at this
point). Changing it gives a new value to $code-type.

These are the template calling code-snippets:

<xsl:call-template name="......">

    <!-- Get the bar/space width pattern -->
    <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>

    <!-- Get the bar height pattern -->
    <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>

</xsl:call-template>

In the first template the $code-type 'arrives' correctly, in the second one
it has the new value. More curios: Replacing the 2 <xsl:call-templates> by
each other shows, that still the first called template gets the correct
value, the second one not.

Because of this bug you are constrained to use another transformer than
Xalan. I will post this bug at Apache bugserver.

Joerg

----- Original Message -----
From: "Raul Rodriguez" <raulnyc@xxxxxxxxxxx>
To: <xsl-list@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Tuesday, October 30, 2001 10:06 PM
Subject: Re:  Xalan Encoding Problems - RETRACTION


>
> OK, I need to retract what I last posted:  it looks like using an older
> Xerces does NOT TOTALLY work.
>
> Here is what I am doing:
>
> I am using Xalan to transform an XML document into an FO object.  I am
> importing a stylesheet that is encoded in ISO-8859-1, which I got from
> http://www.renderx.com and allows me to add a barcode to my FO object.  I
> then use RenderX XEP renderer to render the FO document into PDF.
>
> When I use the latest Xerces JAR file, Xalan dies complaining that it
cannot
> process ISO-8859-1 encoding.  I reverted to an older version of Xerces and
> it worked fine.  However, rendering my FO using RenderX show a barcode
that
> looked horrible.  All of the vertical lines, except one, was missing.
>
> Using the lastest version of Saxon worked perfectly and it looks like I am
> force to abandon Xalan for the time being.
>
> If you wish to test this yourself, download the sample XSL and XML files
at
> http://www.renderx.com/barcodes.html and prove that I am crazy.
>
> Thanks
>
> Raul Rodriguez
> New York City



 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


Current Thread

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.