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 1jTrvY-0002wD-8q for pgsql-docs@arkaria.postgresql.org; Wed, 29 Apr 2020 18:59:24 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jTrvW-0003p6-NB for pgsql-docs@arkaria.postgresql.org; Wed, 29 Apr 2020 18:59:22 +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 1jTrvV-0003oz-PE for pgsql-docs@lists.postgresql.org; Wed, 29 Apr 2020 18:59:22 +0000 Received: from forward5-smtp.messagingengine.com ([66.111.4.239]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jTrvM-0005yO-VI for pgsql-docs@lists.postgresql.org; Wed, 29 Apr 2020 18:59:21 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailforward.nyi.internal (Postfix) with ESMTP id 412EA19404AA; Wed, 29 Apr 2020 14:59:10 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Wed, 29 Apr 2020 14:59:10 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=p97Dza PHpL0lII9D5D9DzPDtYiuI0B1ohyo/rTim/P4=; b=rXGrfXGGH8xIR2URMIkAvn sjWvi2B2dTiWd3ZM0SoLfb4CQfhD8AzQeDEL40MrpTYSsrsZdxLXo9xDuAzoSFkO 5WoWIctxNUmyIVyUXDCVgmxAcHO1YMFOe1m8yvxF4LTiVKixKurUEWvFB5F8r+jJ 17xOF4TychsXL5GMfwcWa5NLUOFhsajKVd4dMCGI/Ii7insVcXwQlDz2/HqqzVei 4kuPtUXY/U960aY6WVuwO5l0okwYa0Xk14IVzaiUTSKu8DzUSzTlLJN4vdq5PY5H MrdHMukT4g+Y2YxHxugK+4CuCldS+0ZZfnRbozAlZ84XKr2Hxliz/cuRj1mt/95w == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrieefgddufedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefuvfhfhfhokffffgggjggtsehmtd erredtfeehnecuhfhrohhmpefrvghtvghrucfgihhsvghnthhrrghuthcuoehpvghtvghr rdgvihhsvghnthhrrghuthesvdhnughquhgrughrrghnthdrtghomheqnecuggftrfgrth htvghrnhepfffhteeuvdetlefgieelieduvdevgfehvddvgeeivdeigeetkeeivdevvddt teehnecuffhomhgrihhnpedvnhguqhhurggurhgrnhhtrdgtohhmnecukfhppeelfedrvd egfedriedrvdegudenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhl fhhrohhmpehpvghtvghrrdgvihhsvghnthhrrghuthesvdhnughquhgrughrrghnthdrtg homh X-ME-Proxy: Received: from april.pezone.net (p5df306f1.dip0.t-ipconnect.de [93.243.6.241]) by mail.messagingengine.com (Postfix) with ESMTPA id 3F7073065EDF; Wed, 29 Apr 2020 14:59:09 -0400 (EDT) Subject: Re: Rendering pi more nicely in PDF To: Tom Lane , pgsql-docs@lists.postgresql.org References: <10598.1587928415@sss.pgh.pa.us> From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: Date: Wed, 29 Apr 2020 20:59:07 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <10598.1587928415@sss.pgh.pa.us> Content-Type: multipart/mixed; boundary="------------D0194110BC97551D68DA6A7E" Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk This is a multi-part message in MIME format. --------------D0194110BC97551D68DA6A7E Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit On 2020-04-26 21:13, Tom Lane wrote: > "π" renders poorly in our PDF docs: as shown in the attached > screenshot, it doesn't line up on the baseline. I realized that > this is the same problem I'd run into recently with right-arrow, > and it can be solved in the same way, namely we have to specify > use of the symbol font explicitly. So attached is a proposed > patch to fix it. The real problem here is that the default font (Times or Times New Roman) embedded in PDF readers doesn't have these off-the-beaten-path glyphs. I'm surprised you see anything at all. The fix is to use a different font with more glyphs. I looked into that some time ago because this also effects the contributors list in the release notes, which has to be dumbed down because of this. To use a different font, you have to (a) pick one, and (b) install it locally when you build the PDFs. My proposal is to use the DejaVu fonts, which are open source and easily available for common operating systems. (Arguably, they also give the documentation a slightly fresher look.) The attached patch implements this. You just have to install the fonts somehow. Red Hat and Debian should have packages for this. We should write instructions for this in any case. (With this you can undo the other patches discussed here and just write π and it should look correctly.) -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services --------------D0194110BC97551D68DA6A7E Content-Type: text/plain; charset=UTF-8; x-mac-type="0"; x-mac-creator="0"; name="0001-FOP-font-configuration.patch" Content-Transfer-Encoding: 8bit Content-Disposition: attachment; filename="0001-FOP-font-configuration.patch"