[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: docbook generation problem with @image
From: |
Karl Berry |
Subject: |
Re: docbook generation problem with @image |
Date: |
Fri, 16 Aug 2013 17:18:33 GMT |
Hi Arnold,
Finally getting back to this report.
Date: Tue, 16 Apr 2013 21:47:16 +0300
From: Aharon Robbins <address@hidden>
... @image{api-figure1, , , Loading the extension} ...
The generated docbook is:
...
<inlinemediaobject><imageobject><imagedata fileref="api-figure1.eps"
format="EPS"></imagedata></imageobject><imageobject><imagedata
fileref="api-figure1.pdf"
format="PDF"></imagedata></imageobject><imageobject><imagedata
fileref="api-figure1.png"
format="PNG"></imagedata></imageobject><textobject><literallayout>
...
This is clearly wrong. It should only include one of the
<imageobject>s, not all of the possible ones. I would think PDF
would be the right one.
Ok for that case, but we need to know generally which image formats
Docbook prefers, in order. The complete list we look for with Docbook
is (alphabetically):
'eps', 'gif', 'jpeg', 'jpg', 'pdf', 'png', 'svg'
1) Are all of those formats actually usable in Docbook?
2) Can you tell us the priority order in which to look for them?
3) If none are found, what to do? Just include nothing and give a warning?
With that, we (i.e., Patrice :) can easily change the output so that
only the "best" format is referred to.
Thanks,
Karl
- Re: docbook generation problem with @image,
Karl Berry <=