Hi,
for my pdf output it seems like I need to scale all my images to 60 % to
make the output look good. I know that I can maintain the imagedata entries
like the following:
I also read that it is possible to turn sizing of for HTML via the *
ignore.image.scaling* parameter. But I would like to
Yes, HTML5 is available as a separate target for output, but it currently comes with a
few caveats.
The epub3 add-on that I've posted has two directories: xhtml5 and epub3. You should
be able to use the stylesheets in the xhtml5 directory to produce HTML5 output with
XML serialization.
The
Hello,
I found the parameter "keep.relative.image.uris" which reduces my
complexity. This way I have to copy the images only to one location
relatively to the build.xml. I would be still nicer if I could configure the
FOP task to use a path relative to the .fo file but I assume this is not
really
Hi folks. At the moment I'm using the XHTML version of the DocBook XSL
scripts. That's mostly fine, but I am trying to convert all of my web
work over th HTML5. (Vis, using more semantic tags, reduced-complexity
head elements, fewer extra wrapping divs, assuming that CSS actually
works now s
Hi Tom,
I would prefer if the path could just be relative to the .fo file.
Introducing a xml catalog and a new re-write rule seems unnecessary
complex.
I could fix it within my ant tasks copying the images into the build project
but this doesn't not seem like a solid solution to me.
Best regards
On Sat, Oct 1, 2011 at 05:33, Lars Vogel wrote:
...
> If I put the graphics relativ to the build.xml (which I keep separated from
> the content) everything works.
> The Ant File I'm currently using is:
> ---
> description="Generates pdf files from DocBook XML">
>
> destdir="${fobtmp
Hello Markus and Dean,
thanks for your replies. Based on your feedback I was able to find my issue.
It seems that the path is relative to the Apache Ant build.xml I'm using and
to the .fo file which is processed by the build.xml file.
If I put the graphics relativ to the build.xml (which I keep s
So if for my current project I use vanilla docbook 5 XSL (no
namespaces), it should work for me?
Not sure what you mean here. I consider "DocBook 5 XSL" to be the namespaced -ns-
version of the stylesheets, because the -ns- version directly processes DocBook 5
documents in the Docbook namespa
Hi, there, thanks for doing this and I appreciate the thoroughness of
the readme file.
One question. you said, "This directory contains a beta version of XSL
stylesheets for generating EPUB3 output from DocBook 4 content. The
stylesheets should work for DocBook5 content by first stripping off
the
