[Rswg] Re: Q: RFC policies / tooling for wide tables

Martin Thomson <mt@lowentropy.net> Mon, 08 July 2024 22:45 UTC

Return-Path: <mt@lowentropy.net>
X-Original-To: rswg@ietfa.amsl.com
Delivered-To: rswg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 033C4C180B68 for <rswg@ietfa.amsl.com>; Mon, 8 Jul 2024 15:45:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.107
X-Spam-Level:
X-Spam-Status: No, score=-7.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_HI=-5, 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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lowentropy.net header.b="SNsODX2o"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="fPUTmQq3"
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 Op3wxQuTAio7 for <rswg@ietfa.amsl.com>; Mon, 8 Jul 2024 15:45:38 -0700 (PDT)
Received: from fhigh4-smtp.messagingengine.com (fhigh4-smtp.messagingengine.com [103.168.172.155]) (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 88688C180B44 for <rswg@rfc-editor.org>; Mon, 8 Jul 2024 15:45:38 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailfhigh.nyi.internal (Postfix) with ESMTP id 8B24811402C0 for <rswg@rfc-editor.org>; Mon, 8 Jul 2024 18:45:37 -0400 (EDT)
Received: from imap41 ([10.202.2.91]) by compute6.internal (MEProxy); Mon, 08 Jul 2024 18:45:37 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm3; t=1720478737; x=1720565137; bh=/y34+XHGjX dp3d3OkzndKcMWuA2NGeOF3CeWFXsTjDI=; b=SNsODX2o1rjEbOGCentNmzZ75z oP5+FHcIIkgVnyUG+pCWCMpwnPDFxqQqE4DQXsm1N2g+t32v512AoOnkGopZLwXd AyAqykHiS7BF0drv+4zH2WrnCsLLt0Ol63iJ9adAXGoMZkOFyTnFZE9AGiyHap0y VahYOR0XtwQ/bn82/AUb6mlvpuT+4vpLxyCSwAQESbVoKyWlvsPAdslsdZeC8Af9 53r8WyqxAhXJG9Fvd1GTvM4Ho5hxHjLhNYmBtrPFpFiDuyl+ir6NlPdt6lwhdd1a 9ZQYTyZNwYK4SLJE12Eeft5grgQ9SWxzP8f98cu9ZZRtzS4A8+8PD2JM5dVg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; t=1720478737; x=1720565137; bh=/y34+XHGjXdp3d3OkzndKcMWuA2N GeOF3CeWFXsTjDI=; b=fPUTmQq3cg/49VafVYDybU7YScPYsZKu4/lZyO+GF7RJ 6mRfY+b/bYJq7sugcfLbzCYfCrVLJ5oHEJIT4N3VwKKUwT4NIYIK7MQoJ65yBfFp qri++zT33lGfksRit1j568/AwvpHVW0Jb8z4a5vKzFLaW6+Yhp1O/u1EGw0rPSZ7 sdZsfZCyifKcpqKst0+XnknFNyfmw8Vnro6+WCgq0Gy9JsPAE7FxmS4FmeTFXMVv nzLYwv1TLzvf++ihDH5G/BFOgvF17eY/V0AhcPBVVRO5KSc2dPkIC6xNW/qnQqkk /EBXOly25LAOxT3MTBkqg14op4yTvviagOEy2EmlFw==
X-ME-Sender: <xms:EWyMZkWeNEQbc6hQh2zVq2e9HofpyDYprRzuZeTCpJWCl_N-85MDuA> <xme:EWyMZol9K1blbMLidB0qRl7iK5276B8ZGw7bD_HHSzPhxmwxry2AW14W2MOsZxK4a gPXOFohU1X0ZGribkc>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeftddrvdekgddugecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesthdtre dtreertdenucfhrhhomhepfdforghrthhinhcuvfhhohhmshhonhdfuceomhhtsehlohif vghnthhrohhphidrnhgvtheqnecuggftrfgrthhtvghrnhephfeitddtveeihfejjefgve efuedugffgkeevkeehueeggeelveekveektdfhueeinecuffhomhgrihhnpehivghtfhdr ohhrghenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpe hmtheslhhofigvnhhtrhhophihrdhnvght
X-ME-Proxy: <xmx:EWyMZobh-UJgvNqDAMGdR4KsHxexUpQWUIuh8F44TnhtWMRJDls0Tg> <xmx:EWyMZjXWbmUdOCqnOVlfZOMbzYGAYF2zecs3vWSCtqYC8eTZ5qirlg> <xmx:EWyMZumWxG-pYQssTrTKhVLEXJsBwraCez2i4Umho7YpaC4AZEFoKg> <xmx:EWyMZocz_OPj7On6LTBeFNEd9T7Q7uhOPD1CShYL10dqpR6SNYfOkA> <xmx:EWyMZltp88_Jkxz-TT42JzejgSjcBtxLHIMid1S7g0XXAVw8f9H4kXld>
Feedback-ID: ic129442d:Fastmail
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 1AB732340081; Mon, 8 Jul 2024 18:45:37 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.11.0-alpha0-568-g843fbadbe-fm-20240701.003-g843fbadb
MIME-Version: 1.0
Message-Id: <95c1d932-f666-4c31-99af-f480d02537b4@betaapp.fastmail.com>
In-Reply-To: <Zos_KjVCroT4P6TP@faui48e.informatik.uni-erlangen.de>
References: <Zos_KjVCroT4P6TP@faui48e.informatik.uni-erlangen.de>
Date: Tue, 09 Jul 2024 08:45:16 +1000
From: Martin Thomson <mt@lowentropy.net>
To: rswg@rfc-editor.org
Content-Type: text/plain
Message-ID-Hash: EIP7IMGBFZR4RTDVWN6GOJLHFXPFW4GN
X-Message-ID-Hash: EIP7IMGBFZR4RTDVWN6GOJLHFXPFW4GN
X-MailFrom: mt@lowentropy.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Rswg] Re: Q: RFC policies / tooling for wide tables
List-Id: "RFC Series Working Group (RSWG)" <rswg.rfc-editor.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rswg/_6wJybBp8VTdopy6L_X4RxIXs6M>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rswg>
List-Help: <mailto:rswg-request@rfc-editor.org?subject=help>
List-Owner: <mailto:rswg-owner@rfc-editor.org>
List-Post: <mailto:rswg@rfc-editor.org>
List-Subscribe: <mailto:rswg-join@rfc-editor.org>
List-Unsubscribe: <mailto:rswg-leave@rfc-editor.org>

I don't know.  Those tables look pretty bad to me.  They overflow pretty badly for me.

Have you considered using definition lists instead?

On Mon, Jul 8, 2024, at 11:21, Toerless Eckert wrote:
> [ Hope this is the right list, else pls. help me to find a better one 
> (rfc-interest ?) ]
>
> I have a draft with tables that are impossible (for me) to format
> into 72 characters in txt output. HTML output on the other hand
> is IMHO fine.
>
> https://www.ietf.org/archive/id/draft-ietf-anima-brski-discovery-03.html
> (Tables 1,2,3)
>
> So i was wondering:
>
> Q1: Is it acceptable for RFCs to only have correct rendering of such
> tables in HTML, for example if the text format had some appropriate
> marking ("see HTML format for this table"). I remember that i have
> seen such notes for images, but not  tables.
>
> Q2: HTML does a better job fitting those tables not only because
> if effectively doesn't care about 72 characters, but also because
> it does do better auto-folding of cell content. I have written
> the doc in kramdown. I have not found any auto-folding for cells..
> maybe i am missing out on some option to improve the txt (even though
> i fear it wouldn't be enough anyhow). Especially Table 2. Or else,
> if manual folding is required, does RFC Editor have better tools
> after they've changed the draft to their full-RFC formatting ?
>
> Thanks a lot!
>     Toerless
>
> -- 
> rswg mailing list -- rswg@rfc-editor.org
> To unsubscribe send an email to rswg-leave@rfc-editor.org