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 1q0oT8-0001Ci-LS for pgsql-committers@arkaria.postgresql.org; Sun, 21 May 2023 19:11:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1q0oT7-0003WF-HK for pgsql-committers@arkaria.postgresql.org; Sun, 21 May 2023 19:11:49 +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 1q0oT7-0003Vc-7W for pgsql-committers@lists.postgresql.org; Sun, 21 May 2023 19:11:49 +0000 Received: from mail-pf1-x435.google.com ([2607:f8b0:4864:20::435]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1q0oT4-001DYT-3Y for pgsql-committers@lists.postgresql.org; Sun, 21 May 2023 19:11:48 +0000 Received: by mail-pf1-x435.google.com with SMTP id d2e1a72fcca58-64d341bdedcso1695974b3a.3 for ; Sun, 21 May 2023 12:11:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=j-davis-com.20221208.gappssmtp.com; s=20221208; t=1684696305; x=1687288305; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:to:from:subject:message-id:from:to:cc:subject:date :message-id:reply-to; bh=MtQQbdl/RWEbomQAlw1HgICOOshIs2ugnh3arjoRlnk=; b=pgUpUuJ1voQ6RmDmhU7J7vW63e38wUF/lOEhc7NApphjjznVBfLbubsWdtgMkh2MAQ +cxwworAcofYiiySWe6J0iKPdcv4DKm6Avb0NtzQqU6VihW0SASR43mYkPidmTVr/zpR CKbbXlCXRxS7H7/PFYYvDlCnVoPu8C0IOAT6Ww8Nfg2En5jykgbiriKLjJB/9Yty4cyd OiPUQR46ve68+JD4CgaSVqglR0lIwXbT9vtX+ghOPEfMW+TgQFEbTm1vIjsOuLb3MyRC AI/EE350BBt4MX3aS5zZyHvlt2clT4O9dYh3yqep+BIYCS8KkebIyGGIgXLi8NynCg7L spmQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684696305; x=1687288305; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:to:from:subject:message-id:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=MtQQbdl/RWEbomQAlw1HgICOOshIs2ugnh3arjoRlnk=; b=h/QLXG3w8tlvPOVA1u6x1tg44v4HLh9cTCzWTcSBB+hYoxdj4saKF0jIfi0D4f3bhr yvtmHm6oIs/6YStdfdXdgZNIZTTr+NfLMrjymzEdN+8M5U6zIYyC4+vFMaI3T/JR8URm CuWZdW1VSJX+nlFetTfQk5uFq78dq/d3QhYIlLyUjdLZMHGlISeg6zbWtCpDcJQDbLl8 kS2Lww39Gict7j5jbLfoRf2xxbXCYJMWcAL3RjIWCeHVwmV+NtKdv8eLh+7LOh+gQZ8w suVEkWQejuDfabDw3Yf9eDnrHCIn227G5l+6JN//XBVHruS7v6JdfxW0gd+mOFBqTQ4U 69wg== X-Gm-Message-State: AC+VfDxi0pZyJDDRgXlOwxyyp+g1P59hrsF6Lc56IebRTb4fRqwvXMHi Z+qJjsxvhUtUPYQRNRPS/QQUy+LQ1gETyF7932c= X-Google-Smtp-Source: ACHHUZ4OoWHgF5RpjiNp3zXHzi4sITMyKWXr0ymEfpXOB1qErzhF+hoSGmwFiJm4Heqx7xRdUXqELg== X-Received: by 2002:a05:6a00:1145:b0:648:ebb2:3d6 with SMTP id b5-20020a056a00114500b00648ebb203d6mr11522785pfm.26.1684696305027; Sun, 21 May 2023 12:11:45 -0700 (PDT) Received: from ?IPv6:2607:fb90:370e:4376:5839:981f:33df:c668? ([2607:fb90:370e:4376:5839:981f:33df:c668]) by smtp.gmail.com with ESMTPSA id n26-20020aa78a5a000000b0064d3881e687sm2864768pfa.35.2023.05.21.12.11.44 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 21 May 2023 12:11:44 -0700 (PDT) Message-ID: <2579c5a67a5302201a506234b6f78d79c6405351.camel@j-davis.com> Subject: Re: pgsql: Doc: fix some rendering problems in the PDF docs build. From: Jeff Davis To: Tom Lane , pgsql-committers@lists.postgresql.org Date: Sun, 21 May 2023 12:11:43 -0700 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.44.4-0ubuntu1 MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Sun, 2023-05-21 at 15:21 +0000, Tom Lane wrote: > Doc: fix some rendering problems in the PDF docs build. >=20 > Tweak column widths in a couple of tables to avoid "contents > ... exceed the available area" warnings.=C2=A0 Remove usage of > some non-Latin-1 characters. Thank you for taking care of this. 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. Regards, Jeff Davis