IETF Logo Mail Archive

Re: [xml2rfc-dev] --table-borders

Bob Briscoe <ietf@bobbriscoe.net> Thu, 03 February 2022 02:06 UTC

Return-Path: <ietf@bobbriscoe.net>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 677253A137E for <xml2rfc-dev@ietfa.amsl.com>; Wed, 2 Feb 2022 18:06:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.812
X-Spam-Level:
X-Spam-Status: No, score=-2.812 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, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.714, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=bobbriscoe.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sIHR6WPzPhID for <xml2rfc-dev@ietfa.amsl.com>; Wed, 2 Feb 2022 18:06:47 -0800 (PST)
Received: from mail-ssdrsserver2.hostinginterface.eu (mail-ssdrsserver2.hostinginterface.eu [185.185.85.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0CB1B3A137D for <xml2rfc-dev@ietf.org>; Wed, 2 Feb 2022 18:06:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bobbriscoe.net; s=default; h=In-Reply-To:Cc:From:References:To:Subject: MIME-Version:Date:Message-ID:Content-Type:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=z1W7BLQgBkx0HdtHklfJNDur97kWVtbp43rkX0CRKBk=; b=D6v/IWOKsYQPRP3f7sBakI9hUP JUoLPd4OdJ68GFH6SUUi1JPKdyxWuyT5qKY6JVk5gQrn5Azh15dYY2zxXW5W2zxRPLkv/CvDU1in5 G3BrS8V3taGIDL+tkOqVSoxLWKcXDGYOUg5SEzB+fCi2HEQOUQMk09hJDRzTSvPUWaqhuH1aV6CGI sLDZTlwo2sqk36ppCu29XhFACNmS0GVyKzIvT7abQSHB/sN97Q4mu6LQza9N47/0M1wW5Wpuu2Vpb KAL51YVihhfPvxImSuLsJvS00IVTl6Sn93MhJ1Y2jmAhui98WoQStSluf2iMi4j7JDJ+TZ7MLdXbw 0F/zXjNw==;
Received: from 67.153.238.178.in-addr.arpa ([178.238.153.67]:55068 helo=[192.168.1.11]) by ssdrsserver2.hostinginterface.eu with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from <ietf@bobbriscoe.net>) id 1nFRWM-0005B2-W9; Thu, 03 Feb 2022 02:06:44 +0000
Content-Type: multipart/alternative; boundary="------------YSDpSkchR5U1FjewURC8QTlZ"
Message-ID: <8d748cd3-1f80-aac7-c127-0791299e6a99@bobbriscoe.net>
Date: Thu, 03 Feb 2022 02:06:43 +0000
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0
Content-Language: en-GB
To: Robert Sparks <rjsparks@nostrum.com>
References: <Ye/CSVZZnKrN+T2K@miek.nl> <cf002966-48ee-06b3-cc60-e52a865743b3@staff.ietf.org> <33F0F5FB-5CBC-4D6D-BFB7-18AC9798C720@ietf.org> <997C8D93-EF22-42D3-A0A4-9C04EDAEF464@tzi.org> <1ee39a65-68e7-6388-fa6d-6364ff546751@nostrum.com> <ABB698C6-813A-4BE8-B009-26DEDBEFD08F@amsl.com> <d4d663c1-b453-7fa8-7179-3094c1c98158@nostrum.com>
From: Bob Briscoe <ietf@bobbriscoe.net>
Cc: xml2rfc-dev@ietf.org
In-Reply-To: <d4d663c1-b453-7fa8-7179-3094c1c98158@nostrum.com>
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - ssdrsserver2.hostinginterface.eu
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - bobbriscoe.net
X-Get-Message-Sender-Via: ssdrsserver2.hostinginterface.eu: authenticated_id: in@bobbriscoe.net
X-Authenticated-Sender: ssdrsserver2.hostinginterface.eu: in@bobbriscoe.net
X-Source:
X-Source-Args:
X-Source-Dir:
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/xnV6JdJBtdRPUGNexHFaLxYH0AA>
Subject: Re: [xml2rfc-dev] --table-borders
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Feb 2022 02:06:53 -0000

Robert,

Coincidentally, I was just about to mail this list to ask about table 
borders when I saw this recent thread.

Q1. Is it possible to render an rfc xml v3 table with no horizontal 
borders except at a transition between header and body and at the 
top/bottom?
Example of what I'm looking for: Table 2 here: 
https://datatracker.ietf.org/doc/html/draft-ietf-tcpm-accurate-ecn-15#section-3.1.2 
which was produced with v2 xml.

Q2. Is this table borders option you mention now supported? And if so, 
is it available in the code running at 
https://xml2rfc.tools.ietf.org/experimental.html ?
And what is the syntax, or where is it documented?

Guessing from what Henrik wrote in the ticket ( 
https://trac.ietf.org/trac/xml2rfc/ticket/527 ) it sounds like the 
mapping from v2 texttable style attribute to these v3 table borders is 
approximately as tabulated below (* = default):

v2	v3
---------------
all	full*
full*	light
headers	minimal
none	n/a?

If I'm right, I'm looking for how to use the 'light' border format.



Bob

On 28/01/2022 19:38, Robert Sparks wrote:
>
> On 1/28/22 1:22 PM, Alice Russo wrote:
>>> On Jan 26, 2022, at 2:48 PM, Robert Sparks <rjsparks@nostrum.com> 
>>> wrote:
>>>
>>>> Somebody wanted the —table-borders feature, or it wouldn’t have 
>>>> been implemented.
>>> The RPC asked Henrik to implement it as an experiment for a 
>>> document, and it ended up not being used.
>> To clarify, I submitted this ticket 
>> (https://trac.ietf.org/trac/xml2rfc/ticket/527), and -- in addition 
>> to the corresponding fix -- the table-borders option was created. 
>> IIRC, the RPC did not ask for the feature.
> Thanks for the clarification and apologies for my misrepresentation.
>>
>> As noted, it has never been used for producing an RFC.
>>
>> Thanks,
>> Alice
>> _______________________________________________
>> xml2rfc-dev mailing list
>> xml2rfc-dev@ietf.org
>> https://www.ietf.org/mailman/listinfo/xml2rfc-dev
>
> _______________________________________________
> xml2rfc-dev mailing list
> xml2rfc-dev@ietf.org
> https://www.ietf.org/mailman/listinfo/xml2rfc-dev

-- 
________________________________________________________________
Bob Briscoehttp://bobbriscoe.net/

v2.23.0 | Report a Bug | By Email