Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cmWia-0002Z9-MN for pgsql-docs@arkaria.postgresql.org; Sat, 11 Mar 2017 02:25:16 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cmWia-0002Br-7X for pgsql-docs@arkaria.postgresql.org; Sat, 11 Mar 2017 02:25:16 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cmWiZ-0002BM-ND for pgsql-docs@postgresql.org; Sat, 11 Mar 2017 02:25:15 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cmWiW-0003Cn-RY for pgsql-docs@postgresql.org; Sat, 11 Mar 2017 02:25:14 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 0A86220890 for ; Fri, 10 Mar 2017 21:25:12 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Fri, 10 Mar 2017 21:25:12 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=smtpout; bh=R1FwzpfCnd3pHA Q0c8rt6p4ce3s=; b=Jc+p44p1dG1M0Wxermb63Dw+AYMK7+lH4uFQ+nKMR2Ndcy tWZ8NH6exrjpZb19vqun3fiQYxmPB6XXpVYIc6MyUm0p8YRoue6BVQg2whN6hbUj 8T0Bsu2sB2DGohlREoON2KF9D0llKDwlytGJp0m/BmR36CSn3iaT0RmBZDvHM= X-ME-Sender: X-Sasl-enc: kKqCcZM5KoDAwuyR7Kh1yGw69/d59G/EGgVm2QsLaF0J 1489199111 Received: from april.local (c-73-13-66-39.hsd1.pa.comcast.net [73.13.66.39]) by mail.messagingengine.com (Postfix) with ESMTPA id C0B467E168 for ; Fri, 10 Mar 2017 21:25:11 -0500 (EST) From: Peter Eisentraut Subject: PDF building with FOP Organization: 2ndQuadrant To: pgsql-docs Message-ID: <8533aa6b-0f07-9d76-af3b-1f8515b1365e@2ndquadrant.com> Date: Fri, 10 Mar 2017 21:25:11 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org As we are moving away from the old DSSSL toolchain, we also need to look into how we are building PDFs. The old way, using jadetex, is called by make postgres-A4.pdf postgres-US.pdf The new way, using FOP, is called by make postgres-A4-fop.pdf postgres-US-fop.pdf This already exists. The questions for those who are building PDFs are - Can you make the build work? - Does the output look OK? Some tips: FOP is extremely memory hungry. You will probably have to fiddle with some Java memory settings to make it work. One way is by edting ~/.foprc and set something like FOP_OPTS='-Xmx1200m' # fop upstream binary installation ADDITIONAL_FLAGS='-Xmx1200m' # centos/fedora JAVA_ARGS='-Xmx1200m' # debian It looks like you need at least -Xmx1000m, depending on the fop version. More memory can make things faster. (Some of this could go into the documentation.) Note also that there are wildly different fop versions shipped with distributions. Compare your package version or fop -v output with the available versions at . I have done a fair amount of testing across different platforms. My assessment is that it's good enough to move forward. It doesn't have to work out of the box for everyone. But I want to make sure that those who are building PDFs regularly are on board with this. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs