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 1q0pIa-0003nq-IQ for pgsql-committers@arkaria.postgresql.org; Sun, 21 May 2023 20:05:00 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1q0pIZ-0005Vv-Dc for pgsql-committers@arkaria.postgresql.org; Sun, 21 May 2023 20:04:59 +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 1q0pIZ-0005Vm-60 for pgsql-committers@lists.postgresql.org; Sun, 21 May 2023 20:04:59 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1q0pIS-0014kE-Mh for pgsql-committers@lists.postgresql.org; Sun, 21 May 2023 20:04:58 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 34LK4pHn398397; Sun, 21 May 2023 16:04:51 -0400 From: Tom Lane To: Jeff Davis cc: pgsql-committers@lists.postgresql.org Subject: Re: pgsql: Doc: fix some rendering problems in the PDF docs build. In-reply-to: <2579c5a67a5302201a506234b6f78d79c6405351.camel@j-davis.com> References: <2579c5a67a5302201a506234b6f78d79c6405351.camel@j-davis.com> Comments: In-reply-to Jeff Davis message dated "Sun, 21 May 2023 12:11:43 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <398395.1684699491.1@sss.pgh.pa.us> Date: Sun, 21 May 2023 16:04:51 -0400 Message-ID: <398396.1684699491@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Jeff Davis writes: > Aside from the formatting issue, I included some non-ascii characters > in the documentation. Are those OK, or should I replace them with &# > sequences, or find some way to not use such characters at all? > I see a few places with such non-ASCII characters, but only a few, so > it's possible those are mistakes. The PDF toolchain can cope with ISO-8859-1 (Latin-1) characters, so it's not problematic to use those. I'm not seeing any complaints from the current build. regards, tom lane