[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [docbook-apps] Using custom fonts
I had problems like this as well when switching to FOP.I had to be very careful with parameter settings in my customization layer, like body.font.family.We had been using XEP, and in modifying my layer for FOP, I found it would often not find the italics version of the body font. In some cases I limited some items to an italic font.With XEP, I'd provide a list of fonts or just the base font name, and it would find the italic version, but with FOP, it wouldn't.--Aaron DaMommio--On Wed, Mar 11, 2015 at 11:39 AM, Alan Oehler <firstname.lastname@example.org> wrote:Any other ideas about what might be wrong here? I've Googled a bunch and I find some places where people had trouble with HTML output not being italic or bold when expected, but pretty much reached a dead end on fop PDF output.On Fri, Mar 6, 2015 at 2:40 PM, Alan Oehler <email@example.com> wrote:Made that change, and it didn't help the emphasis issue.--On Fri, Mar 6, 2015 at 2:32 PM, Thomas Schraitle <firstname.lastname@example.org> wrote:Hi Alan,
Am Freitag, 6. März 2015, 23:28:56 schrieb Thomas Schraitle:
> > I created a fop config file to register Trebuchet as my basic body font
> > and Consolas as my monotype font.
> > I added all four variants of both fonts (normal, italic, bold and bold
> > italic). Is there some other detail I'm missing?
> "Register" Trebuchet? Which version of FOP do you use?
> As far as I know, registering a font is not needed anymore for >1.0.
I forgot to add my example. Here is an excerpt of the PDF renderer:
register all the fonts found in a directory
use recursive="true" to also include subdirectories
<!-- automatically detect operating system installed fonts -->