Re: [docbook-apps] Re: Font for the info part different than for the rest and the colophon

On Jan 29, 2019, at 9:23 AM, Bob Stayton wrote: > > The generated copyright symbol uses a template named 'dingbat' in fo/fo.xsl. > It sets the font-family to the $dingbat.fontset which is defined in > fo/pagesetup.xsl. I remember a time when such hacks were common and reasonable, but is it

[docbook-apps] Missing images in fop generated pdf

Hi Denis I am on fop 2.3 /Niels Greetings Niels Müller Larsen Programmer/Teacher > On 29 Jan 2019, at 16.48, E L L I P S Y S (Denis Gillain) > wrote: > > > Hi, > > which version of FOP do you use ( fop -version ) ? > > I'm afraid to have the same problem. > > > On Sat, 26 Jan 2019

Re: [docbook-apps] Re: Font for the info part different than for the rest and the colophon

The generated copyright symbol uses a template named 'dingbat' in fo/fo.xsl.  It sets the font-family to the $dingbat.fontset which is defined in fo/pagesetup.xsl.  That fontset  starts with the font named in $dingbat.font.family which is defined in param.xsl.  Reset that param to blank to fix

[docbook-apps] Re: Font for the info part different than for the rest and the colophon

The culprit is in the fo visible: Copyright © 2019 Bernhard Kleine the serif in front of Alegreya. Am 29.01.2019 um 14:01 schrieb Bernhard Kleine: > > Hi, > > I could nail down hopefully the last problem I have: > > in the Info part of my book there is > > >     2019 >    

[docbook-apps] Font for the info part different than for the rest and the colophon

Hi, I could nail down hopefully the last problem I have: in the Info part of my book there is     2019     Bernhard Kleine     This gives in the final pdf In the colophon I have written Copyright © 2019 Bernhard Kleine, Lenzkirch which transforms to Note that the