From nobody Tue Feb 1 09:56:00 2022 Return-Path: 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 103193A1830; Tue, 1 Feb 2022 09:55:47 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7.08 X-Spam-Level: X-Spam-Status: No, score=-7.08 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, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] 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 X1YkDjhDmAVq; Tue, 1 Feb 2022 09:55:43 -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 E49013A1833; Tue, 1 Feb 2022 09:55:42 -0800 (PST) Received: from 3aeb60095bf8 ([47.186.48.51]) (authenticated bits=0) by nostrum.com (8.17.1/8.16.1) with ESMTPSA id 211Htdi9071133 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 1 Feb 2022 11:55:39 -0600 (CST) (envelope-from rjsparks@nostrum.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1643738139; bh=2etf1w9+7Uj4Gm+djJcX7GaVAczm1yVwbnJ5eZkZiNk=; h=From:To:Subject:Cc:Date; b=NLAa/ENFfh3sUQegffPM8+4sBDUo8IBFA2yDTDIrdMZOVmbZiMJsbyzx7dwOMCOOj RiN27zZKF3YKxFCuwbKzOaSiK/xfh1oc4TcDPytjsiNHvliCxyk24SUUmZ1B/0SXwL BVldB/LP7I+zDrU+nkxpPM6+wdX1cg4UuUv92Feo= X-Authentication-Warning: raven.nostrum.com: Host [47.186.48.51] claimed to be 3aeb60095bf8 Received: from rjsparks by 3aeb60095bf8 with local (Exim 4.92) (envelope-from ) id 1nExNN-00018k-S4; Tue, 01 Feb 2022 17:55:33 +0000 From: rjsparks@nostrum.com To: xml2rfc-dev@ietf.org, xml2rfc@ietf.org Cc: rfc-markdown@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Message-Id: Date: Tue, 01 Feb 2022 17:55:33 +0000 Archived-At: Subject: [xml2rfc-dev] New xml2rfc release: v3.12.1 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Feb 2022 17:55:47 -0000 Hi, This is an automatic notification about a new xml2rfc release, v3.12.1, generated when running the mkrelease script. Release notes: xml2rfc (3.12.1) ietf; urgency=high * Merged in [4090] from krathnayake@ietf.org: Improve local file lookup: Add source directory to the allowed list, Disallow any files that are on child directories of the source directory, Add a warning when including .ent files. Fixes #703. * Merged in [4089] from krathnayake@ietf.org: Update bibxml subdirectories list. Fixes #701. * Merged in [4088] from krathnayake@ietf.org: Fixes manpage generation issue. Fixes #694. -- Robert Sparks 01 Feb 2022 17:29:53 +0000 The preferred way to install xml2rfc is by doing 'pip install xml2rfc', and 'pip install --upgrade xml2rfc' to upgrade. If there are system- installed python modules which pip will not upgrade, you may have to use 'pip install --upgrade --no-deps xml2rfc' and install dependencies manually. The new version is also available through SVN checkout, with 'svn checkout https://svn.ietf.org/svn/tools/xml2rfc/tags/cli/3.12.1' Documentation for this release is built-in, and also available at: https://xml2rfc.tools.ietf.org/xml2rfc-doc-3.12.1.html Regards, Robert Sparks (via the mkrelease script) From nobody Wed Feb 2 10:38:26 2022 Return-Path: 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 10B5C3A19D0; Wed, 2 Feb 2022 10:38:12 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.097 X-Spam-Level: X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 sWqhUk2OyUT0; Wed, 2 Feb 2022 10:38:06 -0800 (PST) Received: from mail-ot1-x32c.google.com (mail-ot1-x32c.google.com [IPv6:2607:f8b0:4864:20::32c]) (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 BFA323A19C0; Wed, 2 Feb 2022 10:38:06 -0800 (PST) Received: by mail-ot1-x32c.google.com with SMTP id n6-20020a9d6f06000000b005a0750019a7so285199otq.5; Wed, 02 Feb 2022 10:38:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:mime-version:subject:message-id:date:cc:to; bh=kSlVcuf8pO/6YX1NzCgypqrrlJrcZmA6eV1Y1G+wAqE=; b=GBrF2SmcgmuF+bKbJabVlw0qsSGcjEXAHP54gtVt0Td4L1AWegWC0baQcvm9OuDmy6 prIYlswfPbu+znYnr+0mncNKyKX6VYfr6pFprAt75b+WFO18ELt/oL6yaqQ/pvMJCLCY JSj3KRx/qEHMpEFUwgYi8tBJNAcmIoZGNspaV3tf41AIX2ASDh5QTx334FQ/BSk2e1OS pkm8pWQeTBuaxJvjHUF1RbvVprjMnRdn+zqFxXXXhW4O8arF4gg4EDSZarYMJfneUPYB uhOrJDhpqARFaTUu4tHWkRq0soxXEw4y7A9GtLbuQLmbjlXasUo9ZCF17ggcBJmNax+v ZMew== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:mime-version:subject:message-id:date:cc:to; bh=kSlVcuf8pO/6YX1NzCgypqrrlJrcZmA6eV1Y1G+wAqE=; b=oKJ7tos2wXGlJ1545+Z1M6Wt/zeoxIfSltqSpyMPqxC1Wk9OTMoC1CNU5wCMPMMVxY qMU02S68A9WGz3eF7teGBUxSu87lic0O7oXHKi+j1RfTFNAzOmPqHtZEKLyOI26roEU2 lplqXHrlB3Uaw0WqDcon7/Ukaf3Ka+nJKSAkGgHTg4FUNQxPGYu2g0Wb8BJgHcE1qEJK gLr61GN5SAnQt1jbH6cgmNXfcdxig5QiAEppBDoOV7IEoV4iaMb69vdH2png4IhHkr6Z IDRuy/WltMQQmrKwFdUoWAe2/Ei6jYq3ERNI+suqDRu2VrGl6NoJ/d93h5dzMVNJ7kf9 ZeGQ== X-Gm-Message-State: AOAM533UyJAJHN0qFGVJRN2opycoN8JW9mTmZD1RbkTccSq/Adptdq0o SwTq/cV2JPYnNNCXD1+cjUVbXZbWA88= X-Google-Smtp-Source: ABdhPJztU0cY6+YtQ10mfsmjLFfMa0v4lTHqPyKqRvhueOUYGhfMuHFffBjcqjZ0RP0HcGP4bY0sMQ== X-Received: by 2002:a9d:4c0f:: with SMTP id l15mr17203292otf.104.1643827084917; Wed, 02 Feb 2022 10:38:04 -0800 (PST) Received: from smtpclient.apple (adsl-70-234-233-187.dsl.rcsntx.sbcglobal.net. [70.234.233.187]) by smtp.gmail.com with ESMTPSA id f21sm15637060otq.4.2022.02.02.10.38.04 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 02 Feb 2022 10:38:04 -0800 (PST) From: Mahesh Jethanandani Content-Type: multipart/alternative; boundary="Apple-Mail=_DC662575-1E05-4212-A414-1713D0300911" Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\)) Message-Id: <0567AF8D-9EC1-4DF8-B5B8-66B967C59B2E@gmail.com> Date: Wed, 2 Feb 2022 10:38:03 -0800 Cc: xml2rfc@ietf.org To: xml2rfc-dev@ietf.org X-Mailer: Apple Mail (2.3654.120.0.1.13) Archived-At: Subject: [xml2rfc-dev] Warning messages - How to address? 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Feb 2022 18:38:20 -0000 --Apple-Mail=_DC662575-1E05-4212-A414-1713D0300911 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii I am seeing the following warning messages using the latest version of = xml2rfc (3.12.1). Do not know how to address them. Can anyone help? = Thanks. % xml2rfc draft-ietf-netconf-https-notif-09.xml -o = draft-ietf-netconf-https-notif-09.txt --text Warning: = /usr/local/lib/python3.8/dist-packages/xml2rfc/templates/rfc2629-xhtml.ent= is no longer needed as the special processing of non-ASCII characters = has been superseded by direct support for non-ASCII characters in = RFCXML. Warning: = /usr/local/lib/python3.8/dist-packages/xml2rfc/templates/rfc2629-other.ent= is no longer needed as the special processing of non-ASCII characters = has been superseded by direct support for non-ASCII characters in = RFCXML. Warning: = /usr/local/lib/python3.8/dist-packages/xml2rfc/templates/rfc2629-xhtml.ent= is no longer needed as the special processing of non-ASCII characters = has been superseded by direct support for non-ASCII characters in = RFCXML. Warning: = /usr/local/lib/python3.8/dist-packages/xml2rfc/templates/rfc2629-other.ent= is no longer needed as the special processing of non-ASCII characters = has been superseded by direct support for non-ASCII characters in = RFCXML. Warning: = /usr/local/lib/python3.8/dist-packages/xml2rfc/templates/rfc2629-xhtml.ent= is no longer needed as the special processing of non-ASCII characters = has been superseded by direct support for non-ASCII characters in = RFCXML. Warning: = /usr/local/lib/python3.8/dist-packages/xml2rfc/templates/rfc2629-other.ent= is no longer needed as the special processing of non-ASCII characters = has been superseded by direct support for non-ASCII characters in = RFCXML. Warning: = /usr/local/lib/python3.8/dist-packages/xml2rfc/templates/rfc2629-xhtml.ent= is no longer needed as the special processing of non-ASCII characters = has been superseded by direct support for non-ASCII characters in = RFCXML. Warning: = /usr/local/lib/python3.8/dist-packages/xml2rfc/templates/rfc2629-other.ent= is no longer needed as the special processing of non-ASCII characters = has been superseded by direct support for non-ASCII characters in = RFCXML. Mahesh Jethanandani mjethanandani@gmail.com --Apple-Mail=_DC662575-1E05-4212-A414-1713D0300911 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii I = am seeing the following warning messages using the latest version of = xml2rfc (3.12.1). Do not know how to address them. Can anyone help? = Thanks.

% xml2rfc draft-ietf-netconf-https-notif-09.xml -o = draft-ietf-netconf-https-notif-09.txt --text
Warning:= = /usr/local/lib/python3.8/dist-packages/xml2rfc/templates/rfc2629-xhtml.ent= is no longer needed as the special processing of non-ASCII characters = has been superseded by direct support for non-ASCII characters in = RFCXML.
Warning: = /usr/local/lib/python3.8/dist-packages/xml2rfc/templates/rfc2629-other.ent= is no longer needed as the special processing of non-ASCII characters = has been superseded by direct support for non-ASCII characters in = RFCXML.
Warning: = /usr/local/lib/python3.8/dist-packages/xml2rfc/templates/rfc2629-xhtml.ent= is no longer needed as the special processing of non-ASCII characters = has been superseded by direct support for non-ASCII characters in = RFCXML.
Warning: = /usr/local/lib/python3.8/dist-packages/xml2rfc/templates/rfc2629-other.ent= is no longer needed as the special processing of non-ASCII characters = has been superseded by direct support for non-ASCII characters in = RFCXML.
Warning: = /usr/local/lib/python3.8/dist-packages/xml2rfc/templates/rfc2629-xhtml.ent= is no longer needed as the special processing of non-ASCII characters = has been superseded by direct support for non-ASCII characters in = RFCXML.
Warning: = /usr/local/lib/python3.8/dist-packages/xml2rfc/templates/rfc2629-other.ent= is no longer needed as the special processing of non-ASCII characters = has been superseded by direct support for non-ASCII characters in = RFCXML.
Warning: = /usr/local/lib/python3.8/dist-packages/xml2rfc/templates/rfc2629-xhtml.ent= is no longer needed as the special processing of non-ASCII characters = has been superseded by direct support for non-ASCII characters in = RFCXML.
Warning: = /usr/local/lib/python3.8/dist-packages/xml2rfc/templates/rfc2629-other.ent= is no longer needed as the special processing of non-ASCII characters = has been superseded by direct support for non-ASCII characters in = RFCXML.

Mahesh = Jethanandani
mjethanandani@gmail.com






= --Apple-Mail=_DC662575-1E05-4212-A414-1713D0300911-- From nobody Wed Feb 2 11:15:26 2022 Return-Path: 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 A3B9D3A1C8E; Wed, 2 Feb 2022 11:15:24 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.899 X-Spam-Level: X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no 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 1Bz2HKIikCBX; Wed, 2 Feb 2022 11:15:20 -0800 (PST) Received: from ietfx.ietf.org (ietfx.amsl.com [4.31.198.45]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1CEB43A1C8B; Wed, 2 Feb 2022 11:15:20 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by ietfx.amsl.com (Postfix) with ESMTP id E935E4113627; Wed, 2 Feb 2022 11:15:19 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com Received: from ietfx.ietf.org ([4.31.198.45]) by localhost (ietfx.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gnC6tG33zHih; Wed, 2 Feb 2022 11:15:19 -0800 (PST) Received: from smtpclient.apple (unknown [158.140.230.105]) by ietfx.amsl.com (Postfix) with ESMTPSA id 3EC8D4113625; Wed, 2 Feb 2022 11:15:19 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.40.0.1.81\)) From: Jay Daley In-Reply-To: <0567AF8D-9EC1-4DF8-B5B8-66B967C59B2E@gmail.com> Date: Thu, 3 Feb 2022 08:15:15 +1300 Cc: xml2rfc-dev@ietf.org, xml2rfc@ietf.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <0567AF8D-9EC1-4DF8-B5B8-66B967C59B2E@gmail.com> To: Mahesh Jethanandani X-Mailer: Apple Mail (2.3693.40.0.1.81) Archived-At: Subject: Re: [xml2rfc-dev] Warning messages - How to address? 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Feb 2022 19:15:25 -0000 Hi Mahesh The tl;dr is that you do not need the DOCTYPE statement that includes a = .ent file. Read = https://authors.ietf.org/en/templates-and-schemas#character-entities for = a fuller explanation. Jay > On 3/02/2022, at 7:38 AM, Mahesh Jethanandani = wrote: >=20 > I am seeing the following warning messages using the latest version of = xml2rfc (3.12.1). Do not know how to address them. Can anyone help? = Thanks. >=20 > % xml2rfc draft-ietf-netconf-https-notif-09.xml -o = draft-ietf-netconf-https-notif-09.txt --text > Warning: = /usr/local/lib/python3.8/dist-packages/xml2rfc/templates/rfc2629-xhtml.ent= is no longer needed as the special processing of non-ASCII characters = has been superseded by direct support for non-ASCII characters in = RFCXML. > Warning: = /usr/local/lib/python3.8/dist-packages/xml2rfc/templates/rfc2629-other.ent= is no longer needed as the special processing of non-ASCII characters = has been superseded by direct support for non-ASCII characters in = RFCXML. > Warning: = /usr/local/lib/python3.8/dist-packages/xml2rfc/templates/rfc2629-xhtml.ent= is no longer needed as the special processing of non-ASCII characters = has been superseded by direct support for non-ASCII characters in = RFCXML. > Warning: = /usr/local/lib/python3.8/dist-packages/xml2rfc/templates/rfc2629-other.ent= is no longer needed as the special processing of non-ASCII characters = has been superseded by direct support for non-ASCII characters in = RFCXML. > Warning: = /usr/local/lib/python3.8/dist-packages/xml2rfc/templates/rfc2629-xhtml.ent= is no longer needed as the special processing of non-ASCII characters = has been superseded by direct support for non-ASCII characters in = RFCXML. > Warning: = /usr/local/lib/python3.8/dist-packages/xml2rfc/templates/rfc2629-other.ent= is no longer needed as the special processing of non-ASCII characters = has been superseded by direct support for non-ASCII characters in = RFCXML. > Warning: = /usr/local/lib/python3.8/dist-packages/xml2rfc/templates/rfc2629-xhtml.ent= is no longer needed as the special processing of non-ASCII characters = has been superseded by direct support for non-ASCII characters in = RFCXML. > Warning: = /usr/local/lib/python3.8/dist-packages/xml2rfc/templates/rfc2629-other.ent= is no longer needed as the special processing of non-ASCII characters = has been superseded by direct support for non-ASCII characters in = RFCXML. >=20 > Mahesh Jethanandani > mjethanandani@gmail.com >=20 >=20 >=20 >=20 >=20 >=20 > _______________________________________________ > xml2rfc-dev mailing list > xml2rfc-dev@ietf.org > https://www.ietf.org/mailman/listinfo/xml2rfc-dev --=20 Jay Daley IETF Executive Director exec-director@ietf.org From nobody Wed Feb 2 18:06:54 2022 Return-Path: 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 ; 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 ; 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 ; 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 ) 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, 3 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 References: <33F0F5FB-5CBC-4D6D-BFB7-18AC9798C720@ietf.org> <997C8D93-EF22-42D3-A0A4-9C04EDAEF464@tzi.org> <1ee39a65-68e7-6388-fa6d-6364ff546751@nostrum.com> From: Bob Briscoe Cc: xml2rfc-dev@ietf.org In-Reply-To: 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: 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Feb 2022 02:06:53 -0000 This is a multi-part message in MIME format. --------------YSDpSkchR5U1FjewURC8QTlZ Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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 >>> 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/ --------------YSDpSkchR5U1FjewURC8QTlZ Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 Briscoe                               http://bobbriscoe.net/
--------------YSDpSkchR5U1FjewURC8QTlZ-- From nobody Wed Feb 2 18:49:21 2022 Return-Path: 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 D38B13A1542 for ; Wed, 2 Feb 2022 18:49:20 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7.099 X-Spam-Level: X-Spam-Status: No, score=-7.099 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, 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 MonpW37jfGGZ for ; Wed, 2 Feb 2022 18:49:16 -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 2136D3A1540 for ; Wed, 2 Feb 2022 18:49:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bobbriscoe.net; s=default; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:References:Cc:To:From:Subject:MIME-Version:Date:Message-ID:Sender :Reply-To: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=D7l4JumtZIH7netkid3Z2Qg2E+52Zycyv7ALVHO65hQ=; b=d3husyeooUPMPz/TRrLXVprkcn 1zxdz1JuB2aoOEY71+B2STV1jgcUAwLtqcvrVkp/YT4ecz0Etqkge2kOK5zrUCU0eTcN3sHLihe9n tn26fYp7KIiYC4kocv6u1UZC96k2VHYIi+RlRl17HEzgBFTsRdgTuWxkDZJYzb5sUdaJHcgMGhLm2 3rLlNRiF6aOTtNOrDLr+A1oEGT0xrQTrJbbHBEGZGCLI/sndLAgd9tbuoVrvWnffDh1p2blOkgIT5 KdC6eG25qlTqT2i0drnxd3MENIyT2BmLo+xs6qjt602FPeTqmvE2GQPDZUPB6KcDLAPsXLT9rj5vv Xxy08IiQ==; Received: from 67.153.238.178.in-addr.arpa ([178.238.153.67]:55070 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 ) id 1nFSBS-0002mF-Ot; Thu, 03 Feb 2022 02:49:12 +0000 Message-ID: <136ddd96-42a9-1e42-02a0-5ee4ea9bc2a2@bobbriscoe.net> Date: Thu, 3 Feb 2022 02:49:11 +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 From: Bob Briscoe To: Robert Sparks Cc: xml2rfc-dev@ietf.org References: <33F0F5FB-5CBC-4D6D-BFB7-18AC9798C720@ietf.org> <997C8D93-EF22-42D3-A0A4-9C04EDAEF464@tzi.org> <1ee39a65-68e7-6388-fa6d-6364ff546751@nostrum.com> <8d748cd3-1f80-aac7-c127-0791299e6a99@bobbriscoe.net> In-Reply-To: <8d748cd3-1f80-aac7-c127-0791299e6a99@bobbriscoe.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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: Subject: [xml2rfc-dev] tables with no caption 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Feb 2022 02:49:21 -0000 Robert, With v3 rfc xml, is it possible to render a table (or figure) without any caption at all? An example of what I'm trying to achieve: This IANA section using v2 rfc xml: https://datatracker.ietf.org/doc/html/draft-ietf-tcpm-accurate-ecn-15#section-7 With v2 rfc xml, tables or figures with no anchor or title were automatically not given a number or caption. But with v3, one gets a caption saying, say, 'Table 5' on its own. Thx in advance. Bob PS. Here are other similar examples of tables in IANA sections without a caption - they predate rfc xml     https://www.rfc-editor.org/rfc/rfc5304.html#section-4     https://datatracker.ietf.org/doc/html/rfc2474#section-6 -- ________________________________________________________________ Bob Briscoe http://bobbriscoe.net/ From nobody Wed Feb 2 23:32:17 2022 Return-Path: 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 60B293A20D9; Wed, 2 Feb 2022 23:32:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 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_BLOCKED=0.001, 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 (1024-bit key) header.d=eggert.org 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 WZVAr5AUlSd0; Wed, 2 Feb 2022 23:32:12 -0800 (PST) Received: from mail.eggert.org (mail.eggert.org [91.190.195.94]) (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 181483A20D5; Wed, 2 Feb 2022 23:32:11 -0800 (PST) Received: from smtpclient.apple (unknown [IPv6:2a00:ac00:4000:400:54fa:be87:1e8d:ffae]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id 733C91D4113; Thu, 3 Feb 2022 09:31:55 +0200 (EET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1643873515; bh=NRfCaRthGp5hq/tzvyyFmT/wLRFpqZUi6xgkvw9SjAo=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=xtigYYnzxnsy7Jxegq0Ien6Y3auc90qelU0S2edjD0gwzAtM8xVlX9iMibwHbHWaD Nz+ddSrUM6pfwpoWIzieTOOvlA+wGnhFkTmmhArm7lFHBXH9rstKPrY5mOYPnOSqm3 z1pp1TYlHCp606k5ttH2qpSHJmwyjib2hcDBMfJk= Content-Type: multipart/signed; boundary="Apple-Mail=_0050CE67-EC08-4E37-AEAD-A33A565DB5D0"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\)) From: Lars Eggert In-Reply-To: Date: Thu, 3 Feb 2022 09:31:55 +0200 Cc: Mahesh Jethanandani , xml2rfc@ietf.org, xml2rfc-dev@ietf.org Message-Id: <3E165089-0560-435F-A1F7-38D24A4E5D65@eggert.org> References: <0567AF8D-9EC1-4DF8-B5B8-66B967C59B2E@gmail.com> To: Jay Daley X-MailScanner-ID: 733C91D4113.A1417 X-MailScanner: Found to be clean X-MailScanner-From: lars@eggert.org Archived-At: Subject: Re: [xml2rfc-dev] Warning messages - How to address? 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Feb 2022 07:32:17 -0000 --Apple-Mail=_0050CE67-EC08-4E37-AEAD-A33A565DB5D0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 2022-2-2, at 21:15, Jay Daley wrote: > The tl;dr is that you do not need the DOCTYPE statement that includes = a .ent file. Read = https://authors.ietf.org/en/templates-and-schemas#character-entities for = a fuller explanation. Maybe that could be added to the warning message? Thanks, Lars --Apple-Mail=_0050CE67-EC08-4E37-AEAD-A33A565DB5D0 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEmpq0ZpSoejRmyhheVLXDCb9wwVcFAmH7hOsACgkQVLXDCb9w wVcEzhAA0q/MSHdE3JdbyEonOyEmA6keoXYoKGvv0Z8q3fxZbundJC/xKnT0H3A7 59gj57o5/jy9w1eaS5nVdwIKswyJ6g7P6HKuEt+JlOD6H7LCXAU34HQRJa1sMiA1 t/2aIY26cz2OVkB7nViJM2i4HX2+xiYaN0ZROvYXmTGDPjNrAGqisz79OgpJ1E9J Ce2vS9t4d5ulmTYgHbh2S5GhnNgEVRnwlu6n2e3bNz58Huh/Sov3Kn+SBAklP+/C wbrgE0nRPiqUlDDKCq6wFhhSx59hA97zDZCAt/IWaNDxlgGJHjSO/oQOrbBWkEeK 2PDHxfZeLeMcwxp6uHxX53I9WruZSCPlRPG2sFnCB2hiS8aI5NjyMSACR2sq22Rq mOTi9/bgwriyVR5iQ1C2EJfkv5Fv4eB76NkAPgWMF4pVnpFctovTiI3CDCo21PSm ZAWJ5yqSLykMS6Yd5pH3STFhq1QIRL2qfJMnqFqjWsrOYqhythz7xBJ/qV2DIrWh mdD8FTpPH0IrHu9KAJ4HiLcu1hB6Z/ITV1wXr0St98iq+eDassXGIFmYqS57FYHw BxGQHEH1sT3zcc5lU5AaS+bDCJVJxsruaYY0DvrkxhSaiZtILD194wV57qzCud7S uM5CaVeRrBaB9ClPTottOFbJwH/LxUIF4l45l3045ctPNIC/8p4= =+GNp -----END PGP SIGNATURE----- --Apple-Mail=_0050CE67-EC08-4E37-AEAD-A33A565DB5D0-- From nobody Thu Feb 3 00:33:11 2022 Return-Path: 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 44C5E3A2320 for ; Thu, 3 Feb 2022 00:33:09 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.613 X-Spam-Level: X-Spam-Status: No, score=-2.613 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.714, RCVD_IN_MSPIKE_H2=-0.001, 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 (1024-bit key) header.d=gmx.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 S82b0qmQMSzt for ; Thu, 3 Feb 2022 00:33:07 -0800 (PST) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (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 41B933A231E for ; Thu, 3 Feb 2022 00:33:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1643877181; bh=aPixbcYvqPOim4pL7iRwu9O4JoNNmw9KcXjkjW3lc8Y=; h=X-UI-Sender-Class:Date:Subject:To:References:From:In-Reply-To; b=KVmF5bRyLxwiARoGo73Lssitsjp9P2cc5fCjVbSWq5GE9QOJkuqbhVrhTESzmAQYm HFCwbgQ8ItmvyFNJ6IYeyq95j97c1jGv+tkxK4k4dN1GcJ9JnPsDuBcQLeOEigHSB4 cY63bz6pdOzHZhskdy8fhFAGFDEK19oMwRqAylvk= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from [192.168.178.20] ([91.61.56.52]) by mail.gmx.net (mrgmx105 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MaJ3t-1mlekS2l3F-00WHHX for ; Thu, 03 Feb 2022 09:33:01 +0100 Message-ID: Date: Thu, 3 Feb 2022 09:33:00 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.5.1 To: xml2rfc-dev@ietf.org References: <33F0F5FB-5CBC-4D6D-BFB7-18AC9798C720@ietf.org> <997C8D93-EF22-42D3-A0A4-9C04EDAEF464@tzi.org> <1ee39a65-68e7-6388-fa6d-6364ff546751@nostrum.com> <8d748cd3-1f80-aac7-c127-0791299e6a99@bobbriscoe.net> <136ddd96-42a9-1e42-02a0-5ee4ea9bc2a2@bobbriscoe.net> From: Julian Reschke In-Reply-To: <136ddd96-42a9-1e42-02a0-5ee4ea9bc2a2@bobbriscoe.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:lMgDYdivWV2ChMLHgQJRApUbLNpwbYcAmltSryRT4pRivQ5iQCo L1zdqu95nqhofZFII8N+3TjZX1pnJVKky915KUs5nHp3IgGTPquAWRy+GTCB5wVbTJaJF4p 7M9ap+/XFKUkZwOIyzOklAO78dJxrEsHfDMpntmtkIgQAbyecqjC9EV0HJq0YTv3IJIn8H9 t9FOCEcx0P+SaC54G7mgg== X-UI-Out-Filterresults: notjunk:1;V03:K0:dnbe9OXEQ0g=:WJOSlTD8oBUfBq/dzIw+9P oEaGBpwhSaV6g8gMKRCfgiy8QbCq/eCJT78Sa9823z5Yk1cPfe1Xzktw7mGZF/G2f2XqSwvtj obrEBHiki5/AYFdWt7EAVgf7er7O3ZZeKLm6Dejw4SyD0yIK5Lgsj8s+L1FZAy6BLP7r9QmZn D/gOP5I47pMbQgbDiq3VxoR+YtknvGWagRMhgRqIRW7ZkHRCJ0xkq7aru1uCkDdplRK99aT3z h65KNQk52pa6Bb1vWL5GLoDMU/pWtWSfT7SsWueg8jhUIhxhqNhBXd7v4ZLo86KCVNphw9ECX UzBrp17ZYyjSLV2Vaka8pr5qSpSM/xEbCWMmEckaPK9G3X/ersVMojT3z3TGEy4oG95ZwPsNt hgU7XQ60sNei0snXMbH3wlzpHeKVQvuOO3dTmYaSf9zTSxxumcnaU8uIpaJpJ7m6K96gfe/F6 qbTXH6aXuopT8aBdACOcf4QOyspOhHBx1N3YhT+yausU1venx08gOtCQWwJqmVxTdDJm5jF0Z Lo/MhL/QjhPqDA64foKJoXgdYyxGcbSo4Yq0HErqGfoKYOC6c/RVgaLOyyGxdWcb2+Td/txoR KpuXjYvJGj+MJpaaiTVwBbl1+gk8J0AgW/UfNEAxEuGGjZTTzOawGwflLrmblPd/FokjvBx9W 7jpOanO08+nvFwKsZIS0f2bTnSE2t99fsNVqjLzzIdqvtmXTBDZ01EcsO4z/Lgy+J82Go8ExO o76c+Dp/oMrbfAc6DFqV2MeBaYsz0TtZILtXC0N12J48ox6yitbexsb5bYBNlrdCjtJN1wItZ +U4P2XLikM7sV85NfF800ZRA9byMvvRBUKbjoyY8CNezoGQAtK0ssnBn9h2kAGTwOCZX0/i5d owDn5elAcXdR3dNimAJV909GK7wfVo1CjCFiQ2saldZy6sX9VRvUfb0O3iP8qjXkwaLP5YC4o YyJbmf+Ywm4oduAb/Uu8bZNyZvk4R/jYsM2jFHWTIMzdd5RMbuqtTZRQCkPNVkEPw/PVb1DXC 3v8yEWVeQcUAb+uMI/RH5o0sT07UazH6HysWsVfo3YieIoWyo2kTVNxHyj1gS7xvdqFwkiTAe yVP086j9SoQyuE= Archived-At: Subject: Re: [xml2rfc-dev] tables with no caption 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Feb 2022 08:33:10 -0000 Am 03.02.2022 um 03:49 schrieb Bob Briscoe: > Robert, > > With v3 rfc xml, is it possible to render a table (or figure) without > any caption at all? > An example of what I'm trying to achieve: > This IANA section using v2 rfc xml: > https://datatracker.ietf.org/doc/html/draft-ietf-tcpm-accurate-ecn-15#se= ction-7 > > > With v2 rfc xml, tables or figures with no anchor or title were > automatically not given a number or caption. > But with v3, one gets a caption saying, say, 'Table 5' on its own. > > Thx in advance. -> Best regards, Julian From nobody Thu Feb 3 05:48:09 2022 Return-Path: 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 2D08C3A1896 for ; Thu, 3 Feb 2022 05:47:56 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.813 X-Spam-Level: X-Spam-Status: No, score=-2.813 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, 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 KxHwEpDwlD5Y for ; Thu, 3 Feb 2022 05:47:51 -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 74B313A187C for ; Thu, 3 Feb 2022 05:47:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bobbriscoe.net; s=default; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:From:Cc:References:To:Subject:MIME-Version:Date:Message-ID:Sender :Reply-To: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=ZDSpF3be0iYFyFdFi17oL0EmTMdnbrW9wy7ASWem4NY=; b=QHLvKeXAUq0LEa1rW3RKrr8LUv 9Z81qdHRAmSuP07t5km4MGADrfAKpmjJJbZlstgIMKeYHG3l2/P2JrPv/vPAXog43lzaA5TtAg+ef EOivCOx1t4t3ePkNAK/g/qGgtInr/sJ6VWC4NDuzUutvMH3R47yYH6p2+Q5ts4uqnTFswTe2kcs0L cTv/QgezLUrPFZXQOligd6d4PX11Y5EeWzEAjFMFnh01gXSDafDg8tKddom724DaCHxiwog5wjg0l 1zO0Qc+VeHGOtDlduMDTlXwdrPQu+CWj1zall7vMGwGVIWM/rujf465rmF+JzsCGuMoXrZkwVn/Fw Mo+UbSPQ==; Received: from 67.153.238.178.in-addr.arpa ([178.238.153.67]:55076 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 ) id 1nFcSp-0004Ca-V8; Thu, 03 Feb 2022 13:47:49 +0000 Message-ID: <625dd5a0-bd13-2211-4e00-872a497c799e@bobbriscoe.net> Date: Thu, 3 Feb 2022 13:47:47 +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: Julian Reschke References: <33F0F5FB-5CBC-4D6D-BFB7-18AC9798C720@ietf.org> <997C8D93-EF22-42D3-A0A4-9C04EDAEF464@tzi.org> <1ee39a65-68e7-6388-fa6d-6364ff546751@nostrum.com> <8d748cd3-1f80-aac7-c127-0791299e6a99@bobbriscoe.net> <136ddd96-42a9-1e42-02a0-5ee4ea9bc2a2@bobbriscoe.net> Cc: xml2rfc-dev@ietf.org From: Bob Briscoe In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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: Subject: Re: [xml2rfc-dev] tables with no caption 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Feb 2022 13:48:07 -0000 Thx Julian, I'm not surprised this had already been raised - I searched for a couple of hours but didn't find anything - I probably should have searched harder. In issue #14 that you pointed me to, I've suggested that this issue is not labelled as a feature request, given it is about restoring a feature that was in v2 and used in ~50% of cases, but omitted from v3. Bob On 03/02/2022 08:33, Julian Reschke wrote: > Am 03.02.2022 um 03:49 schrieb Bob Briscoe: >> Robert, >> >> With v3 rfc xml, is it possible to render a table (or figure) without >> any caption at all? >> An example of what I'm trying to achieve: >> This IANA section using v2 rfc xml: >> https://datatracker.ietf.org/doc/html/draft-ietf-tcpm-accurate-ecn-15#section-7 >> >> >> >> With v2 rfc xml, tables or figures with no anchor or title were >> automatically not given a number or caption. >> But with v3, one gets a caption saying, say, 'Table 5' on its own. >> >> Thx in advance. > > -> > > Best regards, Julian > > _______________________________________________ > xml2rfc-dev mailing list > xml2rfc-dev@ietf.org > https://www.ietf.org/mailman/listinfo/xml2rfc-dev -- ________________________________________________________________ Bob Briscoe http://bobbriscoe.net/ From nobody Thu Feb 3 05:53:25 2022 Return-Path: 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 3E9533A1886 for ; Thu, 3 Feb 2022 05:53:23 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.614 X-Spam-Level: X-Spam-Status: No, score=-2.614 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.714, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.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 NsmcS4yrLnzZ for ; Thu, 3 Feb 2022 05:53:21 -0800 (PST) Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (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 54FE13A1881 for ; Thu, 3 Feb 2022 05:53:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1643896357; bh=6lLjVTxEohmbsVFyJoMQZ4xteoal83O3kNI0lpLeKvA=; h=X-UI-Sender-Class:Date:Subject:To:Cc:References:From:In-Reply-To; b=G9G32N8+aXPnoNHTINBuhNKRcM/K82mIopPmJCfqY6RlCVCFWamSK8NRtSpVBV2jK Hao4lzaKIOjBLgjFK7GQvTbUkBzmdib4O/mjoaD25oPGhujGKmeWstjND6wACwcxY4 uCIQZ4JV72/mrS9P+JDm5E2itNux9prbw2Cvzijg= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from [192.168.178.179] ([91.61.56.52]) by mail.gmx.net (mrgmx104 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MqaxU-1mT6V31RLs-00mapf; Thu, 03 Feb 2022 14:52:37 +0100 Message-ID: <5dd48f8d-e7c7-897c-4818-bb2a068a4330@gmx.de> Date: Thu, 3 Feb 2022 14:52:36 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.5.1 To: Bob Briscoe Cc: xml2rfc-dev@ietf.org References: <33F0F5FB-5CBC-4D6D-BFB7-18AC9798C720@ietf.org> <997C8D93-EF22-42D3-A0A4-9C04EDAEF464@tzi.org> <1ee39a65-68e7-6388-fa6d-6364ff546751@nostrum.com> <8d748cd3-1f80-aac7-c127-0791299e6a99@bobbriscoe.net> <136ddd96-42a9-1e42-02a0-5ee4ea9bc2a2@bobbriscoe.net> <625dd5a0-bd13-2211-4e00-872a497c799e@bobbriscoe.net> From: Julian Reschke In-Reply-To: <625dd5a0-bd13-2211-4e00-872a497c799e@bobbriscoe.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:WPr1ZIb85mGznP4TdtiNC0aahUERp+PeXuqAJ5ztn78omXUDNiD K+lILIurbCMGwA2LVmhrLB5RlsFxVmMcyA+ka8BDFEI3n3X6AVBQFtzLRc5HpX+EmUjThap nqSp395wWBPSWFqrL0qoso3Zj7E8qBEBxz9DQ+ySrmlb5bXT1UjEJl7UWl1t2gwUSmG4nIQ A/3Zvi5+bz1udRx6bGYzg== X-UI-Out-Filterresults: notjunk:1;V03:K0:mJxyVUy1WDA=:TD25HqjC2FnxtdO4a4fpEw e/ri3Zybwep25Xb5nVw80S0B0+oNn05rWFb6dY18Nw8S2M8nC9dLkk0iS1Jx/07N2+//Z5eta SEJz9BW+k2D8qYMTZrgfQm3K6LCycoetL2a5kVwwssBBbi/aEmW1Z4TJhkYgu+wLSMrN2uKjx /PNLCz3+3Fp36Dq6ntQ16jNfZvvh8IhM38ZSs9jQAx/CD9s5rkoqEOc0njcNbcDYv2zZbkq34 MKNrpkhp/y0LhWqrcU68w42h0UXA53rNGygte32TTiFaMSXFkviaRMcF2UpIkTvXPuyHgasO2 DQlqtCIwS3zE6tdX308RDcHS+CHB40gvYBQNkp/RutKb/e3AZQPoSVWWAbcwrLaAbrQs3gniV CcxgcEGvUaAQnoajBE2GKJJCHEnfau2EXjUcYaDhP5HrE2ZYWbO6Syk8SDfGgghtNQoohIUMQ 07S2O/OhbfAbKrDXU1EjdDrq3rPTpsNoHAbN3VHpqTmgU/ccpocplUt4cuFRQRHB4mcgfCM4f H/LLpG1L6m0HJkd2A3AJlY90uCj4oFK6+0xHXCMiCABl53lRIMQh2CTq0uJYD3zU+Lo7oxOMU 8WpDDE9aUcO2QSGOArEAPNX6TdqvRnqzVi/BJoYPCZ+Df/uXEe4SmWaaxlCtoNSlgIP+5eNvR QZFUby4/xf5wU+2cqmh6hMiYcULN518H7i/ULhsu0T5AC/n4wkdanHm9FCcNsaW9Ebz94cfsG /DlR6UpQXJHB7T6dk+LzCU465Zm9JwCmPzql+G5ci7eVtR2g/AKjBeynawv0+1Lvc+k5tVdnc UZiCstb+jmWkjqpNHXIh6VJbMaClSHbF2mgyjgQz3bE6LalzK2MMWXZnUDT0ayXXWdinta8fI ECCQQ/rduCN5QGsSDQYgSFDYpHogwgudbvnfJgLJwR7ZHiM5cLnVqFZPhribf9VKDX0tYdS3P JEPvGqnb4E0n4ZVMLDbZ/5t27f6AEq6OXOd+At9qz7+G00BPTtWhz+bFvo49KncRIPvnB/u7l i2DYZ6LpuVzboafzfxPCLuAPqFb+wWXqAPO/EvXsLJWOBFn+pwpa5M0YcOoH14OHVIXeqsCqg tTASDNCMY96b2k= Archived-At: Subject: Re: [xml2rfc-dev] tables with no caption 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Feb 2022 13:53:23 -0000 Am 03.02.2022 um 14:47 schrieb Bob Briscoe: > Thx Julian, > > I'm not surprised this had already been raised - I searched for a couple > of hours but didn't find anything - I probably should have searched hard= er. > > In issue #14 that you pointed me to, I've suggested that this issue is > not labelled as a feature request, given it is about restoring a feature > that was in v2 and used in ~50% of cases, but omitted from v3. > > > Bob And even in 2017. I agree that this is a regression; the label was set by StPeter and I have no sufficient privileges to change it. Best regards, Julian From nobody Wed Feb 16 13:01:55 2022 Return-Path: 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 694263A0ABC; Wed, 16 Feb 2022 13:01:41 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.678 X-Spam-Level: X-Spam-Status: No, score=-1.678 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" 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 fbXlJmjU7PmD; Wed, 16 Feb 2022 13:01:37 -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 1CABC3A0AD7; Wed, 16 Feb 2022 13:01:37 -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 21GL1XIU069255 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Wed, 16 Feb 2022 15:01:34 -0600 (CST) (envelope-from rjsparks@nostrum.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1645045294; bh=BryXFFEAFNWZe/fAxufHZyRUamjwetpaDIvDe+VvV4Q=; h=Date:To:From:Subject; b=iwUinQwq1Xmz/woMdjSTTKX2cnO3gDOdQdarNZYgONl6cAUNco6tEy+CHrIkWEPgy 3OGKRklcTQmVwLow6dk6E0xz3NC4LKJQ/a3+aJa0hMHRYSh8WD76gHVVEV72pZ6ZwP uGzPLLwGRLx88NSXriFMNDGGunic5h+7juWo68m4= X-Authentication-Warning: raven.nostrum.com: Host [47.186.48.51] claimed to be [192.168.1.114] Content-Type: multipart/alternative; boundary="------------6yDPba0ls4aatLZcINeZkUFl" Message-ID: Date: Wed, 16 Feb 2022 15:01:28 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.6.0 Content-Language: en-US To: xml2rfc-dev@ietf.org, XML2RFC Interest Group , rfc-markdown@ietf.org, tools-discuss From: Robert Sparks Archived-At: Subject: [xml2rfc-dev] New xml2rfc release: v3.12.2 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Feb 2022 21:01:42 -0000 This is a multi-part message in MIME format. --------------6yDPba0ls4aatLZcINeZkUFl Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit This is _not_ an automated message - we'll build automated mail about releases into the repositories later (or better, people can subscribe to the repository for new releases directly). xml2rfc's repository is now at https://github.com/ietf-tools/xml2rfc/ This release is our first from github. It fixes https://github.com/ietf-tools/xml2rfc/issues/700 As before: > The preferred way to install xml2rfc is by doing 'pip install xml2rfc', > and 'pip install --upgrade xml2rfc' to upgrade. If there are system- > installed python modules which pip will not upgrade, you may have to > use 'pip install --upgrade --no-deps xml2rfc' and install dependencies > manually. Many thanks to Nick, Kesara, and Jennifer for building out and testing the infrastructure needed to make this release. RjS --------------6yDPba0ls4aatLZcINeZkUFl Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

This is _not_ an automated message - we'll build automated mail about releases into the repositories later (or better, people can subscribe to the repository for new releases directly).

xml2rfc's repository is now at https://github.com/ietf-tools/xml2rfc/

This release is our first from github.

It fixes https://github.com/ietf-tools/xml2rfc/issues/700

As before:

The preferred way to install xml2rfc is by doing 'pip install xml2rfc',
and 'pip install --upgrade xml2rfc' to upgrade.  If there are system-
installed python modules which pip will not upgrade, you may have to
use 'pip install --upgrade --no-deps xml2rfc' and install dependencies
manually.

Many thanks to Nick, Kesara, and Jennifer for building out and testing the infrastructure needed to make this release.

RjS

--------------6yDPba0ls4aatLZcINeZkUFl-- From nobody Wed Feb 16 15:01:50 2022 Return-Path: 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 A27F53A0CF0; Wed, 16 Feb 2022 15:01:28 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no 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 K-t29BSXgtuB; Wed, 16 Feb 2022 15:01:24 -0800 (PST) Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DFD3C3A1774; Wed, 16 Feb 2022 15:01:22 -0800 (PST) Received: from client-0015.vpn.uni-bremen.de (client-0015.vpn.uni-bremen.de [134.102.107.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4JzYNY4dsQzDCcg; Thu, 17 Feb 2022 00:01:17 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\)) From: Carsten Bormann In-Reply-To: Date: Thu, 17 Feb 2022 00:01:17 +0100 Cc: XML2RFC Dev , XML2RFC Interest Group , rfc-markdown@ietf.org, tools-discuss X-Mao-Original-Outgoing-Id: 666745277.135753-c8cf86bd10ffc28fdfec1c7586d0ad8c Content-Transfer-Encoding: quoted-printable Message-Id: <940EB617-0D88-4518-885D-E76B8EA63492@tzi.org> References: To: Robert Sparks X-Mailer: Apple Mail (2.3608.120.23.2.7) Archived-At: Subject: Re: [xml2rfc-dev] [Tools-discuss] New xml2rfc release: v3.12.2 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Feb 2022 23:01:29 -0000 On 2022-02-16, at 22:01, Robert Sparks wrote: >=20 > This release is our first from github. Congratulations! =F0=9F=8D=BE=F0=9F=8E=89=F0=9F=8E=8A Kudos for the team that made this happen. And many thanks for = https://github.com/ietf-tools/xml2rfc/blob/main/svn-history/xml2rfc-revmap= .txt =E2=80=94 I don=E2=80=99t have tooling to consume this yet, but = I=E2=80=99ll sure have it soon... Gr=C3=BC=C3=9Fe, Carsten From nobody Wed Feb 16 21:59:03 2022 Return-Path: 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 8ED543A11E2; Wed, 16 Feb 2022 21:58:24 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no 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 U-6SyemAmyC1; Wed, 16 Feb 2022 21:58:23 -0800 (PST) Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 DF1943A11E4; Wed, 16 Feb 2022 21:58:22 -0800 (PST) Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.93) (envelope-from ) id 1nKZo3-000a7F-7L; Thu, 17 Feb 2022 05:58:19 +0000 Date: Wed, 16 Feb 2022 21:58:18 -0800 Message-ID: From: Randy Bush To: Robert Sparks Cc: xml2rfc-dev@ietf.org, XML2RFC Interest Group , rfc-markdown@ietf.org, tools-discuss In-Reply-To: References: User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/26.3 Mule/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII Archived-At: Subject: Re: [xml2rfc-dev] [xml2rfc] New xml2rfc release: v3.12.2 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Feb 2022 05:58:25 -0000 > This release is our first from github. can't speak to other attributes, but it is faster from comcast portland. randy From nobody Thu Feb 17 06:23:14 2022 Return-Path: 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 355983A08AE; Thu, 17 Feb 2022 06:22:54 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.099 X-Spam-Level: X-Spam-Status: No, score=-2.099 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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ribose.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 X7DK0p1zxG6J; Thu, 17 Feb 2022 06:22:49 -0800 (PST) Received: from APC01-HK2-obe.outbound.protection.outlook.com (mail-hk2apc01on0621.outbound.protection.outlook.com [IPv6:2a01:111:f400:febc::621]) (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 AD7CD3A0898; Thu, 17 Feb 2022 06:22:48 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=kNVROf6794Ntde/wIlqBk6BQhxTQgnoU66zMaZryXyMcUD3grS5jU1zYZaPVr4EklPo4CpOOaJJkctQgr/3Ugd477Oabha/74Cl2y2k2TaHqoOeACiJRjOxFvjC+rx44hVhSu2PrR0ZwQ7UdqxBN2OQTEXxNjYGHUpr0/Rh/iEbfH1IIJ3NzZixoE2qdZoFZm4EW7r6+IO+R+5oNPqouhQSf8JdTbWb63dYr78snyBcnfXGMubT/q9+D66FAfiLal2lZbxZOG39AspZtbM95cuZhnhw2FnXMPvwywNqbl7l+11/9b1xie/VZSIh9otWEPKcFD6sGD5z/OHyKslz/dQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=UYyfSo2yfaxb3o1yaujDMLlDMqMy9RgD6vp+GpbKLZI=; b=HJYeKlib/PyWCec7jwir7QVfY8u4GOhdDUJeCK5vV5cQHQiHpadPrfkIKgUp4yrCMZVmPTV49Us5bjO0j190aG8eiMpleZEKu5L9rhmuQ5YAe3jrGL6ON/EJoSE64t9ygqEAKZXez3fDqTJEbfocvcOL12K0qrACuXmaJabUC2TaFbkoY6umlRgefUk6xnEc45vNue6rhNlYNxv974GOXgPFuGZC7WuubiCjbAvuiCGFDGsOm4q2+J11x0iVTOeyifa2SNBVsJjAbJq32H9jOQk2R9M4pwN24iy9Xt7Vfg29rZqicHF1CLtBO9pvtFA5fyFHq9ZK1yHk/bbaRl8lqg== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ribose.com; dmarc=pass action=none header.from=ribose.com; dkim=pass header.d=ribose.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ribose.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=UYyfSo2yfaxb3o1yaujDMLlDMqMy9RgD6vp+GpbKLZI=; b=MI0jpqt4CtXZtkDUHVJLj+CRhD6c7k+eZmOsdnTHyZRc/U6bvZ2p59+2VRZ8ZCcbDwQpgTnLmeZ4y9xeu/ZUx/gZoF2DGZXsoq/epaVLjQfEq8xEaFezzAfaiqOPfMqEiFtZkyEOgSDvJI8xMNA5FbUrQlzwXNBoO+1N/o4E+hY= Received: from HK0PR01MB2001.apcprd01.prod.exchangelabs.com (2603:1096:203:23::14) by PS1PR01MB3513.apcprd01.prod.exchangelabs.com (2603:1096:300:7d::16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4995.15; Thu, 17 Feb 2022 14:22:42 +0000 Received: from HK0PR01MB2001.apcprd01.prod.exchangelabs.com ([fe80::d0ce:e374:5a1a:f8a3]) by HK0PR01MB2001.apcprd01.prod.exchangelabs.com ([fe80::d0ce:e374:5a1a:f8a3%5]) with mapi id 15.20.4995.016; Thu, 17 Feb 2022 14:22:42 +0000 From: Ronald Tse To: Robert Sparks CC: "xml2rfc-dev@ietf.org" , XML2RFC Interest Group , "rfc-markdown@ietf.org" , tools-discuss Thread-Topic: [xml2rfc-dev] New xml2rfc release: v3.12.2 Thread-Index: AQHYI3h05tdSDkCfWUik5/0nBMkmaKyXzLOA Date: Thu, 17 Feb 2022 14:22:42 +0000 Message-ID: <73B345C2-4E4E-48E1-A5A5-9A3DC959A013@ribose.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-mailer: Apple Mail (2.3693.60.0.1.1) authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=ribose.com; x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: d0dee395-e6fc-4b77-1921-08d9f220f5b1 x-ms-traffictypediagnostic: PS1PR01MB3513:EE_ x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:8882; x-ms-exchange-senderadcheck: 1 x-ms-exchange-antispam-relay: 0 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: HlXMnTay1Y9BJjaphYmQvhrrvqCiaZap3JFrPgt2tHVVuA0LxYXOeQXwPhl7ERPRXYn6OiW23Sm6G7dOZOqfcNNkPQ0a+sQZBqGznG8iJksSgBLkKnmFFJm935gYMWXDxgfk4SW88RQ6Kue2fAV6xAa8AnlJ34skbYukDszN55YoZs7lS8f7GnyK9o6/xYg3MjyGmFKmDeo1M5Q2EHLIZPlVTsoZOYvaW7GKHnUh/H5jD00NySiNHVoMeagj4Fz3/a9BdvuT5Z4qkt3Wnq50VU2lAVScsyXyqtHonWimw4jQV3m649ZbmU1L6Lj5TgYO3cqPCxsnqHljq0C1OPJNTeIm/0qKcRIK2BsB+c+wYt1m7quSV0J+XXdGm/ChWWxzCPnH36GLjRNkhZJ+0wDeOy5csaA7fB/ehTI/x3yoFUIkKQeYbNl/AemP3EW4SX6Qd34epLQ854FKd1NUBtZA3mhBv98BIEZfRksqkau5wQr2v1fLIJG67KARJ8dyccfquSp/IKTkO2QLel73bcFD8ztVwGDxra/QPMJCbdkdv67tizPVbrK2VRudz11bl15JdyJYVJl5qz9nz4HulCgrB9WNjNqjYAqp+JsDVHlxoZb9rHmK/KOgPsGesxfspHRozEgkZB1k5mzXeFJkW1La7Cxh4N58dtIZsd08iuLEPbrdELLZ9+D5dKarw8KU3I89mDQzAwVNsWGe/FavMeqsT193aJr+bVnFczc7Y1+yszRxBfbbeG9Dm6ivJufAhMkiTJkX3wSIvaFTjxgNp675unn1v4YiAXwgxeWdUoDNKF8= x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:HK0PR01MB2001.apcprd01.prod.exchangelabs.com; PTR:; CAT:NONE; SFS:(13230001)(346002)(376002)(39830400003)(396003)(366004)(136003)(53546011)(2906002)(4326008)(6512007)(8676002)(86362001)(64756008)(66446008)(66476007)(66556008)(38100700002)(316002)(8936002)(966005)(6506007)(6486002)(71200400001)(508600001)(122000001)(33656002)(76116006)(91956017)(166002)(66946007)(54906003)(5660300002)(2616005)(83380400001)(186003)(6916009)(36756003)(26005)(38070700005); DIR:OUT; SFP:1101; x-ms-exchange-antispam-messagedata-chunkcount: 1 x-ms-exchange-antispam-messagedata-0: =?us-ascii?Q?Kj10igrlnC+TnSt8Xbr50N3KujPxjrosuiX6nMZxuKisTUTXSNU0/bkD6Q3h?= =?us-ascii?Q?AjhGn5ZKHxcHIxQbUm3Y97qC3DIdcs2NYsMBehtgPf6xxDjsuDnhSHmAxQH6?= =?us-ascii?Q?oZhZZ/QkSqujXVsg0g20eO2/3BL6QX/FZeb4Q0JhEufWXWkqrF1TVYWGLtF5?= =?us-ascii?Q?0NKPInWe4YbS8ceWWWj/jdQ4do5/pnIpdwNmLyYFNJ7jUdQXKkLAybxuu1Cb?= =?us-ascii?Q?wgVFbv3IP0svY81QO7R8uU8Rk9yXrZGysHQhPbHzNqLpsSLhu+2Y6iTforrE?= =?us-ascii?Q?eu4+Xiwyy7hQI6cMM3+MzCC51OsxNuibBGoAoo2nx8aTC6r6tFxWZwcnRN8J?= =?us-ascii?Q?YlichBVIz4ODadFTRQaj8Htmw/YnFVyAeSdKx4ZCG+/WB0rQue8w83oDAQ2H?= =?us-ascii?Q?g1U+kzMNAlg2ZyieTTDZGl3iGzcLW3zbw8QG7z7uVY0MFbXkDmplH9N3o2pH?= =?us-ascii?Q?tGvv9n9941c7a3f2tj29pMGRqQr56abTf8HN0ficHilVGrcr0R85MgdnLJBM?= =?us-ascii?Q?KpO6vdJwuNjVnnksrKLsaJnV6urgWY55Jp/DArLa0P9go2YKaEivPQFDgBtX?= =?us-ascii?Q?Vbl1xt1lQAXsyq/0EcJpiOCjIrERCswHspnXFRziO52AjAhe1MBE/BUkgALT?= =?us-ascii?Q?e/foG6lx4Ykea0LqCq9gVwfp3ioPpspuOHI55GMuOr9AiV7lkQ1Q/VRJaJac?= =?us-ascii?Q?ORkJAo3rT97OI+IknLQ9l16ZyZC0Yr0tPNo+x8eYaCIbQi/ULtBhjIEDvthP?= =?us-ascii?Q?0aF4kZQr1sm6Pe26b6vJBqVuRuKXrYLWRVd5HMTQfSKD2FxWmgwE9POQrp75?= =?us-ascii?Q?3MFQlVVuOESyFt7hI9LLi6ZPoQHx8+TfhdV2KQQCThtcd3vvWTF5Hk6nNW0r?= =?us-ascii?Q?ibRV/nCLm+zt8hCvpBY4lEvjkBTPYyFJUz/Gy0lGCDn/VA6y53kaF2Gvr9fs?= =?us-ascii?Q?gU6M0k+SHYSsEX1QiCa4JjTQIpa/uRjWwBgUO2I0784lrRFFqPIfo4KbS+E2?= =?us-ascii?Q?Jd9bIkruhtLPLRmshOMonC3e4J4ZlXcS4HFr17aNViBRZPpMDLJPN51XIXg/?= =?us-ascii?Q?Ul1fDm1dLNzAo+I1dQ1vqXLRh14C5IE0fHWAkDkqH7QgTLdfjFd7nab9fysY?= =?us-ascii?Q?ZBLLtHnAo/oC2p1Fpf9XIWY2j2nskDMMmR/uqTaZTy+BCDpESei4E2yqaZ9v?= =?us-ascii?Q?nPvc2EZAIBscKcB2NDSC5iuWWz1fbFdzIS3D/cwf31KnRmw/726CDPhpOPI2?= =?us-ascii?Q?g5Bvh7yZz7IfVj+d96dvRlbWC8DPyK4S7sjTieGvx73fs7dSIg0mxd5dhPK7?= =?us-ascii?Q?S8E+G8AudnmhyMtwQ/trEXzEIxobLkqov6NpjUlvYJ7LdefsNs3jxYGWWYhM?= =?us-ascii?Q?ym5VwrI0wKint2WRjNIsa1LXbYp8kH2vLQelxhtFZjiIu4SIbH9fsVfHe9z1?= =?us-ascii?Q?REgPi1AAIK3DYLODa49u15f5fv8Ud9wW6ykU4KY5kPRCD2uvJo90w+w7otTe?= =?us-ascii?Q?PilW8O1bmnAYwF7de/ULk0/bc08vURLN6STiiu9DRyL/GMwH3rHkmRdgGpNG?= =?us-ascii?Q?v4T3npYSou7gtDSBMHxSQrexKa3Ro5pxCj9PBuFQ?= Content-Type: multipart/alternative; boundary="_000_73B345C24E4E48E1A5A59A3DC959A013ribosecom_" MIME-Version: 1.0 X-OriginatorOrg: ribose.com X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: HK0PR01MB2001.apcprd01.prod.exchangelabs.com X-MS-Exchange-CrossTenant-Network-Message-Id: d0dee395-e6fc-4b77-1921-08d9f220f5b1 X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Feb 2022 14:22:42.2660 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: d98a04ff-ef98-489b-b33c-13c23a2e091a X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: CMTe1qsLH3xCw8uT+iODg+uszE4gpOQ+/os2C4dw5VuFyRW7IVQ8vo/biTZUINcm X-MS-Exchange-Transport-CrossTenantHeadersStamped: PS1PR01MB3513 Archived-At: Subject: Re: [xml2rfc-dev] New xml2rfc release: v3.12.2 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Feb 2022 14:23:02 -0000 --_000_73B345C24E4E48E1A5A59A3DC959A013ribosecom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Congratulations to the xml2rfc team! This is an excellent step that will se= rve the community well. Ron _____________________________________ Ronald Tse Ribose Inc. +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D+ This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D+ On 17 Feb 2022, at 5:01 AM, Robert Sparks > wrote: This is _not_ an automated message - we'll build automated mail about relea= ses into the repositories later (or better, people can subscribe to the rep= ository for new releases directly). xml2rfc's repository is now at https://github.com/ietf-tools/xml2rfc/ This release is our first from github. It fixes https://github.com/ietf-tools/xml2rfc/issues/700 As before: The preferred way to install xml2rfc is by doing 'pip install xml2rfc', and 'pip install --upgrade xml2rfc' to upgrade. If there are system- installed python modules which pip will not upgrade, you may have to use 'pip install --upgrade --no-deps xml2rfc' and install dependencies manually. Many thanks to Nick, Kesara, and Jennifer for building out and testing the = infrastructure needed to make this release. RjS _______________________________________________ xml2rfc-dev mailing list xml2rfc-dev@ietf.org https://www.ietf.org/mailman/listinfo/xml2rfc-dev --_000_73B345C24E4E48E1A5A59A3DC959A013ribosecom_ Content-Type: text/html; charset="us-ascii" Content-ID: <7E6FC0589B7A98468253AF5BD4249431@apcprd01.prod.exchangelabs.com> Content-Transfer-Encoding: quoted-printable Congratulations to the xml2rfc team! This is an excellent step that will se= rve the community well.

Ron

_____________________________________

Ronald Tse
Ribose Inc.

+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D+
This message may contain confidential and/or privileged
information.  If you are not the addressee or authorized to
receive this for the addressee, you must not use, copy,
disclose or take any action based on this message or any
information herein.  If you have received this message in
error, please advise the sender immediately by reply e-mail
and delete this message.  Thank you for your cooperation.
+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D+

On 17 Feb 2022, at 5:01 AM, Robert Sparks <rjsparks@nostrum.com> wrote:

This is _not_ an automated message - we'll build automated ma= il about releases into the repositories later (or better, people can subscr= ibe to the repository for new releases directly).

xml2rfc's repository is now at https://github.com/ietf-tools/xml2rfc/

This release is our first from github.

It fixes https://github.com/ietf-tools/xml2rfc/issues/700

As before:


The preferred way to install xml2rfc is by doing 'pip insta=
ll xml2rfc',
and 'pip install --upgrade xml2rfc' to upgrade.  If there are system-
installed python modules which pip will not upgrade, you may have to
use 'pip install --upgrade --no-deps xml2rfc' and install dependencies
manually.

Many thanks to Nick, Kesara, and Jennifer for building out an= d testing the infrastructure needed to make this release.

RjS

_______________________________________________
xml2rfc-dev mailing list
xml2rfc-dev@ietf.org=
https://www.ietf.org/mailman/listinfo/xml2rfc-dev

--_000_73B345C24E4E48E1A5A59A3DC959A013ribosecom_-- From nobody Sat Feb 26 16:07:21 2022 Return-Path: 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 D1E1B3A093B for ; Sat, 26 Feb 2022 16:07:18 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.91 X-Spam-Level: X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no 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 R91B24rJlNfn for ; Sat, 26 Feb 2022 16:07:15 -0800 (PST) Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B392B3A0940 for ; Sat, 26 Feb 2022 16:07:15 -0800 (PST) Received: from smtpclient.apple (p5089ad4f.dip0.t-ipconnect.de [80.137.173.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4K5kMz0cPZzDCbV; Sun, 27 Feb 2022 01:07:10 +0100 (CET) From: Carsten Bormann Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\)) Date: Sun, 27 Feb 2022 01:07:10 +0100 Message-Id: <681C8835-5154-4261-88CF-BE0AA90905FA@tzi.org> To: XML2RFC Dev X-Mailer: Apple Mail (2.3693.60.0.1.1) Archived-At: Subject: [xml2rfc-dev] When did v2v3 stop spewing redundant attributes? 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Feb 2022 00:07:19 -0000 We have a little mystery over in = https://github.com/cabo/kramdown-rfc/issues/162 The xml2rfc v2v3 code used to output redundant attributes of the form
where numbered and toc have their default values (and weren=E2=80=99t = set on the input side either). This seems to have stopped with xml2rfc 3.12.1. I have a few instances generated from 3.11.1 v2v3 that look like the = above, and I have a few from the same version that look like
(i.e., one redundant attribute gone, one still there). Previous versions (3.10.0 or earlier) consistently output the redundant = attributes. Now the mystery: When downgrading to, say, 3.9.1, the problem does not recur (!). Where was this fixed? In xml2rfc or maybe some of its dependencies? I=E2=80=99m not asking for the bug to be put back in, but it would help = if we could understand what the shape of the set of instances is that = have this problem. (Note that this is a discussion about documents in processable form = (=E2=80=9Cunprepped=E2=80=9D, editable); not an attempt to bring up the = discussion whether default values are needed in prepped (final published = form) XML documents.) Gr=C3=BC=C3=9Fe, Carsten From nobody Sun Feb 27 04:32:34 2022 Return-Path: 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 1A0883A1048 for ; Sun, 27 Feb 2022 04:32:31 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.909 X-Spam-Level: X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no 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 7MruPKyCkdoO for ; Sun, 27 Feb 2022 04:32:26 -0800 (PST) Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C0603A1049 for ; Sun, 27 Feb 2022 04:32:25 -0800 (PST) Received: from [192.168.217.118] (p5089ad4f.dip0.t-ipconnect.de [80.137.173.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4K62vp2dnMzDCcb; Sun, 27 Feb 2022 13:32:22 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\)) From: Carsten Bormann In-Reply-To: <5dd48f8d-e7c7-897c-4818-bb2a068a4330@gmx.de> Date: Sun, 27 Feb 2022 13:32:22 +0100 Cc: Bob Briscoe , XML2RFC Dev , Julian Reschke X-Mao-Original-Outgoing-Id: 667657941.952462-2018c7012deabf19deb0602047226a2d Content-Transfer-Encoding: quoted-printable Message-Id: References: <33F0F5FB-5CBC-4D6D-BFB7-18AC9798C720@ietf.org> <997C8D93-EF22-42D3-A0A4-9C04EDAEF464@tzi.org> <1ee39a65-68e7-6388-fa6d-6364ff546751@nostrum.com> <8d748cd3-1f80-aac7-c127-0791299e6a99@bobbriscoe.net> <136ddd96-42a9-1e42-02a0-5ee4ea9bc2a2@bobbriscoe.net> <625dd5a0-bd13-2211-4e00-872a497c799e@bobbriscoe.net> <5dd48f8d-e7c7-897c-4818-bb2a068a4330@gmx.de> To: Peter Saint-Andre X-Mailer: Apple Mail (2.3608.120.23.2.7) Archived-At: Subject: Re: [xml2rfc-dev] tables with no caption 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Feb 2022 12:32:31 -0000 On 2022-02-03, at 14:52, Julian Reschke wrote: >=20 > I agree that this is a regression; the label was set by StPeter and I > have no sufficient privileges to change it. And it isn=E2=80=99t changed yet. Gr=C3=BC=C3=9Fe, Carsten From nobody Sun Feb 27 05:03:48 2022 Return-Path: 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 EC6523A108F for ; Sun, 27 Feb 2022 05:03:45 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.909 X-Spam-Level: X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no 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 tT7N6u_jN0Rx for ; Sun, 27 Feb 2022 05:03:40 -0800 (PST) Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B02F3A1091 for ; Sun, 27 Feb 2022 05:03:39 -0800 (PST) Received: from [192.168.217.118] (p5089ad4f.dip0.t-ipconnect.de [80.137.173.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4K63br0kh8zDCd2; Sun, 27 Feb 2022 14:03:36 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\)) From: Carsten Bormann In-Reply-To: Date: Sun, 27 Feb 2022 14:03:35 +0100 Cc: Bob Briscoe , XML2RFC Dev , Julian Reschke X-Mao-Original-Outgoing-Id: 667659815.712021-6b190c4c7878dc58e4ad6d8c34a593cd Content-Transfer-Encoding: quoted-printable Message-Id: <0D66CB2C-395C-46A6-936A-33FAD798FDDB@tzi.org> References: <33F0F5FB-5CBC-4D6D-BFB7-18AC9798C720@ietf.org> <997C8D93-EF22-42D3-A0A4-9C04EDAEF464@tzi.org> <1ee39a65-68e7-6388-fa6d-6364ff546751@nostrum.com> <8d748cd3-1f80-aac7-c127-0791299e6a99@bobbriscoe.net> <136ddd96-42a9-1e42-02a0-5ee4ea9bc2a2@bobbriscoe.net> <625dd5a0-bd13-2211-4e00-872a497c799e@bobbriscoe.net> <5dd48f8d-e7c7-897c-4818-bb2a068a4330@gmx.de> To: Peter Saint-Andre X-Mailer: Apple Mail (2.3608.120.23.2.7) Archived-At: Subject: Re: [xml2rfc-dev] tables with no caption 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Feb 2022 13:03:46 -0000 On 2022-02-27, at 13:32, Carsten Bormann wrote: >=20 > And it isn=E2=80=99t changed yet. The funny thing, of course, is that every RFC published since 8650 = carries the suppress-title attribute on each figure and each table. It = is just always set to false. So fixing this regression wouldn=E2=80=99t = even need a grammar change; we would just need to remove the code that = deletes suppress-title attributes in v2v3.py and delete line 984 and 985 = in writers/base.py. (Note that suppress-title is implemented in v2v3 for figures by simply = stripping the