Hi Mike,

I can't help you with the DocBook query as I've never used DocBook
myself, however, it is important to understand that XSL-FO and XML in
generally is strongly typed.

As for your XML all on one line, there is a way to output a more
readable format, I think you have to set indent="yes" on the
<xsl:output> object (http://www.w3schools.com/xsl/el_output.asp), but
again, I don't use XSLT very often so I'm not 100% on this. Also, in
future, if you have XSLT questions, could you ask them on the XLST
mailing list (http://www.mulberrytech.com/xsl/xsl-list/), this mailing
list is specifically for FOP questions.

Hope that helps

Mehdi

On 7 October 2011 10:05, Mike Chambers <[email protected]> wrote:
> Hi Mehdi,
>
> Ah OK thanks that makes sense, and now I understand the spec. that little bit
> better :) It would seem then that the block vs. inline concept is similar to
> that in HTML/CSS, but that in HTML you don't /have/ to explicitly wrap inline
> content with e.g. a block-level DIV, as you get something along the lines of 
> an
> 'anonymous block box' (I think that is the terminology, and is what happens 
> AIUI
> if you have e.g. <body>Hello world</body>, with no <p /> wrapping the text.).
>
> I manually added the wrapper <fo:block> object to the XSL-FO generated by 
> Saxon
> and FOP processed it OK.
>
> OOI is it normal for an XSLT processor to output an XSL-FO (or indeed any 
> other
> format) document that is a single (very long) line? It makes it harder to
> examine and then edit the structure of the document in a standard text editor.
> I'm puzzled as to why the processor output couldn't be multiline with suitable
> indentation. I know these are essentially machine processed files, but AIUI 
> one
> of the points of XML is that a human can read it if they really want to.
>
> So now to find out why /both/ Saxon and Xalan generated XSL-FO output that
> omitted the same necessary wrapper object.
> Maybe because they were both using the same DocBook XSLT stylesheet(s) ?
> Would it be the case that the DocBook XSL stylesheet for generating FO output
> controls things such as when/where to put an <fo:block>? My logic & limited
> understanding of XSLT suggests it would, and thus maybe there is a bug in the
> XSLT stylesheet I have obtained via a Ubuntu repository package.
>
> Many Thanks,
> Mike
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to