Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pfnNZ-0004PA-Nc for pgsql-hackers@arkaria.postgresql.org; Fri, 24 Mar 2023 19:47:14 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pfnNY-0001TG-J2 for pgsql-hackers@arkaria.postgresql.org; Fri, 24 Mar 2023 19:47:12 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pfnNW-0001T7-Pf for pgsql-hackers@lists.postgresql.org; Fri, 24 Mar 2023 19:47:12 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pfnNR-0005s3-Pc for pgsql-hackers@postgresql.org; Fri, 24 Mar 2023 19:47:10 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 403345C00AE for ; Fri, 24 Mar 2023 15:47:03 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Fri, 24 Mar 2023 15:47:03 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anarazel.de; h= cc:content-type:content-type:date:date:from:from:in-reply-to :message-id:mime-version:reply-to:sender:subject:subject:to:to; s=fm2; t=1679687223; x=1679773623; bh=I3FGu8tIE2aiTPhZpCepQp45O gFls2/PIcNl7V9w9TM=; b=Ycy4YOPEiGdBSP+x7Ll+RBdYtUST675iDM2RuM7dU 9dKg3BF931dDEvnOEjjbaLstgXykd96kcUHour1KpsjKdItNQnwiNEhtsLUaqUqz 2qLVfclgetMzLXSJ5QnnxNHim0aIOAeUO3fi/dXA/9z68kplGDRort01FqaRz/mG vZL1lkrrtc+ROJcVlcnSNKNSn9KbFB9B43iXRRcUw4Hhx0h8wlnClkte05gxkGc/ srHiiWPKtOo9e2uNYItTtVeo/3PdyUY+y0XR0Xxj/hUn4ysAaK5+mrnZ0WLXxNkZ gXupMWZqQYwo5A0ZbUVdnMdzcA+Bn0RhqxvX+dGs+rFwQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:message-id :mime-version:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t= 1679687223; x=1679773623; bh=I3FGu8tIE2aiTPhZpCepQp45OgFls2/PIcN l7V9w9TM=; b=ccy1GFxVciRawcWeo/b+UJGcL6AKPnoIZC6Z0rgRHPEaRt7lg0W I24dJ4vGhNqHVEL6LYReW3k2MFoGhxC5Q6VSrApkcuBLPz5+g5ThGpKmiGypbEf0 lv7hN9suYueKzSNeQwL/5zR+J2BkXPiV74VPod2ZUCkqu+0wQmscVh5lNz4qBpI8 OSp3mfs1u2wR4WrZT1xTPvUO4UXHjXGQBUDjIcIpyOIkSimOyzDgMVX+PJF8aoj1 TTTrqeoD2+rPXtnrznPjPqr7rdtT2sCYTVIM9TRNPUZrESmP8IvKPReYdkog+UWu fv+0T0H2eOe68ldiy51BUR7A4iVRKdJyt9w== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrvdegiedguddvlecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepfffhvffukfggtggusehttdertd dttddvnecuhfhrohhmpeetnhgurhgvshcuhfhrvghunhguuceorghnughrvghssegrnhgr rhgriigvlhdruggvqeenucggtffrrghtthgvrhhnpefffeeludfgffeuleeguefhveefgf fgtdeggeefuefgjedtteegudffjedugfdvvdenucffohhmrghinheprghprggthhgvrdho rhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprg hnughrvghssegrnhgrrhgriigvlhdruggv X-ME-Proxy: Feedback-ID: id4a34324:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Fri, 24 Mar 2023 15:47:02 -0400 (EDT) Date: Fri, 24 Mar 2023 12:47:01 -0700 From: Andres Freund To: pgsql-hackers@postgresql.org Subject: Make fop less verbose when building PDF Message-ID: <20230324194701.dqkzcdtlcikseo22@awork3.anarazel.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, When building the pdf docs, fop emits a line for each page of the docs: > ... > [INFO] FOUserAgent - Rendered page #2931. which, given the length of our docs, makes the output pretty pointless. Even if there are warnings, one likely won't notice them. I just figured out that one can hide those. Unfortunately not at the commandline, but in "$HOME/.foprc" or /etc. $ cat ~/.foprc LOGLEVEL=-Dorg.apache.commons.logging.simplelog.defaultlog=WARN makes it a lot less annoying. And one can see that we currently are getting warnings: [warning] /usr/bin/fop: JVM flavor 'sun' not understood [WARN] FOUserAgent - Font "Symbol,normal,700" not found. Substituting with "Symbol,normal,400". [WARN] FOUserAgent - Font "ZapfDingbats,normal,700" not found. Substituting with "ZapfDingbats,normal,400". [WARN] FOUserAgent - The contents of fo:block line 2 exceed the available area in the inline-progression direction by more than 50 points. (See position 30429:383) [WARN] PropertyMaker - span="inherit" on fo:block, but no explicit value found on the parent FO. The first is a debianism, the next two are possibly spurious [1]. But the next two might be relevant? 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? Greetings, Andres Freund [1] https://lists.apache.org/thread/yqkjzow3y8fpo9fc3hlbqb9fk49fonlf