Subjects
Home
Xalan extension functions
Fomatting question serializing DOM with pretty print
xalan with pull parser
Cannot find the declaration
Apache Xalan drop support to run on JRE 1 1 x
Why does Doctype change processing of a document
Node set to XML string via Java extensions in Xalan J: possible?
Templates/Transformers + thread safety???
Problem evaluating xpath with muliple prefix with different namespace
remove an arbitrary attribute from xsl output
Xalan3 XSLT 2 0 XPath 2 0 support?
Problem using compiled translets with Xalan !!
Xalan and jstl 1 1 problem with transform tag
NullPointer in DOM2DTM getLocalName
URIResolvers base parameter with xsltc and cascaded imports
Performance problem for Xalan J on intel dual core
Standard libraries in JAXP?
Serializing a DOM tree to XML file, customize entities replacement
Library Conflict Involving BCEL Library
A question on how users are using <xsl:message >
Kevin Cormier as a new Apache Xalan J committer
Struggling to iterate over tokenized string
Xalan count() trouble
Problem with recursive xpath
Error when switching to java 1 5
document( ' ')
Problem with Xalan2 7 0 transformation
cr/lf options
entity encoded XML
can xalan transform 2 xml using one xslt?
Xalan J JIRA defect review Monday October 16, 2006 from 2:00 to 3:30 pm ED
xsl transform with cdata section elements
xslt parameters not expanded
Weird behavior of XPath evaluate()
How to avoid <xsl:message > instruction prints stylesheet file informations ?
Cannot find SimpleTransform subdirectory after installing Xalan J
recover from document not found exceptions
jdk1 5 and Xalan jar differences?
Performance Issue
Error/Bug adding floating point numbers
XPathAPI: eval exp using nodes with default namespace
modifying xalan to output invalid XML
NullPointerException
mege two separate xml nodes into one
Is this a XALAN document identification bug?
is StylesheetRoot really java io Serializable ?
transform() fails for DOMSource but succeeds for StreamSource
Thoughts on Transformer parameter passing
HELP, Xalan and jstl 1 1 problem with transformer
Problem with XPath namespace axis?
string utils:replace deleting search string if replacement string is an HTML
help with enumeration values pls
xalan 2 5 1 vs 2 7 performance question
How to insert/update in XML document
HTML Serialization and Handling of Ampersands in HREF Attributes
XHTML link tag stripping
SystemId Unknown; Line #24; Column #49; java lang NullPointerException
xpath text() help
Apostrophe problem with xalan 2 7 0
How to set variables in XML document?
Links
Home
Oracle database error code ...
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
"mixed mode " XML transformation question

"mixed mode " XML transformation question

2003-01-23       - By Santiago Pericas-Geertsen
Reply:     1     2     3  

Derrick,

Have you tried adding indent="no" to your xsl:output instruction?

-- Santiago

----- Original Message -----
From: "Koes, Derrick" <Derrick.Koes@(protected)>
To: <xalan-j-users@(protected)>
Sent: Thursday, January 23, 2003 4:32 PM
Subject: "mixed mode" XML transformation question


>
> Example XML:
>
> <Body state="draft">The <Variable>6</Variable> foot tall man walked down
> <Variable>5th</Variable> street.</Body>
>
> Transforming the above "mixed mode" XML with the XSL below using
> org.apache.xalan.xslt.Process (Xalan 2.4.1), produces:
>
> <fo:block xmlns:fo="http://www.w3.org/1999/XSL/Format"
> white-space-collapse="false" hyphenation-remain-character-count="2"
> hyphenation-push-character-count="2" hyphenate="true" country="US"
> language="en" font-size="10pt" space-after.optimum="5pt">The <fo:inline
> color="#008080" font-style="italic" font-weight="bold">6</fo:inline> foot
> tall man walked down <fo:inline color="#008080" font-style="italic"
> font-weight="bold">5th</fo:inline> street.</fo:block>
>
> However, using either of the transformer factories
> (org.apache.xalan.xsltc.trax.TransformerFactoryImpl,
> org.apache.xalan.processor.TransformerFactoryImpl) embedded in my
> application to create a transformer produces a new line and tab
immediately
> before the <fo:inline> output elements.
> I need to understand why this is happening because it is highly
> undesireable.  Can anyone tell me if something is configured improperly,
or
> what is causing this?
>
> Thanks for the help.
>
>
> <?xml version="1.0" encoding="UTF-8"?>
> <xsl:stylesheet version="1.0"
> xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
>
> xmlns:fo="http://www.w3.org/1999/XSL/Format">
>   <xsl:output method="html" encoding="UTF-8"/>
>
>   <xsl:attribute-set name="variable">
>     <!--xsl:attribute name="background-color">#008080</xsl:attribute-->
>     <xsl:attribute name="color">#008080</xsl:attribute>
>     <xsl:attribute name="font-style">italic</xsl:attribute>
>     <xsl:attribute name="font-weight">bold</xsl:attribute>
>   </xsl:attribute-set>
>
>   <xsl:template match="Body">
>      <xsl:variable name="state" select="@(protected)"/>
>       <fo:block
>           space-after.optimum="5pt"
>           font-size="10pt"
>           language="en"
>           country="US"
>           hyphenate="true"
>           hyphenation-push-character-count="2"
>           hyphenation-remain-character-count="2"
>           white-space-collapse="false">
>         <xsl:call-template name="substitute">
>           <xsl:with-param name="state" select="$state"/>
>         </xsl:call-template>
>       </fo:block>
>   </xsl:template>
>
>   <xsl:template name="substitute">
>     <xsl:param name="state"/>
>     <xsl:apply-templates>
>       <xsl:with-param name="state" select="$state"/>
>     </xsl:apply-templates>
>   </xsl:template>
>
>   <xsl:template match="Variable">
>     <xsl:param name="state"/>
>     <xsl:choose>
>       <xsl:when test="$state = 'final'">
>         <xsl:value-of select="."/>
>       </xsl:when>
>       <xsl:otherwise>
>         <fo:inline xsl:use-attribute-sets="variable"><xsl:value-of
> select="."/></fo:inline>
>       </xsl:otherwise>
>     </xsl:choose>
>   </xsl:template>
>
> </xsl:stylesheet>
>
>
> This electronic transmission is strictly confidential to Smith & Nephew
and
> intended solely for the addressee.  It may contain information which is
> covered by legal, professional or other privilege.  If you are not the
> intended addressee, or someone authorized by the intended addressee to
> receive transmissions on behalf of the addressee, you must not retain,
> disclose in any form, copy or take any action in reliance on this
> transmission.  If you have received this transmission in error, please
> notify the sender as soon as possible and destroy this message.
>
>
>