2016-05-26 14:10 GMT+01:00 Jeremias Maerki <d...@jeremias-maerki.ch>:
> See http://xmlgraphics.apache.org/fop/2.1/events.html for an example of
> exactly that.
>
> HTH
> Jeremias Maerki
>
>
> On 12.05.2016 23:12:22 Oskar Berggren wrote:
> > Hi,
> >
> >
Hi,
Sometimes a document will reference an image that FOP is unable to find.
With FOP 2.0, it will print a SEVERE log and then continue processing the
file, eventually exiting with a regular zero exit code.
Because there may be a significant amount of other logs, and because this
FOP was invoked
Batik bug since 2015:
https://issues.apache.org/jira/browse/BATIK-1112
Sometimes coincidences are ridiculous... I discovered the existence of this
problem only yesterday and tried to bring some attention to it:
Incidentally 1.1.30 changelog contains this:
1.1.30 (release in 2017)
Fix precedence with multiple attribute sets (Nick Wellnhofer),
Rework attribute set resolution (Nick Wellnhofer)
Commit
https://gitlab.gnome.org/GNOME/libxslt/commit/05f70130433478c1075ce8b6fdc4c4dadf51d33e
So apparently
Here is some documentation about intentional changes to the title
formatting:
http://www.sagehill.net/docbookxsl/TitleFontSizes.html
Is there a possibility that your local default stylesheet file have been
modified somehow?
Or is the profiling thing breaking something? What happens if you remove
Haha, I was gonna object and claim I use xsltproc without seeing this
problem but luckily I double checked first. I do use xsltproc, and it seems
I have this problem too just never realized.
Thanks Bob!
/Oskar
Den tors 21 nov. 2019 kl 00:18 skrev Bob Stayton :
> Hi Thomas,
>
> This appears to
