FM 10: DITA to XHTML transformation?

Is there any way to transform/publish a DITA XML file to an XHTML file from within Framemaker?

Here are some options (it depends on what you mean by "from within FrameMaker").
You could create a structured application that converts a ditamap and topic files into a set of XHTML files .. but that would be a lot of work.
You could use RoboHelp, which allows you to import files from FM and export various forms of HTML.
You could install the DITA Open Toolkit connectors for FM8 or FM9 ..
     http://www.adobe.com/devnet/framemaker/fm8_opentoolkit.html
     http://www.adobe.com/devnet/framemaker/fm9_opentoolkit.html
You could use DITA2Go (a free tool from Omsys) ..
     http://www.dita2go.com/
Or you could install DITA-FMx, which among other things also provides a connector to the DITA-OT ..
     http://leximation.com/dita-fmx/
Cheers,
...scott
Scott Prentice
Leximation, Inc.
www.leximation.com

Similar Messages

Transforming XHTML to HTML

Hi all!
Here's the deal: I'm trying to transform an XHTML document to HTML using XSLT and the Tranformers in the JAXP. So far, I can get documents that are entirely text (w/ no HTML tags at all) or documents that have tags but no text! Basically, all I need to do is strip the xml declaration from the top of the document and replace
tags with <br> tags (get rid of the trailing slash). Any suggestions on the correct XSL templates to use? Is there a simpler way of doing this than using XSLT?
Regards,
V.

You basically want to do an identity transform (outputs what was input), but specify that you want the output formatted as html. I did a quick search for identity stylesheet and this is what I found (untested):
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform";>
<xsl:template match="node()|@*">
     <xsl:copy>
          <xsl:apply-templates select="node()|@*"/>
     </xsl:copy>
</xsl:template>
</xsl:stylesheet>
My xsl skills are fuzzy, so we'll just assume it works and let you test it. You also want to include the following rule, which generates html style tags and leaves out the xml declaration:
<xsl:output method="html"/>
As to whether this is the easiest way to do what you want, I really don't know. Maybe DOM or JDom have an output writer which can use html style, or maybe it's not that difficult to write your own.

J'ai converti un pdf en word...ok le site me dit ok document telecharrge sur votre compte..je vais sur mon compte...et il n'y a aucun document word...qu eles pdf que j'ai chargés pour transformer...où se trouve mon .doc???

j'ai converti un pdf en word...ok le site me dit ok document telecharrge sur votre compte..je vais sur mon compte...et il n'y a aucun document word...qu eles pdf que j'ai chargés pour transformer...où se trouve mon .doc???

Hi jean paule92317484,
Please clear the browser cache, and then log in to https://cloud.acrobat.com/files. Do you see your converted file in either the Acrobat.com Files or Recent Files list?
When you use the ExportPDF service--either via the web interface or through Adobe Reader--your files are automatically stored in your online account.
Best,
Sara

Stumped: Why won't DITA-OT process my Frame 9 map file?

I'm stuck and hope someone might provide some guidance. I'm running Frame 9 on Windows XP.
I've created a very simple map file and am trying to get it to process in the DITA OT.
Everything appears to be set up correctly (I specify which Dita map is to be transformed...
etc.), but when I click Transform, I get the following error message:
"WinANT Build Error
It appears the build process failed. Either no log file was produced or the log file stylesheet
was not generated into the output directory.This means the process didn't complete correctly."
It then tells me:
-To be sure I have the Java JDK installed. (I do.)
-Check that the Dita OT dir on the DITA tab is pointing to the correct
location of the DITA toolkit. (It is.)
-To deselect the Overrides on the advanced tabs ( I did.)
-Tweak the fix resolver checkbox on the DITA OT tab (I tried.)
Sigh.....nothing seems to work.
Just wondered if anyone might a clue as to what's going on.
Many thanks in advance,
Gary

Hi Gary...
Note that you don't "import" files into the DITA-OT. The OT is a tool for generating output from DITA files .. you use it to create various types of deliverables from DITA files.
Yes .. the FrameMaker DITA-OT connector plugin does seem to have fallen off the web .. I've asked around, but no one will fess up to where it's gone. I may make a plugin for this purpose .. it's very nice to have this built into Frame. You might want to look into using the DITA-FMx plugin, which provides many additional DITA authoring and publishing features as well as an OT connector. You can download the DITA-FMx trial from my website ..
http://leximation.com/dita-fmx/
It is possible that WinANT doesn't like FM9 DITA files, but I'm thinking that's not the case. You should try building (generating) output from the DITA samples provided in the DITA-OT using WinANT .. that will determine if the problem lies in your WinANT installation or with the FM9 DITA files.
BTW .. the command line isn't all that hard to use. Just locate the DITA-OT folder .. it should contain a file named "startcmd.bat" .. run that file to get the shell from which to run the commands. Once the DOS shell opens up, you can enter the following to create XHTML output from your map file ..
java -jar lib/dost.jar /i:C:/PATH/MAP.DITAMAP /outdir:C:/PATH/OUT /transtype:xhtml
Where "C:/PATH/MAP.DITAMAP" is the path and filename of your ditamap file, and "C:/PATH/OUT" is the path and folder where you want the output created.
In theory, this should all work .. but as you might expect there are reasons that it may not.
Cheers,
...scott

XSL transformation not working

Hi!
I am having problems when trying to generate XSL transformation from XML to XML (where XML output is actually XHTML). It always fails executing <xsl:callTemplate name="something", when <xsl:callTemplate /> is executed from another <xsl:template> which is also called with <xsl:callTemplate. Version of database is 10.2.0.4.0, received error is: ORA-00604: invalid character value 'burek' for attribute 'name'.
Transformation is working in Java and Altova XMLSpy.
PL/SQL code:
procedure process_xsl(p_xml in clob, p_xsl in clob, p_result out clob) is
w_xsl_proc dbms_XSLProcessor.Processor;
w_xsl_ss dbms_XSLProcessor.Stylesheet;
w_dom_xsl dbms_xmldom.DOMDocument;
w_dom_xml dbms_xmldom.DOMDocument;
w_parser dbms_xmlparser.Parser;
begin
--xml in xsl iz cloba v DOMDocument
w_parser := dbms_xmlparser.newParser;
dbms_xmlparser.parseClob(w_parser, p_xml);
w_dom_xml := dbms_xmlparser.getDocument(w_parser);
dbms_xmlparser.freeParser(w_parser);
w_parser := dbms_xmlparser.newParser;
dbms_xmlparser.parseClob(w_parser, p_xsl);
w_dom_xsl := dbms_xmlparser.getDocument(w_parser);
dbms_xmlparser.freeParser(w_parser);
--xsl procesiranje
w_xsl_proc := dbms_XSLProcessor.newProcessor;
w_xsl_ss := dbms_XSLProcessor.newStylesheet(w_dom_xsl, null); <-- Here error is received
END;
Stylesheet:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
     <xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes" doctype-public="-//W3C//DTD XHTML 1.0 Transitional//EN" doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"></xsl:output>
     <xsl:decimal-format name="dec" decimal-separator="," grouping-separator="."/>
     
     <xsl:variable name="einvoiceIssuerCode" select="'II'"></xsl:variable>
     <xsl:variable name="einvoiceRecipientCode" select="'IV'"></xsl:variable>
     <xsl:variable name="einvoiceIssueLocationCode" select="91"></xsl:variable>
     <xsl:variable name="einvoiceIssueDateCode" select="137"></xsl:variable>
     
     <xsl:variable name="einvoiceNumber" select="/IzdaniRacunEnostavni/Racun/GlavaRacuna/StevilkaRacuna/text()"></xsl:variable>
     
     *<xsl:template name="burek"> *
          <xsl:text>TEST</xsl:text>
     </xsl:template>
     
     <xsl:template name="einvoice">
          <html xmlns="http://www.w3.org/1999/xhtml">
          <head>
               <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
               <title>Vizualizacija e-računa št. </title>
               <xsl:call-template name="burek"></xsl:call-template>
          </head>
          <body>
          </body>
          </html>
     </xsl:template>
     
     <xsl:template match="/">
*          <xsl:call-template name="einvoice"></xsl:call-template> *
     </xsl:template>
</xsl:stylesheet>
XML document
<?xml version="1.0" encoding="UTF-8"?>
<IzdaniRacunEnostavni>
<Racun Id="data">
<GlavaRacuna>
<VrstaRacuna>380</VrstaRacuna>
<StevilkaRacuna>1205019908211</StevilkaRacuna>
<FunkcijaRacuna>9</FunkcijaRacuna>
</GlavaRacuna>
<DatumiRacuna>
<VrstaDatuma>137</VrstaDatuma>
<DatumRacuna>2012-05-07T00:00:00.0Z</DatumRacuna>
</DatumiRacuna>
<DatumiRacuna>
<VrstaDatuma>263</VrstaDatuma>
<DatumRacuna>2012-04-28T00:00:00.0Z</DatumRacuna>
</DatumiRacuna>
<DatumiRacuna>
<VrstaDatuma>263</VrstaDatuma>
<DatumRacuna>2012-05-27T00:00:00.0Z</DatumRacuna>
</DatumiRacuna>
<DatumiRacuna>
<VrstaDatuma>263</VrstaDatuma>
<DatumRacuna>2012-03-28T00:00:00.0Z</DatumRacuna>
</DatumiRacuna>
<DatumiRacuna>
<VrstaDatuma>263</VrstaDatuma>
<DatumRacuna>2012-04-26T00:00:00.0Z</DatumRacuna>
</DatumiRacuna>
<DatumiRacuna>
<VrstaDatuma>263</VrstaDatuma>
<DatumRacuna>2012-04-27T00:00:00.0Z</DatumRacuna>
</DatumiRacuna>
<Lokacije>
<VrstaLokacije>91</VrstaLokacije>
<NazivLokacije>Ljubljana</NazivLokacije>
</Lokacije>
</Racun>
</IzdaniRacunEnostavni>
Edited by: 938026 on 01-Jun-2012 00:35

Hi,
I think your problem lies in the <title>. You are using non UTF-8 characters in the title (š), but you marked your XML as UTF-8. So change the title to have unicode charaters and it will work.
Herald ten Dam
http://htendam.wordpress.com

XSLT one XML to multiple linked XHTML files

I want to generate linked XHTML documents based on a data XML file. But it seems that the XSLT implementation of ABAP does not support to create multiple files in one XSL-Transformation (like in XSLT 2.0 or the saxon XSLT enhancements).
Fist question: Am I right :)?
Second question: If yes, what can I do to solve my problem? Starting a transformation for every document would probably end in some serious performance issues.
Thank you in advance.
Tobias Neef

Hi Shantha,
You can do this senario with BPM...............In BPM you need to split messages based on the Order number so that files will be recevied based in the order number ........To do this you need to create a correlation in BPM (Correlation based on Order number which is unique for every order) .by doing u can achive the mutiple receviers
Below mentioned blogs can help doing this senario
BPM-1
/people/krishna.moorthyp/blog/2005/06/09/walkthrough-with-bpm
BPM-2
/people/krishna.moorthyp/blog/2006/04/08/reconciliation-of-messages-in-bpm
BPM-3
/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
BPM-4
/people/michal.krawczyk2/blog/2005/06/11/xi-how-to-retrieve-messageid-from-a-bpm
Thanks
Sai
PS: kindly reward points if helpful

Transforming XML/XSLT : CDATA problem

Hi!
I have a problem transforming xml with XSLT using the API javax.xml.
The result is correct until I have a CDATA section in my xml document.
The transforming process encodes all the & < > (special characters) it finds in.
This occurs problem for the follow of my treatement because the content of my CDATA is already encoded.
For example, this xml code :
<?xml version='1.0' encoding="ISO-8859-1" ?>
<article>
<article-contenu><![CDATA[Accent : é Signe : <]]></article-contenu>
</article>
produces in my output :
Accent : &eacute; Signe : &lt;
This is my java code :
TransformerFactory tFactory = TransformerFactory.newInstance();
Source xmlSource = new StreamSource(readerXml);
Source xslSource = new StreamSource( fileXsl );
// Generate the transformer.
Transformer transformer = tFactory.newTransformer(xslSource);
// Perform the transformation, sending the output to the response.
transformer.transform(xmlSource, new javax.xml.transform.stream.StreamResult(sw));
How can I tell the transformer not to do that?
Thanks for your answers!

I am having a similar problem. I have enclosed my text data in my xml file like this:
<![CDATA[<b>Hello World!</b>]]>
My select statement in my XSLT sheet is as follows:
<xsl:value-of select="." disable-output-escaping="yes"/>
I have tried setting xsl:output to text, to html, and to xml. The <, >, and & get converted to xhtml entities.
Where should I begin to troubleshoot? If the Xalan xslt jars? My stylesheet. My xml doc? Java code?
Any feedback welcome.

Invalid meta tag generated when using XHTML method

Hi,
I'm trying to generate an XHTML file using XSL and the XHTML output method. However, transformation results in adding the following XHTML-invalid meta tag (uppercase and non-closing) in the head tag:
<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
Is it a bug in the XDK or am I missing something? Transform is performed using the JXTransformer provided in 11g.
Thanks in advance,
Stephane
input file:
<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xml:lang='en' lang='en' xmlns='http://www.w3.org/1999/xhtml'>
<head>
     <title>Some title</title>
</head>
<body></body>
</html>
xsl file:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="2.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:xhtml="http://www.w3.org/1999/xhtml">
     <xsl:output method="xhtml"
doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN" doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"/>
<xsl:template match="*">
     <xsl:element name="{local-name()}" namespace="http://www.w3.org/1999/xhtml">
          <xsl:apply-templates />
     </xsl:element>
</xsl:template>
</xsl:stylesheet>
output:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
*<META http-equiv="Content-Type" content="text/html; charset=UTF-8">*
<title>Some title</title></head><body></body></html>

For some reason when I use MapForce tool to generate my xslt mapping source, it is generating the following statement in the xsl file.
     <xsl:namespace-alias stylesheet-prefix="n" result-prefix="#default"/>
So at the root element of XML file, it is replacing the character n with '#default' for some reason, I don;t know the purpose of this.
As you suggested, I changed the name space, still I experienced same problem.
It is now resolved after removing the above xsl statement from the xsl file before creating/uploading the relevant zip file into archives folder.
It works fine now. Thanks for the clue.

XSLT transformation on mobile

Hello,
I am developing a mobile application where i need to do an XML to XSLT transformation on the mobile phone itself.
I will store XML and XSLT file in mobile and want to see a WML or XHTML file in the browser.
Is WTK supporting this?
Does anybody know library for this/ how can i achieve this.
thanks,
Krishna

{color:#ff0000}{size:20px}CROSS POSTED{size}{color}
[http://forums.sun.com/thread.jspa?threadID=5335722]
Cross posting is rude.
db

Generating XHTML elements

Hi there
I have problem with j2sdk1.4.2_02 and Xalan.
I have parts of servlet output (XHTML 1.0) generated from DOM.
i.e.
<!DOCTYPE ...>
<html><head....>
<body><div id="container"><%=formatedDom%></div></body>Thie point is, that with javax.xml.transform.Transformer I am able only to generate xml tags (i.e. empty <textarea></textarea> is written as <textarea/> , which sucks under IE6, because exploder treats rest of code as textarea value) or html4 tags (i.e. <br> instead of
Setting OutputProperty(OutputKeys.METHOD, Method.XHTML) works as pure XML.
Do you have any idea how to solve this problem?
Regards

I ran into this same problem. My first research suggested I need to set the output type and version.
You can do this in the xsl
<xsl:output method="html" version="4.0" /> or override whatever's in the XSL in code:
import javax.xml.transform.OutputKeys;
transformer.setOutputProperty( OutputKeys.METHOD, "html" );
transformer.setOutputProperty( OutputKeys.VERSION, "4.0" );BUT in my case it turned out that there was an error in the stylesheet definition.
Here's the normal header:
<?xml version="1.0"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">For some unknown reason (a missed attempt to update the html tag?) the stylesheet I was testing had this: (WRONG!!)
<?xml version="1.0"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0" xmlns="http://www.w3.org/TR/REC-html40">Bizarre -- note the second namespace attribute! -- but subtle things like this can apparently confuse the transformer into overriding the options you specified.
Rob
jtheory.com

XML validation: how to check ALL validation problem for XHTML

I have a lot of documents in HTML format (not very good) that I would like to convert in XML (XHTML). I know it is not so easy and I would use this strategy in a Java program:
1. Try to check the well-formness and validation with a XML parser (SAX or Xerces)
2. If not valid: try to individuate ALL the problems the file has (*and not only the first one that halts the processing process*)
3. Try to transform the HTML to a validable XHTML with some approach: regular expression or other methods
So the questions I do to you are the following:
1. What XML parser do you think is the best for this purposes? SAX or Xerces?
2. How can I understand what are all the validation problems in the file and not only the first one (If I remember well XML parsers halt the parsing process at the first error...)?
3. How can I transform the HTML to a valid XHTML? I have only to use RegEx or is there other tools to do this for XHTML and HTML problem?
Thanks
r
Edited by: robertobat on Feb 21, 2009 7:09 PM

>
1. Neither of them. (Disregarding the fact that SAX and Xerces aren't in the same category and don't cover all the possibilities.I would say SAX default implementation in JRE and SAX parser in Xerces.
2. I think you have "valid" and "well-formed" confused. And HTML isn't a dialect of XML so the idea of trying to use an XML parser to handle HTML isn't a good idea.I know very well what is the difference between valid and well-formed but I've used "validation" to represent all the conversion problem. But you are right. I'm convincing myself that using a XML parser as the first step is not a good idea.
3. Well, this is the real question, isn't it? Those other two were just a waste. Don't screw about with regex, for one thing it doesn't work well for hierarchical structures and for another you won't finish in a finite time. Just use an HTML parser which can produce a DOM, like TagSoup for example. Or run them through HTMLTidy. You could also submit them to one of the internet sites which will validate XHTML for you.I've seen Tidy and its capability to convert an HTML to a XHTML and I think it is better then TagSoup because I have to implement this mechanism in a production environment and I want to use only open source projects that have a very long story and that are strong. But I'll see TagSoup as you say.
I cannot use an Internet service to convert millions of private documents.

Transforming XML source to (X)HTML StreamResult outputs long comment

Hi,
I'm using javax.xml.transform.* to transform XML data into an XHTML page. The XML data represents a document (contains information about headers, paragraphs, related pages, etc.) and an XSL file is used to properly transform that data into an XHTML compatible file. All transformations go just as they should, however, the XHTML output contains a very lenthy comment about elements and attributes concerning HTML. Obviously, I do not want this comment in my final output. As a side note: I'm using a StreamSource(File) for the XML data source, a StreamSource(File) for the XSL file and a StreamResult(HttpServletResponse.getOutputStream()) for the HTML output. I'm not sure wether the problem is with using a StreamResult directly (rather than a SAXResult), or because I'm outputting directly to the servlet output stream. All input and output is in UTF-8, and the HttpServletResponse has been configured using setCharacterEncoding("UTF-8") and setContentType("text/html").
Everything works fine, except I get this stinkin' long comment, which I want gone.
Thanks,
Yuthura

I get the following result.html file (properly transformed and displayed in my browser, except for the comment):




















































 ... (more to come)

Problems with xsl transformation

Hi,
I have an XSL to transform an XML to HTML code.
I want my HTML to be ACCESSIBLE.
All is working ok, but the <html> tag have two or three attributtes that make de code no ACCESSIBLE.
This is a part of the XSL code:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:fn="http://www.w3.org/2005/xpath-functions" xmlns:xdt="http://www.w3.org/2005/xpath-datatypes">
     <xsl:output method="xhtml" version="1.0" encoding="UTF-8" indent="yes" standalone="no"/>
<xsl:include href="barraSuperior.xsl"/>
     <xsl:include href="cabecera.xsl"/>
     <xsl:include href="menu.xsl"/>
     <xsl:include href="enllacosDestacats.xsl"/>
     <xsl:include href="contenido.xsl"/>
     <xsl:include href="barraBanners.xsl"/>
     <xsl:include href="pie.xsl"/>
     <xsl:variable name="homeWeb">http://172.16.67.119:8080/Biblioteques/xslt/V53CapSetmana</xsl:variable>
     <xsl:variable name="idioma"><xsl:value-of select="xmlData/config/idioma"/></xsl:variable>
     <xsl:variable name="literals" select="document(concat($homeWeb,'/traduccions/',$idioma,'.xml'))"/>
     <xsl:template match="/">
          <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="{$idioma}" lang="{$idioma}">
               <head>
                    <title>
<body>
                    <xsl:call-template name="barraSuperior"/>
                    <xsl:call-template name="cabecera"/>
                    <div id="wrapper">
                         <div id="columna0">
                              <xsl:apply-templates select="xmlData/menuLateral/contingutVignette/contingut/llista"/>
                         </div>
                         <xsl:call-template name="contenido"/>
                    </div>
                    <xsl:call-template name="pie"/>
               </body>
          </html>
     </xsl:template>
</xsl:stylesheet>
This is a part of the HTML result:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<html xmlns="http://www.w3.org/1999/xhtml" xmlns:fn="http://www.w3.org/2005/xpath-functions" xmlns:xdt="http://www.w3.org/2005/xpath-datatypes" xmlns:xs="http://www.w3.org/2001/XMLSchema" xml:lang="ca" lang="ca">
     <head>
          <title>B cap de setmana</title>
</head>
<body>
</body>
I want the <html> to be like this:
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="ca" lang="ca">

Use the exclude-result-prefixes attribute in your xsl:stylesheet element.

Indisign scripting and cross-media export - Xhtml / Dreamweaver

Hi.
I've searched for the solution but haven't found it yet. Hope you'll help me.
I need to write a script which will transform all indd files in the selected folder to xhtml. But I cannot find methods for exporting files to xhtml in JS (like menu -> File -> Cross-media export -> Xhtml / Dreamweaver). Is it possible? how?
P.S. Using CS3
Thanks

Thanks Olav, that would be very helpful if you could.
You're right, and XSLT is what Java uses for the CS2 version of
this project. We never used ExtendScript to do anything other than
mapping styles to XML.
I was hoping to avoid too many details, but this might benefit the discussion:
Original need:
We use an open source project called Sakai (Learning Management System)
that comes with documentation which we rebranded every time a new release
was rolled out. Our implementation of the Sakai LMS is called TRACS here at
Texas State University|San Marcos and we have a pretty strong demand for
consistentcy and adhering to project and university level branding guidelines.
Our support staff was using word documents and spent a laborious 2 months
minimum with their workflow getting everything migrated. Our branding needs
were steep. I was the graphic designer at the time the brand was created
and saw branding issues with the word docs being authored. We constantly
fought issues with inconsistent formatting (logo placement, logo version,
leading, fonts, etc.).
Automation with ExtendScript was the answer (and Java, AppleScript).
What took a variety of people with differing MS word skill sets 2 months
now took a mere 5 minutes or less.
Rough outline of our app:
Our Java process looks at a watched folder and coordinates the automation
with receipts that are written out after each phase is done.
Our Word documents are formatted with identically named character
and paragraph styles that are found in our InDesign template.
Java grabs a list of all the word docs to be processed, writes out an include
to be used later for our ExtendScript.
ExtendScript systematically takes each one in the array:
- takes care of flowing in the word doc
- page numbering
- mapping styles to tags
- PDF export
- XML export
- XML cleanup (some trash comes over from the export)
- XHTML generation
- writes receipts at each phase to tell JAVA it's ready for
the next phase as flow control
Java picks up the receipt, transforms XML (using XSLT) to XHTML snippets that
the end user copy/pastes into our Content Management System. Ultimately, we'll
shoot for direct DB inserts, but we have to get the dust off the CS2 version
before we can discuss that again.
In regards to not using XSLT:
A recent test we did showed that InDesign CS4 had the ability to export very clean XHTML
based on style sheets applied to items in the document. Effectively, that negates our
need for XML mapping of stylesheets and the use of XSLT.
That is, if cross-media exports can be automated.

Genereting JSTL tags with an XSLT transformation question

Hi there!
I have some XML datas to display in a jsp file.
XML content is of this type:
<message>
<title>A message</title>
</message>
The most elegent way to present them is to transform XML via xslt into xhtml.
(that way I can externally change with ease the message formatting output without changing the jsp)
For that, I use the cool tag
<x:transform>
on each xml file i want to display (with x:foreEach)
The output produced for each xml file is:
<div class="message">
<h2>A message</h2>
</div>
My problem is now that I want to include custom tags in the generated content!
For exemple:
<div class="message">
<h2>A message<c:out ...></h2>
</div>
My question is:
how can I make that xslt generated tag to be executed???
Since it is the product of an xslt transformation ,I suppose it won't be executed at all...
Advices greatly appreciated! :)

I'm not sure I understand what you mean when you say "how can I make that xslt generated tag to be executed???"
You've got your XML input and the XSL-T stylesheet that will transform the XML input into an XHTML stream containing JSTL tags.
I'm assuming that you're going to ask a servlet to pass the XML input to the XSL transformer and get the XHTML output stream. Once you have that, the servlet will write the XHTML to the HTTP response output stream, where it'll be rendered by the browser.
I think the key is to make sure that you tell the browser that response type is a JSP (that's the only document type in which it makes sense to put JSTL tags). When the browser gets that JSP, it'll treat it like any other: generate .java code, compile that to a .class file, and then render.
I'm not sure about efficiency, but it sure is an elegant solution. - MOD

FM 10: DITA to XHTML transformation?

Similar Messages

Maybe you are looking for