Re: [xsl] Converting XML into ODT document to print as paper

Subject: Re: [xsl] Converting XML into ODT document to print as paper
From: "Christophe Marchand cmarchand@xxxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Date: Thu, 24 Sep 2020 12:02:35 -0000
HTML + CSS print is usually a good-enough solution. You may have a look 
to or to one of its 

I actually work on a maven-plugin that transform markdown to our 
exercise-book odt format, with quite a good result. But it's a very 
specific layout, and for now, is not open-source.

Flyingsaucer is probably your solution, as it is already ready-to-use.


Le 24/09/2020 C  10:24, Jean-Paul Rehr rehrjb@xxxxxxxxx a C)critB :
> >ready-made solution?
> Ready-made solutions usually are domain/standard specific (like 
> TEI-XML for book editions, etc). But even those usuallyB require 
> certain code-level interventions to work.
> Your data + layout are quite simple and are a goodB candidate for 
> XSL-FO <>:B  
> purpose-made to handle XML -> PDF outputs.
> Alternately, transform your source XML data into Open Office-compliant 
> XML...
> On Thu, Sep 24, 2020 at 9:57 AM Manuel Souto Pico 
> terminolator@xxxxxxxxx <mailto:terminolator@xxxxxxxxx> 
> <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx 
> <mailto:xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>> wrote:
>     Dear all,
>     I would need to convert XML to something that has a fixed page
>     layout ready to print, like ODT/OOXML or PDF.
>     I know OOXML is complex, but since the final document needs to be
>     printed and keep the same layout, probably HTML output is not good
>     for this (I guess!).
>     What I need at the moment is just a quick and dirty proof of
>     concept to show that this conversion is feasible and not too
>     difficult, to show it to decision makers (I'm not a XSLT developer
>     myself).
>     This is my input (sample):
>     And this would be my output:
>     My first thought was to unzip the ODT model I have, look at the
>     content.xml inside and then try to transform my XML into that same
>     structure (as suggested here:
>     However, probably that's the hard way...
>     I'm doing some research, any tips or pointers or advice or
>     recommendation or examples here would be highly appreciated. Is
>     there any best practice to do this? or a ready-made solution?
>     Thanks in advance.
>     Cheers, Manuel
>     XSL-List info and archive <>
>     EasyUnsubscribe
>     <> (by email)
> XSL-List info and archive <>
> EasyUnsubscribe <> 
> (by email <>)

Current Thread