XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
search
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Home » Boards » Stylus Studio Developer Network » Stylus Studio Technical Forum » Built-In Processor Handling CDATA Transforms Differently
Conferences Close Tree View
+ Stylus Studio Feature Requests (1192)
- Stylus Studio Technical Forum (14621)
-> + element type must not contain ... (3)
-> + XML to .txt file (7)
-> + Modifying a XSL-FO report (5)
-> + Retrievning multiple values...... (2)
-> + does Stylus Enterprise work wi... (2)
-> + MSSQL to 837P conversion (4)
-> + Generating XML files accesing ... (6)
-> + How to bold text using XSL (6)
-> + Different heading based on pag... (3)
-> + Code folding (2)
-> + Bad param=value pair on comman... (2)
-> + Saving an XML file (2)
-> + stylus adding random non print... (2)
-> + Displaying Base64Binary as Ima... (6)
-> - probleme de representation d'i... (1)
-> + SS 2008 error message not disp... (8)
-> + XQuery external variable conve... (4)
-> + encodings available (3)
-> + stand-alone application file n... (4)
-> + Windows Installer Dialog Box a... (4)
-> + Block search and replace (2)
-> + Problem with validation (3)
-> + ISA12 vs GS08 (5)
-> + Web Service Call failure... an... (11)
-> + Quotes in xpath query (3)
-> + Java Built-in processor no lon... (6)
-> + Dynamic input and output names (8)
-> + Java built-in parser (3)
-> + Contains an invalid path (2)
-> + Wizard XML Schema to XML (2)
-> + XML to EDI (14)
-> + Computer with original install... (2)
-> + using Custom Tool - passing ar... (3)
-> + Non-printable special characte... (3)
-> + Transfer Options (Settings, Pr... (2)
-> + Enterprise Edition, Rel. 3, Bu... (9)
-> + Need help with xsl file and xm... (2)
-> + Upgrading and retaining settin... (4)
-> + saxon9.dll etc. missing (2)
-> - Error on using XQuery File in ... (1)
-> - Strange Dialog Box (1)
-> + Studio Crashes in schema edito... (3)
-> + Xml to XMl Conversion (2)
-> + Unable to create a complex typ... (2)
-> + Error message wen trying run j... (2)
-> - XSLT Mapper question... (1)
-> + Dcument Wizard XSLT Editor Tab... (2)
-> + Beginner Question - XPath with... (2)
-> + Trying to generate .net code w... (2)
-> + duplicate values in variable w... (5)
-> + Java Runtime Environment libra... (4)
-> + programmatically generate XML ... (4)
-> + Help Loading Oracle BI Publish... (4)
-> + [French] xsl <=> report (3)
-> + XML Diff (3)
-> + StylusStudio 2008, saxon saxon... (6)
-> + Msql Table err:FODC0004 Table ... (2)
-> + The evaluation period for Data... (2)
-> + Mysql to XML (2)
-> + Is there a Collapse All nodes ... (2)
-> + flat file conversion with CDAT... (4)
-> + Struzzo.exe eats up %40 CPU ba... (2)
-> + schematron support? (11)
-> + XML Generator did not generate... (2)
-> + Nesting XML files (2)
-> + Web Service Call fails - targe... (5)
-> + getting not valid for content ... (2)
-> - element modem was referenced i... (1)
-> + xerces-c++ xml parser (2)
-> + movie.dtd (2)
-> + HELP! Stylus Studio 2008 Enter... (3)
-> + Xalan problem with xsl:attribu... (2)
-> + Breakpoints being ignored (12)
-> + Need a new key for Stylus Stud... (2)
-> + Global parameters are not reco... (4)
-> + mySQL DB Connection 2 (10)
-> + Using Data Direct xQuery to ag... (4)
-> + stylusXslt command line -- XSL... (15)
-> + XSLT processor using EXSLT fun... (2)
-> + Integrating Omni Mark (2)
-> + EDI Standards to gXML (2)
-> + flat file conversion (3)
-> + EDI to XML: Invalid URI error (3)
-> + Validating and XML Schema (6)
-> + XSD to DDL (MS-SQL/2005) (6)
-> + xml converter cant encode 0x19 (4)
-> + XSD Help Needed (2)
-> + How do you delete a field in a... (2)
-> + Disable page breaks (3)
-> + XSD semantic structure compari... (3)
-> + Studio Crashes On File Open (7)
-> + Which parser is used by Stylus... (2)
-> + How to DIFF XML windows with d... (3)
-> + Automation using Visual Studio (7)
-> + CSV to XML conversion help (2)
-> + XML tree help (3)
-> + java.lang.NullPointerException... (2)
-> + Creating schema from xml - how... (3)
-> + Mismatch between intellisense ... (4)
-> + Using FOP 0.94 in XML Pipeline (2)
-- Previous [1081-1100] [1101-1120] [1121-1140] Next
+ Website Feedback (249)
+ XSLT Help and Discussion (7625)
+ XQuery Help and Discussion (2017)
+ Stylus Studio FAQs (159)
+ Stylus Studio Code Samples & Utilities (364)
+ Stylus Studio Announcements (113)
Topic  
Postnext
Jamil TaylorSubject: Built-In Processor Handling CDATA Transforms Differently
Author: Jamil Taylor
Date: 01 Dec 2007 11:38 AM
I am using the latest version of Stylus Studio 2007 R2 Enterprise currently available for download. An issue I have just encountered is detailed below:

My XSLT 1.0 transformation outputs to HTML, and my HTML contains a table. When the cells for the table from my source XML are empty, the entire row is collapsed in the table. I do not wish for the table to appear this way, so I used the old HTML trick of adding &nbsp;
Instead of this in my HTML output:

<td></td>

I have this:

<td>&nbsp;</td>

The issue I have encountered is that my HTML appears just the way I expect when using the Built-In XSL processor. The empty table cells contain no text and are not collapsed. If I use any other processor, the table cells contain the text &nbsp;

The portion of my XSL transformation contained within a template is below:

<xsl:for-each select="column">
<td>
<xsl:variable name="value"><xsl:value-of select="translate(self::node(),' ','')"/></xsl:variable>
<xsl:choose>
<xsl:when test="string-length($value)=0"><![CDATA[&nbsp;]]></xsl:when>
<xsl:otherwise><xsl:value-of select="."/></xsl:otherwise>
</xsl:choose>
</td>
</xsl:for-each>
Postnext
Jamil TaylorSubject: Built-In Processor Handling CDATA Transforms Differently
Author: Jamil Taylor
Date: 01 Dec 2007 12:55 PM
More on this--

I have discovered a way to get the desired output in all other processors BUT Built-In. That is to replace the line above to the following:

<xsl:when test="string-length($value)=0">&#160;</xsl:when>

When I use this, all processors except for Built-In now show an empty table row.

Built-In, however, now shows a collapsed table row.

Is this a bug?
Postnext
(Deleted User) Subject: Built-In Processor Handling CDATA Transforms Differently
Author: (Deleted User)
Date: 06 Dec 2007 08:49 AM
Hi Jamil,
yes, it's a bug of the built-in processor; the &nbsp; will appear if there is other non-whitespace text to be printed.

Alberto
Postnext
Jamil TaylorSubject: Built-In Processor Handling CDATA Transforms Differently
Author: Jamil Taylor
Date: 07 Dec 2007 07:34 AM
Originally Posted: 07 Dec 2007 07:31 AM
Thank you for investigating this.

I am not sure what 'Built-in' in the name of the processor actually refers to. Does this mean that your team owns the source code for this processor and is able to correct the issue? I thought I read something about the code being used from another open source project or something.

This is the first issue I have found with the Built-in processor. Now it seems that almost every processor within Stylus Studio has a different problem (there's two more I can try still).
Posttop
(Deleted User) Subject: Built-In Processor Handling CDATA Transforms Differently
Author: (Deleted User)
Date: 11 Dec 2007 06:22 AM
Hi Jamil,
the 'built-in' XSLT processor is a processor we wrote in house; on the other hand, the 'built-in' XML validation processor is the open source Xerces-C++ XML parser.
As for each XSLT processor behaving in different ways... that's the beauty of having multiple processors inside Stylus Studio: so you can test your stylesheet against the specific processor you are going to use when deploying your stylesheet.

Hope this helps,
Alberto
   
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.