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 1jTuBF-00008S-SY for pgsql-docs@arkaria.postgresql.org; Wed, 29 Apr 2020 21:23:45 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jTuBC-0007PI-Mx for pgsql-docs@arkaria.postgresql.org; Wed, 29 Apr 2020 21:23:42 +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 1jTuBC-0007Mj-Bd for pgsql-docs@lists.postgresql.org; Wed, 29 Apr 2020 21:23:42 +0000 Received: from mail-qk1-x743.google.com ([2607:f8b0:4864:20::743]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jTuB5-0005cV-AX for pgsql-docs@lists.postgresql.org; Wed, 29 Apr 2020 21:23:40 +0000 Received: by mail-qk1-x743.google.com with SMTP id b188so3626107qkd.9 for ; Wed, 29 Apr 2020 14:23:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=BK/uP6GsI2RH789D8UzZC5ZPZ8xi2saAuJHBLTTFQfQ=; b=pu9KeFGPd3LnL0aM7VG9pfd0Yz0wRcuKcsecdgxXgVhpJiT2AjEAoYD0ifX6nUk0fy yvO5VwTsYQAth2FNe9pTSr3WL6yfEwIuoPOEyS5bttMNfXVvbORBwBkS9rJK4pDIJaVG itet7AyWxDxWVmmJz8dtExlcgJD8UUHEYLNjbqEgqybgFIpJfw+Oi4avtAPilx4a4ZT4 OfuFZxKhnukrY7P38V34MMKwvNO2/Xzm1AKjakNzD0+xLM40ZqIhX3kmCEIRoY7plreF sqnnqZG0sFyu5nkLgiWVv4yE5bDLe8kc2QSQxl84Rr2oPWqO/3Y0DJqefO9W/ZGKmsf9 ZjNQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=BK/uP6GsI2RH789D8UzZC5ZPZ8xi2saAuJHBLTTFQfQ=; b=l0NlyJQBDW9IJhFU27osVrH3GRpG/wSLKhrp2WuMSm4rjrBh/UzswG9grdOvFNtsxK kE0bN5d5W1iwxnCHQKtZMovwDLBARH8Htg/m9OBy2fjTpisZqGXJqlRmXBO1RHSjnOML nM7pFGH3utPIUyO41Z/YDezKq8w0d0J2kZs44wNSmVeDiRhlTS8DzZlAq/DDWh4QOesT TutJnj7huduc3zV9gfgh8lVodROojLIjRDu8B2pxLXHKcppZXpc/VwiS5uwNadkwuImc gPDwPQpU+ixTmddxIsyDKA01b8c81zUlukiDjZPlVwzmK6neErfO26guvAnVPKGvVO9i s/aQ== X-Gm-Message-State: AGi0PuZgjZGyLGxOyCGC3mDY1RVf7wahipt+EEoeCrp7Vseupsa33szs lHNmm9j4QMn4TgQwdtWC8nzmmw== X-Google-Smtp-Source: APiQypJFMmn2/EYuRgiXL10+XIUVCMWrnhyElu6VljUaMKNjSU2sSGRJM2UllJw+hck4++p4Pwk5PQ== X-Received: by 2002:a05:620a:2013:: with SMTP id c19mr505212qka.162.1588195414217; Wed, 29 Apr 2020 14:23:34 -0700 (PDT) Received: from nimloth.alvh.no-ip.org ([190.95.18.252]) by smtp.gmail.com with ESMTPSA id h6sm333410qtd.79.2020.04.29.14.23.33 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 29 Apr 2020 14:23:33 -0700 (PDT) Received: by nimloth.alvh.no-ip.org (Postfix, from userid 1000) id D3BC0301604; Wed, 29 Apr 2020 17:23:31 -0400 (-04) Date: Wed, 29 Apr 2020 17:23:31 -0400 From: Alvaro Herrera To: Peter Eisentraut Cc: Tom Lane , pgsql-docs@lists.postgresql.org Subject: Re: Rendering pi more nicely in PDF Message-ID: <20200429212331.GA13762@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2020-Apr-29, Peter Eisentraut wrote: > 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. It's not easy to build the PDF with this. There's a stray > in fop.xml. After fixing that, I get a warning about fontbox java lib not being installed. OK, I can install libfontbox-java and that one disappears. Then there's this other warning: [warning] /usr/bin/fop: JVM flavor 'sun' not understood which seems to be innocuous. The build it still dies because of a CFF type1 something or other: Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/fontbox/cff/CFFType1Font at org.apache.fop.fonts.truetype.OTFFile.isType1(OTFFile.java:151) After a quick search I found this bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584472 which suggests that I patch /usr/bin/fop to find_jars in "fontbox2" instead of fontbox. OK, remove package libfontbox-java, patch the script, try again. Now it seems to work, and the doc looks pretty. But apparently it's not sufficient -- the new font is not used everywhere. For example footnotes seem to use a different font than the main body of text. (I altered the fontname to Gentium, which I like better, and uses a different glyph for "g" which is easy to spot ... and notably absent in footnote in page 5 under 1.4 Accessing a Database.) I +1 the idea of using a more complete font if it means we can render contributor names better, though :-) -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services