Re: [Xml-sg-cmt] Odd table breaks (odd breaks within a row)

Kesara Rathnayake <kesara@staff.ietf.org> Thu, 25 August 2022 02:47 UTC

Return-Path: <kesara@staff.ietf.org>
X-Original-To: xml-sg-cmt@ietfa.amsl.com
Delivered-To: xml-sg-cmt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49157C1524C8 for <xml-sg-cmt@ietfa.amsl.com>; Wed, 24 Aug 2022 19:47:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MeyoIeCttjyZ for <xml-sg-cmt@ietfa.amsl.com>; Wed, 24 Aug 2022 19:47:31 -0700 (PDT)
Received: from ietfx.amsl.com (ietfx.amsl.com [50.223.129.196]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 229F8C1522CE for <xml-sg-cmt@ietf.org>; Wed, 24 Aug 2022 19:47:31 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by ietfx.amsl.com (Postfix) with ESMTP id 3E9A940FC7BF; Wed, 24 Aug 2022 19:47:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from ietfx.amsl.com ([50.223.129.196]) by localhost (ietfx.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v82AbSfy7NfK; Wed, 24 Aug 2022 19:47:30 -0700 (PDT)
Received: from [192.168.1.87] (122-58-124-12-vdsl.sparkbb.co.nz [122.58.124.12]) by ietfx.amsl.com (Postfix) with ESMTPSA id 3CCFE402AB38; Wed, 24 Aug 2022 19:47:29 -0700 (PDT)
Message-ID: <ec14e2d1-8406-cae3-b134-9e5c908bbd0e@staff.ietf.org>
Date: Thu, 25 Aug 2022 14:47:27 +1200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:104.0) Gecko/20100101 Thunderbird/104.0
Content-Language: en-NZ
To: Sandy Ginoza <sginoza@amsl.com>, xml-sg-cmt@ietf.org
Cc: Jay Daley <jay@staff.ietf.org>, Jean Mahoney <jmahoney@amsl.com>
References: <5B2438DF-C64B-44C4-9CE2-1491D934793C@amsl.com>
From: Kesara Rathnayake <kesara@staff.ietf.org>
Organization: IETF Administration LLC
In-Reply-To: <5B2438DF-C64B-44C4-9CE2-1491D934793C@amsl.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml-sg-cmt/aUlsVrFbbNHgAyOTQS6IJ6PFtE8>
Subject: Re: [Xml-sg-cmt] Odd table breaks (odd breaks within a row)
X-BeenThere: xml-sg-cmt@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Working list for the xml and style guide change management team <xml-sg-cmt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml-sg-cmt>, <mailto:xml-sg-cmt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml-sg-cmt/>
List-Post: <mailto:xml-sg-cmt@ietf.org>
List-Help: <mailto:xml-sg-cmt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml-sg-cmt>, <mailto:xml-sg-cmt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2022 02:47:34 -0000

Hi Sandy,

This is an issue on WeasyPrint.
I've already created a bug report [1].
I'll investigate if there's anything that can be done on xml2rfc to 
avoid this issue.

[1] https://github.com/Kozea/WeasyPrint/issues/1712

Cheers,
Kesara

On 25/08/22 9:31 am, Sandy Ginoza wrote:
> Hi all,
> 
> While prepping 2 docs for pub, we noticed a couple of odd table breaks in RFCs-to-be 9053 and 9054.  Some info within a row appears on one page, and some info in the same row appears on the next page.  Please see:
> 
> https://www.rfc-editor.org/authors/rfc9053.pdf
> Table 16 on pages 26-27
> 
> https://www.rfc-editor.org/authors/rfc9054.pdf
> Table 2 on pages 6 and 7
> 
> Is this something that can be fixed?  Is there some workaround here?  I imagine we’ll see this with some frequency.
> 
> FYI: These are Jim Schaad’s last documents (afaik).  There is *some* urgency to get these docs published in that they have been stuck in AUTH48 for over a year and were released for pub last week at the urging/override of the AD.  They have been delaying publication of another cluster for some time.
> 
> Thanks!
> Sandy

-- 
Kesara Rathnayake
Senior Software Development Engineer - IETF LLC
kesara@staff.ietf.org