docbook-apps

I am getting this warning when running fop for pdf from my fo file
(generated from docbook source):

I thought that shouldn't happen since the ZapfDingbats is hard-coded
in fop. Isn't it a vector font so that any size can be produced?

However, I found reference to fop bug 47279 which says:

<quote>
When the font-family property hasn't been specified in the FO file, it defaults
to "sans-serif,Symbol,ZapfDingbats". But the latter two aren't available in a
bold variant. When a block of text can be rendered using the sans-serif family
only, warnings are still issued about unavailable Symbol bold and ZapfDingbats
bold. This is likely to puzzle users.
</quote>

So, isn't the missing default fo entry due to a docbook bug? I
couldn't find reference to anything similar in the docbook tracker.

Thanks.

-Tom

Thomas M. Browder, Jr.
Niceville, Florida
USA

On Mon, Jun 28, 2010 at 09:05, Tom Browder <tom.browder@gmail.com> wrote:
> I am getting this warning when running fop for pdf from my fo file
> (generated from docbook source):

Oops, here it is:

WARNING: Font "ZapfDingbats,normal,700" not found. Substituting with
"ZapfDingbats,normal,400"

Sorry.

-Tom

On Mon, Jun 28, 2010 at 09:08, Tom Browder <tom.browder@gmail.com> wrote:
> On Mon, Jun 28, 2010 at 09:05, Tom Browder <tom.browder@gmail.com> wrote:
>> I am getting this warning when running fop for pdf from my fo file
>> (generated from docbook source):

I also get the same type of warning about another base-14 font:

WARNING: Font "Symbol,normal,700" not found. Substituting with
"Symbol,normal,400".

-Tom

You can modify symbol.font.family[1] and add a symbol font that supports
boldface. I always set it to empty, because I only use UTF-8 fonts which
already include all the symbols I need.

> Isn't it a vector font so that any size can be produced?

No. Bold versions of a font aren’t automatically produced out of the normal
version. They have to be designed too. Some word processors can automatically
“boldify” a font, but the result isn’t very pretty/professional imho.

Bela

[1]http://docbook.sourceforge.net/release/xsl/current/doc/fo/symbol.font.family.html

On Monday 28 June 2010 16:16:20 Tom Browder wrote:
> On Mon, Jun 28, 2010 at 09:08, Tom Browder <tom.browder@gmail.com> wrote:
> > On Mon, Jun 28, 2010 at 09:05, Tom Browder <tom.browder@gmail.com> wrote:
> >> I am getting this warning when running fop for pdf from my fo file
>
> >> (generated from docbook source):
> I also get the same type of warning about another base-14 font:
>
> WARNING: Font "Symbol,normal,700" not found. Substituting with
> "Symbol,normal,400".
>
> -Tom
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org

On Mon, Jun 28, 2010 at 09:29, Bela Hausmann <post@belahausmann.name> wrote:
...
>> Isn't it a vector font so that any size can be produced?
...
> No. Bold versions of a font aren’t automatically produced out of the normal

Maybe my bug reference was misleading. The need for bold may be
happening behind the scenes in fop, but the warning doesn't say
anything about needing a bold font, so maybe this is an fop bug after
all?

Thanks, Bela.

-Tom

Thomas M. Browder, Jr.
Niceville, Florida
USA

I would guess that this is because symbol.font.family is added to
title.font.family as well and titles are bold?

You can inspect your .fo file and find out where exactly bold and
symbol.font.family are mixed, that may clear up if it’s a FO-XSL bug or not?

Bela

On Monday 28 June 2010 17:00:46 you wrote:
> On Mon, Jun 28, 2010 at 09:29, Bela Hausmann <post@belahausmann.name>
> wrote: ...
>
> >> Isn't it a vector font so that any size can be produced?
>
> ...
>
> > No. Bold versions of a font aren’t automatically produced out of the
> > normal
>
> Maybe my bug reference was misleading. The need for bold may be
> happening behind the scenes in fop, but the warning doesn't say
> anything about needing a bold font, so maybe this is an fop bug after
> all?
>
> Thanks, Bela.
>
> -Tom
>
> Thomas M. Browder, Jr.
> Niceville, Florida
> USA

Tom
Have you configured FOP to handle the fonts that you want?

I try not to have FOP search for fonts - it takes too long and you really can't control what it finds. Instead, I specify the fonts specifically.
Here is a snippet from my FOP config file:
<fonts>





































<directory>../../doctools/dejavu-fonts-ttf/ttf</directory>





</fonts>


--------------------------------------
In addition, I have some XSL code that allows markup like <emphasis role="bold"> when I what to specifically bold an item.

HTH
Dean Nelson


In a message dated 06/28/10 08:01:28 Pacific Daylight Time, tom.browder@gmail.com writes:
On Mon, Jun 28, 2010 at 09:29, Bela Hausmann <post@belahausmann.name> wrote:
...
>> Isn't it a vector font so that any size can be produced?
...
> No. Bold versions of a font aren’t automatically produced out of the normal

Maybe my bug reference was misleading. The need for bold may be
happening behind the scenes in fop, but the warning doesn't say
anything about needing a bold font, so maybe this is an fop bug after
all?

Thanks, Bela.

-Tom

Thomas M. Browder, Jr.
Niceville, Florida
USA

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org

On Mon, Jun 28, 2010 at 10:38, DeanNelson <deannelson@aol.com> wrote:
> Tom
> Have you configured FOP to handle the fonts that you want?

Dean, I'm just getting started customizing a large set of docbook xml
that was converted from our html docs.

I haven't tried to use any specific fonts at all. I am happy with the
base-14 until I get formatting, etc, more into desired shape.

I appreciate the font config inf and I'm sure I will be using it as I
improve my set up.

So, if I don't specify fonts in my xml source, will your setup help
with the warnings?

Thanks.

Regards,

-Tom

P.S. I am always looking for good customizations.

Most likely it has to do with the fonts that reside on your system. You will need to have a good symbol font that covers the symbols you need. We use the DejaVu fonts (http://dejavu-fonts.org) and I have not had any problems with them. It's been a long while since I used any other fonts, but I remember some "issues" with the regular fonts in Windows and Linux that FOP tries to use.

I have attached my font setup customization for your perusal. Also, like some of the previous posts said, check out the FO file and see what problem it is having. FOP usually will tell you a line to go to in the error. When I need to dig into the FO file, I usually format the FO with xmllint before running it through FOP. It will be easier to find the structure around your problem.

If FOP cannot find a suitable font, it will substitute one that it has.

Regards,
Dean Nelson




In a message dated 06/28/10 08:49:45 Pacific Daylight Time, tom.browder@gmail.com writes:
So, if I don't specify fonts in my xml source, will your setup help
with the warnings?

On Mon, Jun 28, 2010 at 13:28, deannelson <deannelson@aol.com> wrote:
> Most likely it has to do with the fonts that reside on your system. You will
> need to have a good symbol font that covers the symbols you need. We use the
> DejaVu fonts (http://dejavu-fonts.org) and I have not had any problems with
...
> I have attached my font setup customization for your perusal. Also, like
> some of the previous posts said, check out the FO file and see what problem
> it is having. FOP usually will tell you a line to go to in the error. When I

Thanks, a heap, Dean!

Regards,

-Tom