IETF Logo Mail Archive

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

Robert Sparks <rjsparks@nostrum.com> Fri, 28 January 2022 19:38 UTC

Return-Path: <rjsparks@nostrum.com>
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 6BA1C3A0E17 for <xml2rfc-dev@ietfa.amsl.com>; Fri, 28 Jan 2022 11:38:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.793
X-Spam-Level:
X-Spam-Status: No, score=-2.793 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, NICE_REPLY_A=-0.714, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.com
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 pH6XLLzIc11v for <xml2rfc-dev@ietfa.amsl.com>; Fri, 28 Jan 2022 11:38:49 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7337B3A0E13 for <xml2rfc-dev@ietf.org>; Fri, 28 Jan 2022 11:38:49 -0800 (PST)
Received: from [192.168.1.114] ([47.186.48.51]) (authenticated bits=0) by nostrum.com (8.17.1/8.16.1) with ESMTPSA id 20SJcj2t056060 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Fri, 28 Jan 2022 13:38:46 -0600 (CST) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1643398726; bh=9hrBftRFvNN46BOLkBSsyDYABoWHLL60Y6QWI5ml8GE=; h=Date:Subject:To:References:From:In-Reply-To; b=tLxAp0uq5JPNEx6RpwcPzfNo2LwMJumzDt8B6Hufm5ULBUW6QiNc46iJ9StqEZ+m0 M6Lgsm4hoq9AQFACi5/qayoX/AxsugqF0/t1VfTuu6Y+nfZkRypR8mUQN57FTpcddb gJU2yhgXPq3Znt4p8bImrDMWAkIY0X8InrFzVu7o=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.48.51] claimed to be [192.168.1.114]
Message-ID: <d4d663c1-b453-7fa8-7179-3094c1c98158@nostrum.com>
Date: Fri, 28 Jan 2022 13:38:40 -0600
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.5.1
Content-Language: en-US
To: Alice Russo <arusso@amsl.com>, xml2rfc-dev@ietf.org
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>
From: Robert Sparks <rjsparks@nostrum.com>
In-Reply-To: <ABB698C6-813A-4BE8-B009-26DEDBEFD08F@amsl.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/sfXFi7LUIhU0QBhMP5TgMAyScUo>
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: Fri, 28 Jan 2022 19:38:54 -0000

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

v2.23.0 | Report a Bug | By Email