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]

Re: [docbook-apps] Image Sizing in Printed Output (PDF)


This problem may have something to do with the way FOP handles the width and
depth attributes, which is hardly at all.  I'd try to use a unit other than
pixels, since that unit is implementation dependent.  Try in or cm and see
if the output matches your specified sizes.

Also, the last time I tested FOP, only the width attribute in imagedata had
any effect on the graphic.  Neither contentwidth nor contentdepth seems to
be used by FOP.

The fact that the table overwrites the graphic sounds like a FOP bug.  That
means the block that FOP allocates to the graphic is too small, and the
graphic marks extend beyond the block. The table block starts after the
graphic block without overlapping the block, but if the graphic marks go
beyond its own block, that's a problem.

You might experiment by editing the FO output and inserting border
properties on some of the fo:blocks to see what is going on with the blocks.

Bob Stayton
Sagehill Enterprises
DocBook Consulting
bobs@sagehill.net


----- Original Message ----- 
From: "Russell Seymour" <russell.seymour@turtlesystems.co.uk>
To: <docbook-apps@lists.oasis-open.org>
Sent: Tuesday, August 17, 2004 1:47 AM
Subject: [docbook-apps] Image Sizing in Printed Output (PDF)


> Good morning List,
>
> I have asked similar questions to the list before about this topic, and
> whilst I have recieved very favorable replies in the past none of them
> have fixed the issue I am having.  If anyone has any ideas then I would
> be most grateful for your input.
>
> I create SVG charts based on data pulled from a database, in this case
> server availability.  These charts are then added to the PDF using the
> <mediaobject> tag in the docbook XML.  In addition I create an
> <informaltable> in the <figure> tag to show the raw data of the
> availablity as a percentage.  This is where I have an issue.
>
> The graphic is successfully converted from SVG to a bitmap by FOP and
> added to the document, however the table holding the raw data does not
> start below the bottom of the graphic, instead it is placed over the top
> of it - over the x-axis label.  Obviuosly this looks untidy and is very
> difficult to read .
>
> The XML markup I am using is at the end of the email.
>
> I can provide a test output to anyone that needs to see what I am on
> about before making any suggestions.
>
> Thanks in advance for any help you can provide.
>
> Russell
>
> <figure><title>System Availability</title>
> <mediaobject>
> <imageobject role='html'>
> <objectinfo><title>Avaliability of Systems</title></objectinfo>
> <imagedata format='SVG'
> fileref='/working//18/avaliability_of_systems.svg' contentwidth='550'
> depth='400' align='center' />
> </imageobject>
> <imageobject role='fo'>
> <objectinfo><title>Avaliability of Systems</title></objectinfo>
> <imagedata format='SVG' fileref='/tmp/18/avaliability_of_systems.svg'
> contentwidth='550px' depth='450px' contentdepth='450px' scalefit='1' />
> </imageobject>
> </mediaobject>
> <informaltable>
> <tgroup cols='10'>
> <tbody>
> <row><entry>1</entry>
> <entry>2</entry>
> <entry>3</entry>
> <entry>4</entry>
> <entry>5</entry>
> <entry>6</entry>
> <entry>7</entry>
> <entry>8</entry>
> <entry>9</entry>
> <entry>10</entry>
> </row>
> ....... SNIP .......
> </tbody>
> </tgroup>
> </informaltable>
> </figure>
>
>
>



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