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 1jTsql-0005BK-OJ for pgsql-docs@arkaria.postgresql.org; Wed, 29 Apr 2020 19:58:31 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jTsqk-0008NU-Gs for pgsql-docs@arkaria.postgresql.org; Wed, 29 Apr 2020 19:58:30 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jTsqk-0008NN-BG for pgsql-docs@lists.postgresql.org; Wed, 29 Apr 2020 19:58:30 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jTsqi-0004px-5C for pgsql-docs@lists.postgresql.org; Wed, 29 Apr 2020 19:58:29 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id 03TJwQjE025119; Wed, 29 Apr 2020 15:58:26 -0400 From: Tom Lane To: Peter Eisentraut cc: pgsql-docs@lists.postgresql.org Subject: Re: Rendering pi more nicely in PDF In-reply-to: References: <10598.1587928415@sss.pgh.pa.us> Comments: In-reply-to Peter Eisentraut message dated "Wed, 29 Apr 2020 20:59:07 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <25117.1588190306.1@sss.pgh.pa.us> Date: Wed, 29 Apr 2020 15:58:26 -0400 Message-ID: <25118.1588190306@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Peter Eisentraut writes: > 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. > 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. Well, I do ... > 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. I think making the built documentation depend on nonstandard fonts is a truly awful idea. It'd be okay perhaps if the requirement only applied to people building the docs, but won't the requirement also flow through to end users? regards, tom lane