This is the mail archive of the docbook-apps@lists.oasis-open.org mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[docbook-apps] <literallayout> rendered with lots of internal whitespace


  (i'm on a roll this morning, and that's just based on decaf.  most
of these observations are based on a document that i'm throwing
together that demonstrate how to use a sizable number of docbook
elements by showing samples of their use.  so i'm getting to see
little glitches in the PDF generation i might not have noticed
before.  the toolchain is xsltproc + FOP.)

  the latest weirdness is the rendering of a simple 

<literallayout>
 Now is the time
   for all good men
 to come to the aid
   of their party.
</literallayout>

  an absolutely stock, non-customized PDF rendering appears as:

           Now          is         the         time
            for       all        good           men
        to       come      to         the       aid
               of             their           party.

in other words, all sorts of inserted whitespace, and left-justified
for no reason that i know of.

  OTOH, if i change this ever so slightly to

<literallayout class="monospaced">...

it's perfect -- courier font, proper indentation:

 Now is the time
   for all good men
 to come to the aid
   of their party.


any reason why a generic literallayout would generate the first
example above?  the example shown in the online docbook TDG is
wrapped inside a <blockquote>, but a <para> is apparently a legal
parent as well, which is what i'm using.

  thoughts?

rday


To unsubscribe from this list, send a post to docbook-apps-unsubscribe@lists.oasis-open.org.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]