XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Show tree view Topic
Topic Page 1 2 3 4 5 6 7 8 9 Go to previous topicPrev TopicGo to next topicNext Topic
Postnext
Elliot PerezSubject: StylusStudio - pick XSLT 1.0 but it still writes XSLT 2.0
Author: Elliot Perez
Date: 16 Mar 2010 05:09 PM
My end game is to create a stylized report, export the XSLT to be used with FO PDF conversion. (please excuse me - im a newbie to all of this). From a collegues research, it seems that even though I choose to export in version 1.0, it writes it in 2.0. Problem is the .NET Xml convertor to FO - PDF maker will only accept version 1.0.

Anyone have any insight/exceptions?

Thanks for any help (in advance)

Postnext
Ivan PedruzziSubject: StylusStudio - pick XSLT 1.0 but it still writes XSLT 2.0
Author: Ivan Pedruzzi
Date: 16 Mar 2010 05:27 PM
Elliot,

If you are referring to XML Publisher (File -> New -> XML Report) you should be able pick the XSLT version every time you are running the code generator. If you pick XSLT 1.0 the transformation should be compatible with the .NET built-in XSLT processor.

Hope this helps
Ivan Pedruzzi
Stylus Studio Team

Postnext
Elliot PerezSubject: StylusStudio - pick XSLT 1.0 but it still writes XSLT 2.0
Author: Elliot Perez
Date: 17 Mar 2010 09:29 AM
Originally Posted: 17 Mar 2010 09:24 AM
It seems once I "generate" the XSLT using Transformation language, into XSLT-FO, "according to one of the developers here who knows tons more than I do", it still puts in attributes that our F)-PDF generator can't handle.

eg. column-width=15%
(i have to change it to)
column-width="proportional-column-width(15%)

It also doesn't like scale-to-fit ( i have top remove that attribute and make sure that the image I placed it an exact size. Issues like this my developer told me are XSLT-FO ver 2.0, but out FO-PDF generator cant handle them so I have to then go back in and remove from the newly generated XSLT.

Any insight?

Postnext
Elliot PerezSubject: StylusStudio - pick XSLT 1.0 but it still writes XSLT 2.0
Author: Elliot Perez
Date: 17 Mar 2010 10:04 AM
To clarify my previous post,

I am trying to creste a grid with alternate background colors for even and odd rows of dynamically results. I am setting the properties of the row a follows:
Background: <dynamic>
Context: $WorkInfoRow
XPath: if(position() mod 2 = 1) then "white" else "lightsteelblue"
(all these attributes are being done within Stylus Studio Report Designer)

Now I am trying to generate the XSLT using :
Report>Generate> (selecting Transformation Language : XSLT 1.0)
Unfortunately, the generated XSLT is compliant with XSLT 2.0/XPath 2.0 which allows inline “if” statements”
(eg. of generated XSLT)
<fo:table-row background-color="{if(position() mod 2 = 1) then &quot;white&quot; else &quot;lightsteelblue&quot;}">
Because of such behavior, I have to manually go to the XSLT and change it to make it compliant with the XSLT 1.0.
(eg.
<xsl:variable name="ColorW">
<xsl:choose>
<xsl:when test="position() mod 2 = 0">white</xsl:when>
<xsl:otherwise>lightsteelblue</xsl:otherwise>
</xsl:choose>
</xsl:variable>
<tr bgcolor="{$ColorW}">
<fo:table-row background-color="{$ColorW}">

Now every time I make a change to the report, I have to regenerate the XSLT, and make this manual change converting to XSLT 1.0.

Please advise.
Thank You.

Postnext
Yitzhak KhabinskySubject: StylusStudio - pick XSLT 1.0 but it still writes XSLT 2.0
Author: Yitzhak Khabinsky
Date: 12 Apr 2010 09:10 AM
I am experiencing the same issue like Elliot.

Stylus Studio 2010 (build 1540b) Report Designer generates XSLT 2.0/XPath 2.0 inline “if” statements even upon selection XSLT 1.0 in the Report>Generate> (selecting Transformation Language : XSLT 1.0).

Please take a look into this issue.
It seems like a bug.

Regards,
Yitzhak

Posttop
Alberto MassariSubject: StylusStudio - pick XSLT 1.0 but it still writes XSLT 2.0
Author: Alberto Massari
Date: 21 Apr 2010 12:12 PM
Hi Eliot,
XML Report can control the generated code only in the parts controlled by the GUI designer; in your case, the XPath containing the if() statement is entered by the user, and is maintained as is in the generated stylesheet.

Hope this helps,
Alberto

 
Topic Page 1 2 3 4 5 6 7 8 9 Go to previous topicPrev TopicGo to next topicNext Topic
Download A Free Trial of Stylus Studio 6 XML Professional Edition Today! Powered by Stylus Studio, the world's leading XML IDE for XML, XSLT, XQuery, XML Schema, DTD, XPath, WSDL, XHTML, SQL/XML, and XML Mapping!  
go

Log In Options

Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2016 All Rights Reserved.