To view parent comment, click here.
To read all comments associated with this story, please click here.
Ok, I wrote my comment really fast because the boss was coming ;-)
Seriously, I think people focus too much on the form of the document, and not enough about its content.
An OpenDocument should generate an XSL template for PDF generation (XSLFO, for example) or HTML generation, along with the generated document (or there could be 2 standard XSL templates for this).
This way, an exported document from OpenDocument to XML could be converted directly into browsers that support XSL Transformations.
Does it sound better now?
Some while ago i was thinking about a very evil plan about this topic:
I think the perfect content manager(tm) should store its pages in an as rich as possible form, possibly xml, and now the better/cooler is OpenDocument, and should transform the pages with xsl server-side (obviously with an aggressive caching of the generated documents to not eat too much cpu).
And then when the user access the site, (s)he can specify the preferred format, for example:
-www.ubercoolsite.com/index.html will be the default, normal html page
-www.ubercoolsite.com/index.odt will be opendocument and so on
in this way there will be a consistent way to generate html, opendocument, pdf and tons of different formatted documents, with a wery little effort.






Member since:
2005-08-20
"Export to xsl and make templates
"
Me izz Mr. Wise Guy tonight... XSL (resp. XSLT) is a language in which you can write templates to transform XML code - so no need to "export to XSL"
Okay, here's the serious part of my answer: Doesn't make sense - does it? Using XSL you can transform the XML Code of the OpenDocument format into something else. But you'd still need some new capability in the browser so that "something else"(tm) is displayed with the layout etc. of the original file.
Edited 2005-11-16 19:42