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

Jean Mahoney <jmahoney@amsl.com> Wed, 24 August 2022 22:14 UTC

Return-Path: <jmahoney@amsl.com>
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 CAF96C14CF11 for <xml-sg-cmt@ietfa.amsl.com>; Wed, 24 Aug 2022 15:14:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 fR3ECFNijNaG for <xml-sg-cmt@ietfa.amsl.com>; Wed, 24 Aug 2022 15:14:29 -0700 (PDT)
Received: from c8a.amsl.com (c8a.amsl.com [4.31.198.40]) (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 0C6C9C14F74B for <xml-sg-cmt@ietf.org>; Wed, 24 Aug 2022 15:14:29 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id E8A9F4243EFA; Wed, 24 Aug 2022 15:14:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jhPXnnV462Sn; Wed, 24 Aug 2022 15:14:28 -0700 (PDT)
Received: from [192.168.1.203] (unknown [47.186.48.51]) by c8a.amsl.com (Postfix) with ESMTPSA id ADC5E4243EF9; Wed, 24 Aug 2022 15:14:28 -0700 (PDT)
Content-Type: multipart/alternative; boundary="------------b6yPlSx6CxdfaLXmsCNbC0UB"
Message-ID: <85d121a9-91a8-2d6b-e213-fcd200a97719@amsl.com>
Date: Wed, 24 Aug 2022 17:14:27 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.1.2
To: Sandy Ginoza <sginoza@amsl.com>, xml-sg-cmt@ietf.org
Cc: Jay Daley <jay@staff.ietf.org>
References: <5B2438DF-C64B-44C4-9CE2-1491D934793C@amsl.com>
Content-Language: en-US
From: Jean Mahoney <jmahoney@amsl.com>
In-Reply-To: <5B2438DF-C64B-44C4-9CE2-1491D934793C@amsl.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml-sg-cmt/aJlm2287XCI00ATBKReFKBZiWwg>
X-Mailman-Approved-At: Thu, 25 Aug 2022 06:09:51 -0700
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: Wed, 24 Aug 2022 22:14:32 -0000

Hi all,

Some more details below:

On 8/24/22 4:31 PM, 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
[JM] Setup: A <tr> has a combination of <td>s that contain either short 
or long text strings (whether the text is wrapped in <t/> doesn't seem 
to have any impact).

When the PDF is generated, one of these rows has a page break in the 
middle of it. The shorter strings are displayed at the top of the row 
(they "float" and are displayed on the first page) and the longer 
strings are displayed on the second page (they sorta "sink" onto the 
next page but not necessarily to the very bottom of the row):

    ...       |     |         |                  |        |Key Wrap w/  |
    |         |     |         |                  |        |256-bit key  |
    +---------+-----+---------+------------------+--------+-------------+
    |         |-32  |         | no               |A128KW  |             |

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ page break ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    +=========+=====+=========+==================+========+=============+
    |Name     |Value| KDF     | Ephemeral-Static |Key Wrap|Description  |
    +=========+=====+=========+==================+========+=============+
    |ECDH-SS +|     | HKDF -- |                  |        |ECDH SS w/   |
    |A128KW   |     | SHA-256 |                  |        |HKDF and AES |
    |         |     |         |                  |        |Key Wrap w/  |
    |         |     |         |                  |        |128-bit key  |
    +---------+-----+---------+------------------+--------+-------------+

If the <td>s contain text strings of equivalent length (either long or 
short), the page break ends up between rows and the text is displayed 
correctly within the row. For the following example, I just copy/pasted 
the longest line of text:

    ...       |     |         |                  |        |Key Wrap w/  |
    |         |     |         |                  |        |256-bit key  |
    +---------+-----+---------+------------------+--------+-------------+
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ page break ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    +=========+=====+=========+==================+========+=============+
    |Name     |Value| KDF     | Ephemeral-Static |Key Wrap|Description  |
    +=========+=====+=========+==================+========+=============+
    |ECDH ES|ECDH ES|ECDH ES | ECDH ES w/ HKDF  |ECDH ES  |ECDH ES w/   |
    |w/ HKDF|w/ HKDF|w/ HKDF | and AES Key Wrap |w/ HKDF  |HKDF and AES |
    |and AES|and AES|and AES | w/ 256-bit key   |and AES  |Key Wrap w/  |
    |Key    |Key    |Key Wrap|                  |Key Wrap |256-bit key  |
    |Wrap w/|Wrap w/|w/      |                  |w/       |             |
    |256-bit|256-bit|256-bit |                  |256-bit  |             |
    |key    |key    |key     |                  |key      |             |


Thanks!
Jean


>
> 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