Subject: Re: [xsl] XSL-FO and XSD Information request From: Kamal Bhatt <kbhatt@xxxxxxxxx> Date: Mon, 20 Mar 2006 18:47:00 +1100 |
Much of Mulberry's schema documentation is built this way, however, and we're not the only ones. The thing is, that's part of the special value we provide our clients, and not something we're able to develop and support for the world at large. So in general we (and many other schema designers will say the same, I think) can affirm that yes, it's doable, and in principle a good idea (assuming you know what you're doing); but we can't say much more beyond that than ask the classic question: "what are your requirements?". Whether it's hard or not depends on the task. It's not hard to do lots of useful stuff; but particular tasks can be quite challenging, depending on what kind of schema you have. Perhaps the biggest conceptual challenge is in developing a good sense of which tasks can be automated easily and usefully, and which ones are better left for sensible people to do.
<element attr1="xxxx" attr2="xxxx" attr3="xxxx" attr4="xxxx" attr5="xxxx" attr6="xxxx" attr7="xxxx" attr8="xxxx" attr9="xxxxx" attr10="xxxxxxxx" attr11="xxxxx" attr12="xxxxxxx" attr13="xxxxxx" attr14="xxxxx"> ... </element>
I was thinking that maybe I could use something to convert the XML into PDF, word and HTML inside of cocoon. I think there is support for FOP in cocoon, what about WordML?
I've created a system that turns content stored in XML into PDF (through
XSLT to XSL-FO and then through FOP), Word (through XSLT to WordML), HTML
(throught XSLT), JavaHelp (through XSLT), and text (through XSLT).
So, what you have in mind can be done.
-- Disclaimer: This email is confidential and may contain privileged information for the sole use of the person or business to which it is addressed. If you are not the intended recipient, please notify the sender by return e-mail or phone as you must not view, disseminate, distribute or copy this email without our consent. We do not accept any liability in connection with any computer virus, data corruption, incompleteness, or unauthorised amendment of this email. It is the sole responsibility of the receiver to scan for viruses before opening.
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] XSL-FO and XSD Informatio, Wendell Piez | Thread | Re: [xsl] XSL-FO and XSD Informatio, Wendell Piez |
[xsl] Announce: Repeat XSL Delivery, G. Ken Holman | Date | [xsl] descendant-or-self XSLT 1.0, news |
Month |