From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
cc: pgsql-hackers@postgresql.org
Subject: Re: Make fop less verbose when building PDF
In-reply-to: <20230324194701.dqkzcdtlcikseo22@awork3.anarazel.de>
References: <20230324194701.dqkzcdtlcikseo22@awork3.anarazel.de>
Comments: In-reply-to Andres Freund <andres@anarazel.de>
	message dated "Fri, 24 Mar 2023 12:47:01 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2403062.1679689197.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Fri, 24 Mar 2023 16:19:57 -0400
Message-ID: <2403063.1679689197@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/2403063.1679689197%40sss.pgh.pa.us>
Precedence: bulk

Andres Freund <andres@anarazel.de> writes:
> I just figured out that one can hide those. Unfortunately not at the
> commandline, but in "$HOME/.foprc" or /etc.

> $ cat ~/.foprc
> LOGLEVEL=3D-Dorg.apache.commons.logging.simplelog.defaultlog=3DWARN

Yeah.  I've done it locally by modifying the "fop" script ;-)
... but probably ~/.foprc would be neater.  I see that I also
changed the default logger:

LOGCHOICE=3D-Dorg.apache.commons.logging.Log=3Dorg.apache.commons.logging.=
impl.SimpleLog

because at least in the version I have, that isn't the default.

> [warning] /usr/bin/fop: JVM flavor 'sun' not understood
> [WARN] FOUserAgent - Font "Symbol,normal,700" not found. Substituting wi=
th "Symbol,normal,400".
> [WARN] FOUserAgent - Font "ZapfDingbats,normal,700" not found. Substitut=
ing with "ZapfDingbats,normal,400".
> [WARN] FOUserAgent - The contents of fo:block line 2 exceed the availabl=
e area in the inline-progression direction by more than 50 points. (See po=
sition 30429:383)
> [WARN] PropertyMaker - span=3D"inherit" on fo:block, but no explicit val=
ue found on the parent FO.

> The first is a debianism, the next two are possibly spurious [1]. But th=
e next
> two might be relevant?

The one about "exceed the available area" has been on my radar to fix;
it's a consequence of an overly-wide example somebody added recently.
The other ones have been there all along and I don't know of a way to
get rid of them.

> I don't immediately see a way that's not too gross (like redefining HOME=
 when
> invoking fop) to set LOGLEVEL without editing .foprc.  Perhaps we should=
 add
> advice to do so to docguide.sgml?

+1

			regards, tom lane