[ 
https://issues.apache.org/jira/browse/XALANJ-2642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mukul Gandhi reassigned XALANJ-2642:
------------------------------------

    Fix Version/s: xslt3.0_alpha1
         Assignee: Mukul Gandhi  (was: Gary D. Gregory)

> with html xsl:output method, and default html namespace present on the xslt 
> stylesheet, certain html like tags within the input xml are not being 
> generated with xml syntax on the xslt transformation result
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: XALANJ-2642
>                 URL: https://issues.apache.org/jira/browse/XALANJ-2642
>             Project: XalanJ2
>          Issue Type: Bug
>      Security Level: No security risk; visible to anyone(Ordinary problems in 
> Xalan projects.  Anybody can view the issue.) 
>          Components: Serialization, XSLTC
>    Affects Versions: The Latest Development Code, 2.7.1, 2.7.2
>            Reporter: Mukul Gandhi
>            Assignee: Mukul Gandhi
>            Priority: Major
>             Fix For: xslt3.0_alpha1
>
>
> This XalanJ bug is, reflected with the conf.xsltc test case output63.
> Following is the purpose, of this test case, as mentioned within this test 
> case's XSLT transformation stylesheet,
> "The html output method should not output an element differently from the xml 
> output method unless the expanded-name of the element has a null namespace 
> URI; an element whose expanded-name has a non-null namespace URI should be 
> output as XML. So the html tags <p>, <hr> and <br> in this case, due to the 
> default html namespace will be output as xml not html".
> Following is the relevant section, about these XSLT 1.0 specification details 
> : https://www.w3.org/TR/1999/REC-xslt-19991116#section-HTML-Output-Method.
> This bug is present on the XalanJ xsltc processor, but XalanJ interpretive 
> processor doesn't have this bug.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to