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.
entity-encoded XML

entity-encoded XML

2007-02-27       - By rbaxter
Reply:     1     2     3     4     5  


Hi, there may be a simple answer to this but I have not found anything.

I have an XML file that is entity-encoded (see below) which I want to
transform into an HTML file using Xalan.  What would be the best way to make
Xalan read the XML file?

Sample XML file:
http://www.nabble.com/file/6818/SalesReportEncoded.xml
SalesReportEncoded.xml
--
View this message in context: http://www.nabble.com/entity-encoded-XML
-tf3302404.html#a9186221
Sent from the Xalan - J - Users mailing list archive at Nabble.com.


Hi, there may be a simple answer to this but I have not found anything.

I have an XML file that is entity-encoded (see below) which I want to transform
into an HTML file using Xalan.  What would be the best way to make Xalan read
the XML file?

Sample XML file:
<a href="http://www.nabble.com/file/6818/SalesReportEncoded.xml" target="_top"
rel="nofollow">SalesReportEncoded.xml</a>
<br><hr align="left" width="300">
View this message in context: <a href="http://www.nabble.com/entity-encoded-XML
-tf3302404.html#a9186221">entity-encoded XML</a><br>
Sent from the <a href="http://www.nabble.com/Xalan---J---Users-f275.html">Xalan
- J - Users mailing list archive</a> at Nabble.com.<br>