ASN.1 encoding rules: Specification of basic encoding Rules = (BER), Canonical encoding rules (CER) and Distinguished encoding rules = (DER)

Acknowledgments I also tried:

Same error. What perhaps am I doing wrong? From nobody Thu May 21 08:51:40 2020 Return-Path: X-Original-To: xml2rfc@ietfa.amsl.com Delivered-To: xml2rfc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EC7F3A02BB for ; Thu, 21 May 2020 08:51:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, 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 kair8-znbXIj for ; Thu, 21 May 2020 08:51:36 -0700 (PDT) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (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 E60373A017E for ; Thu, 21 May 2020 08:51:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1590076286; bh=iHb25Mnmatxrb5HeGlGZzF0wnPFdXhoFPyLkSGStHao=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=Q+Qelsdrs/IonOzzOxboJwUdVT2XU2rU00aod+FYj26RtYVyvKMfAJiAL4o50TPbf IKRkjcrozYJWOY8c15TBpo5Qr7korjt+iTlel1KwRm78didCc6ijFFXLZEEp0aqyOF eCiEMu66cXfcGfzeTPRAO+jV19PwXIqjJOVZrwpo= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from [192.168.178.182] ([84.171.144.54]) by mail.gmx.com (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MKKUv-1jL6Kv10ox-00Lnli; Thu, 21 May 2020 17:51:26 +0200 To: Robert Moskowitz , "xml2rfc@ietf.org" References: From: Julian Reschke Message-ID: <95b07998-22e3-dd37-5973-4bd96ff5bee0@gmx.de> Date: Thu, 21 May 2020 17:51:25 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:BJ5ep4Bnf/Ze8eu2hMX7/oKNQF6tEjCV2ku09iXhM4tdJPuKgM1 qD05PIuWCmbvUlGC8Ydt5fTNUA+zkJfBdx6BimQy9/i/DIKeFUTrZjdQQOvRgnB3vNGzZLh W9HqkNVUkSulRWkctimxvtTHWOLbPlvc3Lan6jT2PxX/rJyWGzkA0/aDfiBpkYCnJ8qolbK w3s7sW1cAuCiamoMfpQzQ== X-UI-Out-Filterresults: notjunk:1;V03:K0:mci742ab31o=:XIdpie1JSmOfsCzmuS1GBR lfKVUuonyWNU6BG4BvwwqhnmDKFif6CNr68VaSrfGpT7ywnxout0TQjqwP9NiUVVJC2w1adAn FS4jZAmPX+mIphiC3iCdtMsQyBRyew8YHq4dqXWsDYbzr62chV7+5YHEtzRiUwtlmeCA4mk9e BM33ojLWUJywoqR5BK9JKkBbh6Xw94D8fcf2y1qVgQQH/+tpxikGJCqHoDhqXyJ+eVNtdhvwW yP+UJwR0e9cTcLCk2kf/f6H/lSGMXW+iWMTONElek5XGvv6lt23qaw0UsEVXP80eR71BuyWZH HRDYlsipgKQNuoPfCXEVBH6c+kimPFndSLc8xT/M1zzjiuScvg1okWeFFKwR+eCmS+ww0RViU KudLsHZqErtgur++SizNTq2qYgBIiJ4PlYH35r59579p4lCVi1tvRTfPebClvSYNT8mHOaDOu QXj0gEZMuLORZmrOQ4y58bdzqWlUNxx3/qBRLZgOv8yQKhm77ZxCLi3sRun2ul45tOR4zcFQt ZvWnDUWDtL11yuelRCFIQzDmuranhugojkWw533wtxyFgXiuzSLvDt4QL89eRA+2GM+cUTvGE kG7p7LqWwoi6xescJNcPpWF0pVQtoGGLu2SPMK9rwm7l7N5BuGdNdShUwMIgSS7AMq7tG1+1/ KHUzkZMOx8gg89rnKyYkN9LvUjpDG/JAWiptXnc/M+3yQky4brm7n+xoGQ7XoBzuFNv7ue0ma NpatCb/En3JcgmK5rcHTOhz2c8nFUil7bQPg7+Frqvt8elkrcyagonLJrRl2Q9cgFSF/pfP43 z/wUxp6XVWnVGAQY1AfQmlBTpuvCdcsWQg6dlsxeuDCg/smUnG8GmEnWPKWCiQgl8e8xthC+p kqlnrUVDNI6o0SUubA67nft/wxrIoWUuJX8lt6eLSpMrhmKCLygOinV+Mkvueb350JdGEqqrQ 9V0XzUwkCxFNs7EOC7OvdcBa5R9u32HuZvGfwagb3QmC4HareWTOffUWg9pwaI7aXTspPPv/Y NJG7lucRBiMbXdApWhfx8McEs2A9l3mJlztH73ObVEdzD3f85sDLzRdABOeoQZS1r2GTSoZXk 6qHcVKH2Ad5j2omohyFsGL9KqAXTARpj5h00GcRDI2H3l0BNUynLH3IsjTm8e9XjxJlCDvyHb lmvPLB6ngNyzV3chHvvYfQ2nsjG+g1FiUFBy6LXFO4jAGhqqzWS/aylcyCYZUZt4o9rfqG1uM k6s7/pnXmCMxA8+9z Archived-At: Subject: Re: [xml2rfc] Acknowledgments in Back? X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 May 2020 15:51:39 -0000 On 21.05.2020 17:23, Robert Moskowitz wrote: > Carsten mentioned that Acknowledgments now belong in the back: > > "the Acknowledgements section to the back material, as now required by > RFC 7322 Section 4.10 [1]" > > But in the draft I am currently working on in xml2rfc --v3 > > draft-moskowitz-orchid-cshake-01.xml(361): Error: Invalid attribute > numbered for element section, at /rfc/back/section[2] > draft-moskowitz-orchid-cshake-01.xml(13): Error: Invalid document before > running preptool. > > I put the Acknowledgements after my one appendix in the back. > > The Acknowledgements section starts with: > >

Acknowledgments > > I also tried: > >

> > > Same error. > > > What perhaps am I doing wrong? See . Try numbered=3D"false" Best regards, Julian From nobody Thu May 21 09:04:36 2020 Return-Path: X-Original-To: xml2rfc@ietfa.amsl.com Delivered-To: xml2rfc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CE413A040C for ; Thu, 21 May 2020 09:04:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 TnrGd_1VJjrS for ; Thu, 21 May 2020 09:04:30 -0700 (PDT) Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (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 0061E3A041E for ; Thu, 21 May 2020 09:04:03 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id A507862196; Thu, 21 May 2020 12:04:02 -0400 (EDT) X-Virus-Scanned: amavisd-new at htt-consult.com Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id J+P5ndAcMUh6; Thu, 21 May 2020 12:03:57 -0400 (EDT) Received: from lx140e.htt-consult.com (unknown [192.168.160.29]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 1510262162; Thu, 21 May 2020 12:03:57 -0400 (EDT) To: Julian Reschke , "xml2rfc@ietf.org" References: <95b07998-22e3-dd37-5973-4bd96ff5bee0@gmx.de> From: Robert Moskowitz Message-ID: Date: Thu, 21 May 2020 12:03:54 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0 MIME-Version: 1.0 In-Reply-To: <95b07998-22e3-dd37-5973-4bd96ff5bee0@gmx.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Archived-At: Subject: Re: [xml2rfc] Acknowledgments in Back? X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 May 2020 16:04:34 -0000 On 5/21/20 11:51 AM, Julian Reschke wrote: > On 21.05.2020 17:23, Robert Moskowitz wrote: >> Carsten mentioned that Acknowledgments now belong in the back: >> >> "the Acknowledgements section to the back material, as now required by >> RFC 7322 Section 4.10 [1]" >> >> But in the draft I am currently working on in xml2rfc --v3 >> >> draft-moskowitz-orchid-cshake-01.xml(361): Error: Invalid attribute >> numbered for element section, at /rfc/back/section[2] >> draft-moskowitz-orchid-cshake-01.xml(13): Error: Invalid document before >> running preptool. >> >> I put the Acknowledgements after my one appendix in the back. >> >> The Acknowledgements section starts with: >> >>

Acknowledgments >> >> I also tried: >> >>

>> >> >> Same error. >> >> >> What perhaps am I doing wrong? > > See > . > > Try > > numbered="false" Thanks. That was the needed piece of magic... > > Best regards, Julian > > From nobody Thu May 21 14:04:01 2020 Return-Path: X-Original-To: xml2rfc@ietfa.amsl.com Delivered-To: xml2rfc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A481B3A0AE1 for ; Thu, 21 May 2020 14:03:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.897 X-Spam-Level: X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 xx5PZCGT8wdk for ; Thu, 21 May 2020 14:03:57 -0700 (PDT) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E8E63A0A88 for ; Thu, 21 May 2020 14:03:56 -0700 (PDT) Received: from [192.168.217.119] (p548dc699.dip0.t-ipconnect.de [84.141.198.153]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 49Shtf66xSzyd1; Thu, 21 May 2020 23:03:54 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) From: Carsten Bormann In-Reply-To: <95b07998-22e3-dd37-5973-4bd96ff5bee0@gmx.de> Date: Thu, 21 May 2020 23:03:54 +0200 Cc: Robert Moskowitz , "xml2rfc@ietf.org" X-Mao-Original-Outgoing-Id: 611787833.608037-d05806e0f9d65e811c8ed6f9edb998a3 Content-Transfer-Encoding: quoted-printable Message-Id: <3869F392-81AA-4915-A541-315DF39F9153@tzi.org> References: <95b07998-22e3-dd37-5973-4bd96ff5bee0@gmx.de> To: Julian Reschke X-Mailer: Apple Mail (2.3608.80.23.2.2) Archived-At: Subject: Re: [xml2rfc] Acknowledgments in Back? X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 May 2020 21:04:00 -0000 On 2020-05-21, at 17:51, Julian Reschke wrote: >=20 > See > = . > Try >=20 > numbered=3D=E2=80=9Cfalse" (And for the historians, who will want to find the source of the = confusion in a hundred years: numbered=3D=E2=80=9Cno=E2=80=9D was added in an informal manner to the = v2 syntax that is documented in RFC 7749 (2629). The first RFC that I can find that was authored with this was RFC 7401, = by a certain and others, and the last one was RFC 8649, of August 2019. Of course, =E2=80=9Cyes=E2=80=9D and =E2=80=9Cno=E2=80=9D are not = pedantically pure Boolean values, so in the name of consistency this was = changed into =E2=80=9Cfalse=E2=80=9D and =E2=80=9Ctrue=E2=80=9D. The = v2v3 converter of course understands the old attribute names; so = kramdown=E2=80=94rfc users often use them, but not all of them: RFC 8470 of September 2018 is the first RFC I can find with = numbered=3D=E2=80=9Cfalse=E2=80=9D, and this was built with = kramdown-rfc.) Gr=C3=BC=C3=9Fe, Carsten From nobody Thu May 21 14:38:11 2020 Return-Path: X-Original-To: xml2rfc@ietfa.amsl.com Delivered-To: xml2rfc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 545733A0C21 for ; Thu, 21 May 2020 14:38:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 xznfiaEY4T3u for ; Thu, 21 May 2020 14:38:05 -0700 (PDT) Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (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 E872E3A0C4C for ; Thu, 21 May 2020 14:38:04 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 140AC62196; Thu, 21 May 2020 17:38:03 -0400 (EDT) X-Virus-Scanned: amavisd-new at htt-consult.com Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id awnOaeImHOgK; Thu, 21 May 2020 17:37:56 -0400 (EDT) Received: from lx140e.htt-consult.com (unknown [192.168.160.29]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 70D8062162; Thu, 21 May 2020 17:37:54 -0400 (EDT) To: Carsten Bormann , Julian Reschke Cc: "xml2rfc@ietf.org" References: <95b07998-22e3-dd37-5973-4bd96ff5bee0@gmx.de> <3869F392-81AA-4915-A541-315DF39F9153@tzi.org> From: Robert Moskowitz Message-ID: <10d8cc06-38e0-0882-051a-4af56bd6db9a@htt-consult.com> Date: Thu, 21 May 2020 17:37:53 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0 MIME-Version: 1.0 In-Reply-To: <3869F392-81AA-4915-A541-315DF39F9153@tzi.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Archived-At: Subject: Re: [xml2rfc] Acknowledgments in Back? X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 May 2020 21:38:08 -0000 :) On 5/21/20 5:03 PM, Carsten Bormann wrote: > On 2020-05-21, at 17:51, Julian Reschke wrote: >> See >> . >> Try >> >> numbered=“false" > (And for the historians, who will want to find the source of the confusion in a hundred years: > > numbered=“no” was added in an informal manner to the v2 syntax that is documented in RFC 7749 (2629). > > The first RFC that I can find that was authored with this was RFC 7401, by a certain > > fullname="Robert Moskowitz" role="editor”> I just checked draft-ietf-hip-rfc5201-bis-20.xml, and no numbered= at all. This was put in by the RFC editor. Though it is nice to know we were the first test draft->rfc. > > and others, and the last one was RFC 8649, of August 2019. > > Of course, “yes” and “no” are not pedantically pure Boolean values, so in the name of consistency this was changed into “false” and “true”. The v2v3 converter of course understands the old attribute names; so kramdown—rfc users often use them, but not all of them: > > RFC 8470 of September 2018 is the first RFC I can find with numbered=“false”, and this was built with kramdown-rfc.) > > Grüße, Carsten > From nobody Wed May 27 04:29:07 2020 Return-Path: X-Original-To: xml2rfc@ietfa.amsl.com Delivered-To: xml2rfc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43CE23A0DA6; Wed, 27 May 2020 04:28:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 ouYxvNAq3kdO; Wed, 27 May 2020 04:28:55 -0700 (PDT) Received: from durif.tools.ietf.org (durif.tools.ietf.org [IPv6:2001:1900:3001:11::3d]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 905243A0AB9; Wed, 27 May 2020 04:28:55 -0700 (PDT) Received: from henrik by durif.tools.ietf.org with local (Exim 4.80) (envelope-from ) id 1jduEw-0007if-7I; Wed, 27 May 2020 04:28:54 -0700 To: xml2rfc-dev@ietf.org, xml2rfc@ietf.org Cc: rfc-markdown@ietf.org Message-Id: From: Henrik Levkowetz Date: Wed, 27 May 2020 04:28:54 -0700 X-SA-Exim-Connect-IP: X-SA-Exim-Rcpt-To: rfc-markdown@ietf.org, xml2rfc-dev@ietf.org, xml2rfc@ietf.org X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Scanned: No (on durif.tools.ietf.org); SAEximRunCond expanded to false X-Clacks-Overhead: GNU Terry Pratchett Archived-At: Subject: [xml2rfc] New xml2rfc release: v2.45.0 X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 May 2020 11:28:57 -0000 Hi, This is an automatic notification about a new xml2rfc release, v2.45.0, generated when running the mkrelease script. Release notes: xml2rfc (2.45.0) ietf; urgency=medium * Fixed the html rendering of with display=false. Fixes issue #516. * Fixed the text rendering of with display=false. Fixes issue #515. * Fixed an error in postal address rendering for Sweden. Fixes issue #520. * Changed the internals of the text formatter to retain
information for longer internally, in order to make
have effect in for instance

and element text. Fixes issues #508 and #513. * Fixed erroneous indentation of first line of second and following paragraphs of multi-paragraph

elements, and changed code to retain
in filled text. * Added a font-family setting for @page in PDF mode, and added code to warn about missing Roboto Mono fonts if the python-fontconfig package is available * Added instructions for RobotoMono to the installation help for the --pdf switch. -- Henrik Levkowetz 27 May 2020 04:07:48 -0700 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 http://svn.tools.ietf.org/svn/tools/xml2rfc/tags/cli/2.45.0' Regards, Henrik (via the mkrelease script) From nobody Wed May 27 06:13:32 2020 Return-Path: X-Original-To: xml2rfc@ietfa.amsl.com Delivered-To: xml2rfc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A5763A0D7C for ; Wed, 27 May 2020 06:13:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 QR9_jVcnaA4R for ; Wed, 27 May 2020 06:13:29 -0700 (PDT) Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (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 965F83A0D7D for ; Wed, 27 May 2020 06:13:29 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id E61D66233C for ; Wed, 27 May 2020 09:13:27 -0400 (EDT) X-Virus-Scanned: amavisd-new at htt-consult.com Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id aeUqQEt+Uscb for ; Wed, 27 May 2020 09:13:22 -0400 (EDT) Received: from lx140e.htt-consult.com (unknown [192.168.160.29]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 66DD762250 for ; Wed, 27 May 2020 09:13:22 -0400 (EDT) To: "xml2rfc@ietf.org" From: Robert Moskowitz Message-ID: <4676a8d6-82fa-8085-79fb-92ab7737bcb3@htt-consult.com> Date: Wed, 27 May 2020 09:13:15 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Archived-At: Subject: [xml2rfc] question about ?anchor= in xi:include X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 May 2020 13:13:31 -0000 In the usage below: Where at the beginning of there is: What value is the anchor? I can't use it in a xref target= If I leave it out, there is no difference in the resultant draft. When I look at the v3 FAQ, it seems that the anchor is used when no displayreference? thanks From nobody Wed May 27 06:28:31 2020 Return-Path: X-Original-To: xml2rfc@ietfa.amsl.com Delivered-To: xml2rfc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80CA63A0DD4 for ; Wed, 27 May 2020 06:28:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.897 X-Spam-Level: X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 IRBSye78M_3K for ; Wed, 27 May 2020 06:28:26 -0700 (PDT) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E6CFF3A0DCB for ; Wed, 27 May 2020 06:28:25 -0700 (PDT) Received: from [172.16.42.112] (p5089ae91.dip0.t-ipconnect.de [80.137.174.145]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 49XBVG1CwFz101Y; Wed, 27 May 2020 15:28:22 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) From: Carsten Bormann In-Reply-To: <4676a8d6-82fa-8085-79fb-92ab7737bcb3@htt-consult.com> Date: Wed, 27 May 2020 15:28:21 +0200 Cc: "xml2rfc@ietf.org" X-Mao-Original-Outgoing-Id: 612278901.4367369-a9f83aa6fce3800a623092f20a97928a Content-Transfer-Encoding: quoted-printable Message-Id: <4E908DDB-571E-4501-8597-52266AE46A73@tzi.org> References: <4676a8d6-82fa-8085-79fb-92ab7737bcb3@htt-consult.com> To: Robert Moskowitz X-Mailer: Apple Mail (2.3608.80.23.2.2) Archived-At: Subject: Re: [xml2rfc] question about ?anchor= in xi:include X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 May 2020 13:28:30 -0000 Hi Bob, > On 2020-05-27, at 15:13, Robert Moskowitz wrote: >=20 > In the usage below: >=20 > The HTTP query part would need to be interpreted by the bibxml server, = but it is not implemented for bibxml3 (it *is* for DOI and IANA). So = this is right now completely equivalent to: > >=20 > Where at the beginning of there is: >=20 > >=20 > What value is the anchor? I-D.card-drip-reqs > I can't use it in a xref target=3D >=20 > If I leave it out, there is no difference in the resultant draft. >=20 > When I look at the v3 FAQ, it seems that the anchor is used when no = displayreference? You use the anchor in target=3D attributes (for elements such as xref or = displayreference). The output sees the value of the to=3D attribute of the display = reference, if any, or the anchor otherwise. (This is all a bit simpler in kramdown-rfc, thanks to a contribution by = Martin Thomson: informative: drip-requirements: I-D.card-drip-reqs Then you can use {{drip-requirements}} and will see [drip-requirements] = as the displayed reference.) Gr=C3=BC=C3=9Fe, Carsten From nobody Wed May 27 06:30:43 2020 Return-Path: X-Original-To: xml2rfc@ietfa.amsl.com Delivered-To: xml2rfc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C54623A0DD5 for ; Wed, 27 May 2020 06:30:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, 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 tV1y-ABNxoYx for ; Wed, 27 May 2020 06:30:37 -0700 (PDT) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (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 458253A0E30 for ; Wed, 27 May 2020 06:30:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1590586229; bh=/fE6EqUFPSpKN8aKLUKRQM7VZpn3HoVHf+Aqo/napXw=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=dBapvzoJpZFJRXsmXn+ABAHlbilpnRGr+Qg6pFTj/aWfX+Hlg/yCXCyPSxKJ1cQSG uVTg/ECRwXwcg3SMVlnMCUUnlF0E16EfmNgyG1UtOWqJvN1+sFT7TMkB4R71vRePgc dePXLg5CgMhCBrChkbbZz/dcmn45H7M3OLQ229+8= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from [192.168.1.220] ([217.91.35.233]) by mail.gmx.com (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MJVHe-1jK3o50mZE-00JskI; Wed, 27 May 2020 15:30:29 +0200 To: Robert Moskowitz , "xml2rfc@ietf.org" References: <4676a8d6-82fa-8085-79fb-92ab7737bcb3@htt-consult.com> From: Julian Reschke Message-ID: <2b516e43-3f11-1888-c3e0-499d05c496f6@gmx.de> Date: Wed, 27 May 2020 15:30:26 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.8.1 MIME-Version: 1.0 In-Reply-To: <4676a8d6-82fa-8085-79fb-92ab7737bcb3@htt-consult.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:xF0u+qy70wOHNW1xcuHefOAaqV+i4vU9hItzcutJEiEhhOhLWCL R58x+CDNjFcG9jGWvSrYMd2vZRPIw8Aq3vzcdGxa+w+lI4jGd16vswoAzYKwcIPI04jaKZu j/L2e2aM/qxM+TyaGJOsZc0X0ptyAYyBS+fqblJasiw5dZL8kQVFduiyv5i7VUNw0HNSJ9I GRrQBuqzheOMb0GA2WcgA== X-UI-Out-Filterresults: notjunk:1;V03:K0:KsZX9Isdk/c=:T6ZKjjLvQBKHJ0Zr10MAeW /ef0uqvyhZiKFOmJ2+qeVIvMSA2+cbGq1shxBXm41Nxcif9EJu2oGpX5i+5S2BnEQk1JNnz/D L2bI9D2zJPlT/NqgAc8/teC32gkkrPp3cCu5xqYEU2JtQ8NzDHvJ5NLkwiSFG0IVVf7WV3Vuw Mauj8yZPgqufaIt5cb+tBAns80gUcPuUb7WDQ5WWpjBlzP23v+U6f/f86FRJdwDjpC0ixKmr4 SuzKbRhzk2ifYbJcum5alT0nJ7D1QDDdF4Y9g09pjN9mOtWvd9wTn49miDA0/cgS2yF/vRmNX Z7ZfoIMo+Fe/GeZW21zrAFrBGO1uM2DCvwqIUvNsE/JPHzbTTDj3+bWzbUABvatoQMQ25JyuN mi4sAwrLeen6MUGdFsD4mGsBj9Z25klVdh1eoi6sA8qCjsp5FEBiDOV36XZV7U+WaGxGBJqz2 oCG83IJ7WYYRy/81ZMACYEQqULQ9Yjhf++6M5jCxroVUCxWYPlRyM/oIFhGLG58+v+t5i/cmS jvJ1RoIh74hkfPscHMzMXNskS3CCdtaviCKhZAWD6ro2vserA0WBqdC4si4JFejbb7GymQkii 1fab2e+NTTg7XtOtnnNuXpuIRbqf4HZ/+uex9W/AGqvHx0ssLOPvs4zYq3qg1oE1PM7ayLqM9 jdTePhmW4AfQl1/gePAoM8ZwDeVS0k+3daMw0tBDMldUs9tGX58+4Gi2XK6I2X0Z+eqT8Ot6U YIPdwlmkwkc0OiaPBNqT7xcanev9ag82UBP1f3x+nrYY59x192iIQJUqhBoQE4xDg7d12LWpG fG1SOFPhLMeK30T4IRaScLWRiNvN716T66znhQQwGOkvycj0h3zxUvNmmeFNjG6carmNvIGmw n3F9r5UlZQl08NrPRimn/HjWp3jfVLOGh2wZR/G9ZTyx+Df8hEUw5078oTV9qQ/KO0d42j79J /pdY2zsnTefJO2V0P7UTe+CF2FU8Gq2S6Z+VMkwZl52clHbObZgZnzu7oGvoJUxtLYyghjjAD doQPD4M2PuPu1YbYs4UG0WzDFOoIY1ispxnm0Qxj6SeDw2pMhvIpBeKDA/s6/FYF1Qvm/CPI1 kcG7EirVAtLrC/ZnBrNdGwPVnO7XGARgwvR3e06JHEhyZiEkE+ozCh5Th6EVQ9bFQSqmTFZYi HhovCjU4VWoWlWo2WaRLHMTSUChq2fFB85M5bN0sLAKPZiIgy0uHK5QnTRJi+F6G1b/ZptfWE ZcxKOyRtxcyR3ilM1 Archived-At: Subject: Re: [xml2rfc] question about ?anchor= in xi:include X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 May 2020 13:30:42 -0000 On 27.05.2020 15:13, Robert Moskowitz wrote: > In the usage below: > > href=3D"https://xml2rfc.tools.ietf.org/public/rfc/bibxml3/reference.I-D.= card-drip-reqs.xml?anchor=3Ddrip-reqs"/> > > > Where at the beginning of there is: > > > > What value is the anchor? In the URI https://xml2rfc.tools.ietf.org/public/rfc/bibxml3/reference.I-D.card-drip-= reqs.xml?anchor=3Ddrip-reqs the "anchor" query parameter doesn't seem to be used; the XML is: Drone Remote Identification Protocol (DRIP) Requirements This document defines the requirements for Drone Remote Identification Protocol (DRIP) Working Group protocols and services to support Unmanned Aircraft System Remote Identification (UAS RID). Objectives include: complementing external technical standards as regulator-accepted means of compliance with UAS RID regulations; facilitating use of existing Internet resources to support UAS RID and to enable enhanced related services; and enabling verification that UAS RID information is trustworthy (to some extent, even in the absence of Internet connectivity at the receiving node). So, as anchor you'll need to use "I-D.card-drip-reqs". The just changes what's displayed in the references. > I can't use it in a xref target=3D You are not supposed to :-) > If I leave it out, there is no difference in the resultant draft. > > When I look at the v3 FAQ, it seems that the anchor is used when no > displayreference? only affects *display*. See . Best regards, Julian From nobody Wed May 27 06:40:02 2020 Return-Path: X-Original-To: xml2rfc@ietfa.amsl.com Delivered-To: xml2rfc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6ABC53A0A94 for ; Wed, 27 May 2020 06:40:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 eDvh5uR6Fhtk for ; Wed, 27 May 2020 06:39:59 -0700 (PDT) Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (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 AEA623A0A8C for ; Wed, 27 May 2020 06:39:59 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 901236233C; Wed, 27 May 2020 09:39:58 -0400 (EDT) X-Virus-Scanned: amavisd-new at htt-consult.com Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id KrQw9XXVFGIy; Wed, 27 May 2020 09:39:53 -0400 (EDT) Received: from lx140e.htt-consult.com (unknown [192.168.160.29]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 375C662250; Wed, 27 May 2020 09:39:50 -0400 (EDT) To: Julian Reschke , "xml2rfc@ietf.org" References: <4676a8d6-82fa-8085-79fb-92ab7737bcb3@htt-consult.com> <2b516e43-3f11-1888-c3e0-499d05c496f6@gmx.de> From: Robert Moskowitz Message-ID: <58060c12-55d6-91f8-8a65-61813c9cfc10@htt-consult.com> Date: Wed, 27 May 2020 09:39:50 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0 MIME-Version: 1.0 In-Reply-To: <2b516e43-3f11-1888-c3e0-499d05c496f6@gmx.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Archived-At: Subject: Re: [xml2rfc] question about ?anchor= in xi:include X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 May 2020 13:40:02 -0000 thank you Carsten and Julian. On 5/27/20 9:30 AM, Julian Reschke wrote: > On 27.05.2020 15:13, Robert Moskowitz wrote: >> In the usage below: >> >> > href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml3/reference.I-D.card-drip-reqs.xml?anchor=drip-reqs"/> >> >> >> >> Where at the beginning of there is: >> >> >> >> What value is the anchor? > > In the URI > > > https://xml2rfc.tools.ietf.org/public/rfc/bibxml3/reference.I-D.card-drip-reqs.xml?anchor=drip-reqs > > > the "anchor" query parameter doesn't seem to be used; the XML is: > > > > Drone Remote Identification Protocol (DRIP) Requirements > > > > > > > > > > > > > > > > This document defines the requirements for Drone Remote > Identification Protocol (DRIP) Working Group protocols and services to > support Unmanned Aircraft System Remote Identification (UAS RID). > Objectives include: complementing external technical standards as > regulator-accepted means of compliance with UAS RID regulations; > facilitating use of existing Internet resources to support UAS RID and > to enable enhanced related services; and enabling verification that UAS > RID information is trustworthy (to some extent, even in the absence of > Internet connectivity at the receiving node). > > > > > target="http://www.ietf.org/internet-drafts/draft-card-drip-reqs-02.txt"/> > > > > > So, as anchor you'll need to use "I-D.card-drip-reqs". The > just changes what's displayed in the references. > >> I can't use it in a xref target= > > You are not supposed to :-) > >> If I leave it out, there is no difference in the resultant draft. >> >> When I look at the v3 FAQ, it seems that the anchor is used when no >> displayreference? > > only affects *display*. See > . > > > > Best regards, Julian From nobody Fri May 29 12:56:57 2020 Return-Path: X-Original-To: xml2rfc@ietfa.amsl.com Delivered-To: xml2rfc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 508923A102B; Fri, 29 May 2020 12:56:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.898 X-Spam-Level: X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 hyZO1s31wMec; Fri, 29 May 2020 12:56:43 -0700 (PDT) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A6D5D3A1029; Fri, 29 May 2020 12:56:43 -0700 (PDT) Received: from [172.16.42.112] (p5089ae91.dip0.t-ipconnect.de [80.137.174.145]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 49Yb1P6sqLzydq; Fri, 29 May 2020 21:56:41 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) From: Carsten Bormann In-Reply-To: Date: Fri, 29 May 2020 21:56:41 +0200 Cc: xml2rfc-dev@ietf.org, xml2rfc@ietf.org, rfc-markdown@ietf.org X-Mao-Original-Outgoing-Id: 612475001.437464-8547a85ec6df2a072461d9666d7e7b8f Content-Transfer-Encoding: quoted-printable Message-Id: <93E5295E-CE96-4121-B3F5-C04540D542FD@tzi.org> References: To: Henrik Levkowetz X-Mailer: Apple Mail (2.3608.80.23.2.2) Archived-At: Subject: [xml2rfc] SVG broken (Re: [xml2rfc-dev] New xml2rfc release: v2.45.0) X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 May 2020 19:56:48 -0000 Hi Henrik, I no longer get SVG through this version that has been =E2=80=9Crepaired=E2= =80=9D by svgcheck -qra; the SVG processing now seems very picky. (I = haven=E2=80=99t updated since 2.39, so this might have happened = earlier.) (I do get figures through this version that have the attribute = foo=3D=E2=80=9Cbar=E2=80=9D, so it can=E2=80=99t just be more picky XML = processing.) Before I generate a more detailed test case: Is svgcheck still intended = to be the tool to be used with xml2rfc to make SVG palatable to it? Is = that being updated along with xml2rfc getting more picky? Gr=C3=BC=C3=9Fe, Carsten y2020-05-29svg.xml(606): Error: Invalid attribute shape-rendering for = element svg, at /rfc/middle/section[2]/section[2]/artset[1]/artwork[1]/* y2020-05-29svg.xml(645): Error: Invalid attribute stroke for element = text, at = /rfc/middle/section[2]/section[2]/artset[2]/artwork[1]/*/*[2]/*[7] y2020-05-29svg.xml(646): Error: Invalid attribute stroke for element = text, at = /rfc/middle/section[2]/section[2]/artset[2]/artwork[1]/*/*[2]/*[8] y2020-05-29svg.xml(647): Error: Invalid attribute stroke for element = text, at = /rfc/middle/section[2]/section[2]/artset[2]/artwork[1]/*/*[2]/*[9] y2020-05-29svg.xml(648): Error: Invalid attribute stroke for element = text, at = /rfc/middle/section[2]/section[2]/artset[2]/artwork[1]/*/*[2]/*[10] y2020-05-29svg.xml(635): Error: Invalid attribute shape-rendering for = element svg, at /rfc/middle/section[2]/section[2]/artset[2]/artwork[1]/* y2020-05-29svg.xml(666): Error: Invalid attribute stroke for element = path, at = /rfc/middle/section[2]/section[2]/artset[3]/artwork[1]/*/*[2]/*[4] y2020-05-29svg.xml(670): Error: Invalid attribute stroke for element = text, at = /rfc/middle/section[2]/section[2]/artset[3]/artwork[1]/*/*[2]/*[8] y2020-05-29svg.xml(671): Error: Invalid attribute stroke for element = text, at = /rfc/middle/section[2]/section[2]/artset[3]/artwork[1]/*/*[2]/*[9] y2020-05-29svg.xml(672): Error: Invalid attribute stroke for element = text, at = /rfc/middle/section[2]/section[2]/artset[3]/artwork[1]/*/*[2]/*[10] y2020-05-29svg.xml(659): Error: Invalid attribute shape-rendering for = element svg, at /rfc/middle/section[2]/section[2]/artset[3]/artwork[1]/* y2020-05-29svg.xml(692): Error: Invalid attribute stroke for element = text, at = /rfc/middle/section[2]/section[2]/artset[4]/artwork[1]/*/*[2]/*[8] y2020-05-29svg.xml(693): Error: Invalid attribute stroke for element = text, at = /rfc/middle/section[2]/section[2]/artset[4]/artwork[1]/*/*[2]/*[9] y2020-05-29svg.xml(694): Error: Invalid attribute stroke for element = text, at = /rfc/middle/section[2]/section[2]/artset[4]/artwork[1]/*/*[2]/*[10] y2020-05-29svg.xml(695): Error: Invalid attribute stroke for element = text, at = /rfc/middle/section[2]/section[2]/artset[4]/artwork[1]/*/*[2]/*[11] y2020-05-29svg.xml(696): Error: Invalid attribute stroke for element = text, at = /rfc/middle/section[2]/section[2]/artset[4]/artwork[1]/*/*[2]/*[12] From nobody Fri May 29 14:29:20 2020 Return-Path: X-Original-To: xml2rfc@ietfa.amsl.com Delivered-To: xml2rfc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCB5E3A10BD; Fri, 29 May 2020 14:29:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.897 X-Spam-Level: X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 Z3fIsErjFyCM; Fri, 29 May 2020 14:29:08 -0700 (PDT) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 25CE63A10BC; Fri, 29 May 2020 14:29:08 -0700 (PDT) Received: from [172.16.42.112] (p5089ae91.dip0.t-ipconnect.de [80.137.174.145]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 49Yd4253qQzyVK; Fri, 29 May 2020 23:29:06 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) From: Carsten Bormann In-Reply-To: <93E5295E-CE96-4121-B3F5-C04540D542FD@tzi.org> Date: Fri, 29 May 2020 23:29:06 +0200 Cc: xml2rfc-dev@ietf.org, xml2rfc@ietf.org, rfc-markdown@ietf.org X-Mao-Original-Outgoing-Id: 612480546.2601579-5f6d26a63098ed057328a975374b2901 Content-Transfer-Encoding: quoted-printable Message-Id: References: <93E5295E-CE96-4121-B3F5-C04540D542FD@tzi.org> To: Henrik Levkowetz X-Mailer: Apple Mail (2.3608.80.23.2.2) Archived-At: Subject: Re: [xml2rfc] SVG broken (Re: [xml2rfc-dev] New xml2rfc release: v2.45.0) X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 May 2020 21:29:11 -0000 On 2020-05-29, at 21:56, Carsten Bormann wrote: >=20 > I no longer get SVG through this version that has been =E2=80=9Crepaired= =E2=80=9D by svgcheck -qra; the SVG processing now seems very picky. (I = haven=E2=80=99t updated since 2.39, so this might have happened = earlier.) Well, OK, this is now SVG generated by ditaa instead of goat, and ditaa = seems to want to show of its knowledge of SVG some more. So that may = not be a change in xml2rfc at all. My question is mostly still valid, = though: > Is svgcheck still intended to be the tool to be used with xml2rfc to = make SVG palatable to it? Is that being updated along with xml2rfc ...? Gr=C3=BC=C3=9Fe, Carsten From nobody Fri May 29 16:25:00 2020 Return-Path: X-Original-To: xml2rfc@ietfa.amsl.com Delivered-To: xml2rfc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD3F93A11AA; Fri, 29 May 2020 16:24:48 -0700 (PDT) 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, FREEMAIL_FROM=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 (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 O_YkOtwVcHev; Fri, 29 May 2020 16:24:47 -0700 (PDT) Received: from mail-pj1-x1033.google.com (mail-pj1-x1033.google.com [IPv6:2607:f8b0:4864:20::1033]) (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 6E9CE3A11A9; Fri, 29 May 2020 16:24:47 -0700 (PDT) Received: by mail-pj1-x1033.google.com with SMTP id s88so1507008pjb.5; Fri, 29 May 2020 16:24:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=CpUku3ZdPq2HSt3j4A2YJNeryBJoOuUC0Hezs8OsBwE=; b=DoiK9jITejOSaS4h7OedMQ0N24Gz8+KZHQzYsmgW/sfgHGDYFdz7SKI3s5aSAz6sKL tiwn3mgwRQcKgEGQuOG1axdsLvxGx6+HiF6Dxfu10gX+8Buq1BIzQIK/qkCEosyj7jIH avn4em/b55VfNcumlS9pEWHbmkR3abNLDalOZtcrAwLs31IwSre83lpsutiR9oI+d3w7 ebkj0OJbdTxuB90i1s5ZQE9NfLeeXxpwsZGKFwtrsbZahY0AZ2xeY0Qs82M69xirFu/z zs5JqvS5i9hi8A90J/hu8y414eh+YQxJFQ5X9up/O34e+Z0lbqGbLRowkSxOvEpaoxD6 zH9w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=CpUku3ZdPq2HSt3j4A2YJNeryBJoOuUC0Hezs8OsBwE=; b=rQq62Pubk5pgzCvF5CPFMdbEZBuP4ZezXVZr6fQTh/RmUQHR7or7sd3fS0zq5VrbS/ tNPcYJL32QTahTTrAQHQLPtCWb9W6jsQOAZNSX6BgAOSViNOoMJ8nBbNp6Ax+qw5SZ9l JWKps1nXhP3Qjd61dXIIYtNtQKBkXQZhTXRlnlhcMCeisWcF86/3LcgCCXHuKYCRiK09 Ch9NT8xzlTkX7g23HT0FMxCDq+MbnVmpAnR58XV4NkuMHJoN1F2NHNMTKHMZ8iTu91ix Laac6SFfTLXsItT+HsGfyci7D7vaiSsdp8z+H359svmkzuBTbqRE57sFdcIw/9/jb8oC YmNA== X-Gm-Message-State: AOAM530PYmYMvgm+d0OpP0JHr4LGTaz8jvIfYGxReq0eV41A/aSm4cay wphNi/dPcKEiSTqw6d54dVk3s3uJs2g= X-Google-Smtp-Source: ABdhPJyWbUUJhR4+n2NDiAZZb3TMcUipZkSG/K3sDsJp6Q60RPpX7oOk4smXcZecpuUwQbvXD1upUg== X-Received: by 2002:a17:90a:fd85:: with SMTP id cx5mr11549770pjb.146.1590794686599; Fri, 29 May 2020 16:24:46 -0700 (PDT) Received: from [192.168.178.30] ([165.84.12.178]) by smtp.gmail.com with ESMTPSA id t201sm5374063pfc.104.2020.05.29.16.24.43 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 29 May 2020 16:24:45 -0700 (PDT) To: Carsten Bormann , Henrik Levkowetz Cc: rfc-markdown@ietf.org, xml2rfc@ietf.org, xml2rfc-dev@ietf.org References: <93E5295E-CE96-4121-B3F5-C04540D542FD@tzi.org> From: Brian E Carpenter Message-ID: <1a5cfced-2718-0a4a-41ef-b366543ec5a2@gmail.com> Date: Sat, 30 May 2020 11:24:40 +1200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Archived-At: Subject: Re: [xml2rfc] SVG broken (Re: [xml2rfc-dev] New xml2rfc release: v2.45.0) X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 May 2020 23:24:49 -0000 Do you know what bit of SVG it is barfing on? I'm curious because I've done some personal patching of svgcheck and disc= overed what a minefield this all is. Indeed, some drawing tools produce s= tuff that others don't, so there is a strong element of crapshoot. Regards Brian On 30-May-20 09:29, Carsten Bormann wrote: > On 2020-05-29, at 21:56, Carsten Bormann wrote: >> >> I no longer get SVG through this version that has been =E2=80=9Crepair= ed=E2=80=9D by svgcheck -qra; the SVG processing now seems very picky. (= I haven=E2=80=99t updated since 2.39, so this might have happened earlier= =2E) >=20 > Well, OK, this is now SVG generated by ditaa instead of goat, and ditaa= seems to want to show of its knowledge of SVG some more. So that may no= t be a change in xml2rfc at all. My question is mostly still valid, thou= gh: >=20 >> Is svgcheck still intended to be the tool to be used with xml2rfc to m= ake SVG palatable to it? Is that being updated along with xml2rfc ...? >=20 > Gr=C3=BC=C3=9Fe, Carsten >=20 > _______________________________________________ > xml2rfc mailing list > xml2rfc@ietf.org > https://www.ietf.org/mailman/listinfo/xml2rfc >=20 From nobody Fri May 29 19:43:38 2020 Return-Path: X-Original-To: xml2rfc@ietfa.amsl.com Delivered-To: xml2rfc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B55773A1316; Fri, 29 May 2020 19:43:32 -0700 (PDT) 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, FREEMAIL_FROM=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 (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 Ebq2Ew7XkNR9; Fri, 29 May 2020 19:43:31 -0700 (PDT) Received: from mail-wr1-x42b.google.com (mail-wr1-x42b.google.com [IPv6:2a00:1450:4864:20::42b]) (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 2B9753A1315; Fri, 29 May 2020 19:43:31 -0700 (PDT) Received: by mail-wr1-x42b.google.com with SMTP id x13so6010677wrv.4; Fri, 29 May 2020 19:43:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=+i9t7roWmBvJ7/cTs8s5DFUIMDkYkYlCup+c67H19MQ=; b=byhMlkJUK6lG6moE+8LOBx7apuXhJrf0PbDcCQW78iUeMSCmrv86saDX1+v6HgUOlE bofWh6L68bpK0wYoPHLH6ElvcnvUkNi6nm9PCRZT+IRH5wEk5jNxz+PZgcZXPbtTM3kJ /f2vbzQ5MqBxE44VWlY7dwHWswOrZ36zlL/4XtVybgPvJh+jNW0PfZ7paWsTQEA+yijm OAdKAGbvVIC9u4MZ9nnHo/C8vkXV0oPA5DiF/wVH2sSjq2O+YhUiEHleYkxcgIz6Vz2n 25ndVlVtI15nvsvL6zp4A+4Uesey1+gl9/V1BO/el0BY/ISucC2gO9CMERLU9I8m1Dix 6oGg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=+i9t7roWmBvJ7/cTs8s5DFUIMDkYkYlCup+c67H19MQ=; b=nHMbIUEPRilahBjSCuzFoOeYioOsmXPYBOxxhS5iQ33h79BgmMsddnLOr1dRB3LoxE muhYHe5y6daJyEKHTfZ1lwzGoFedMPve4psyow2WUjjZUhkll5tEiy8gshdbo40dxJBh PvM5HwyMSaWdI8Y8ACaIl5TX7DJpfkcWCbQO3KWQfZ4pvkRMhV/DoFjT+RDg83JFHXoQ k01AAh6U7SvaX81Imxv6c+crcOq4hDkN42jHrRY+dlLhV74AJmCh81WSyetBKqIh8YhT xrZ3sx3DxAzENn0qrApVea2dv11ivSY8kqHLT/jy4uRQ5yAid8hFk9myoypi7sYUSiJj q10w== X-Gm-Message-State: AOAM531Alkc9UN0AskwFUV9bVkhNCg1XWTAceMTeXU5yHiUEfEhScaXZ aOb7+kzw9uw0y6wGmd4LW9s74ePn5Xc= X-Google-Smtp-Source: ABdhPJzAhMnQg+ngKM90rk4pnML4zfHug+uweuikORovPSav+hlFTSnVFznEFkDDpid255wc2TAHYQ== X-Received: by 2002:a5d:60c3:: with SMTP id x3mr10899893wrt.48.1590806607711; Fri, 29 May 2020 19:43:27 -0700 (PDT) Received: from [192.168.1.79] (25.131.146.77.rev.sfr.net. [77.146.131.25]) by smtp.googlemail.com with ESMTPSA id c140sm1739361wmd.18.2020.05.29.19.43.26 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 29 May 2020 19:43:27 -0700 (PDT) To: Henrik Levkowetz , xml2rfc@ietf.org Cc: rfc-markdown@ietf.org References: From: Anders Rundgren Message-ID: Date: Sat, 30 May 2020 04:43:23 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.8.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Archived-At: Subject: [xml2rfc] RfcMarkup ToC has no links X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 May 2020 02:43:33 -0000 sample RFC: https://tools.ietf.org/html/rfc8759 That the page number links are gone is understandable since there (fortunately) is no paging anymore but removing links for headers seem illogical in an HTML formatted document. I understand that the IETF want to retire the RfcMarkup format but since the IETF apparently still publish in this format, shouldn't also stay useful? I'm currently in the auth48 state and the on-line xml2rfc tool produces ToC links for appendices(!). Is that a bug or a feature? thanx, Anders From nobody Fri May 29 23:42:24 2020 Return-Path: X-Original-To: xml2rfc@ietfa.amsl.com Delivered-To: xml2rfc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF0453A1483; Fri, 29 May 2020 23:42:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.897 X-Spam-Level: X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 srvu5e3DGiWO; Fri, 29 May 2020 23:42:19 -0700 (PDT) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 21CAD3A1481; Fri, 29 May 2020 23:42:19 -0700 (PDT) Received: from [172.16.42.112] (p5089ae91.dip0.t-ipconnect.de [80.137.174.145]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 49YsLJ503nzyv7; Sat, 30 May 2020 08:42:16 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) From: Carsten Bormann In-Reply-To: <1a5cfced-2718-0a4a-41ef-b366543ec5a2@gmail.com> Date: Sat, 30 May 2020 08:42:16 +0200 Cc: Henrik Levkowetz , rfc-markdown@ietf.org, xml2rfc@ietf.org, xml2rfc-dev@ietf.org X-Mao-Original-Outgoing-Id: 612513736.276876-a855b7e3f7abe0dff0fd4c3676353ece Content-Transfer-Encoding: quoted-printable Message-Id: <3E78C586-228A-457E-BADD-D66117FFD1C0@tzi.org> References: <93E5295E-CE96-4121-B3F5-C04540D542FD@tzi.org> <1a5cfced-2718-0a4a-41ef-b366543ec5a2@gmail.com> To: Brian E Carpenter X-Mailer: Apple Mail (2.3608.80.23.2.2) Archived-At: Subject: Re: [xml2rfc] [Rfc-markdown] SVG broken (Re: [xml2rfc-dev] New xml2rfc release: v2.45.0) X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 May 2020 06:42:23 -0000 Hi Brian, > On 2020-05-30, at 01:24, Brian E Carpenter = wrote: >=20 > Do you know what bit of SVG it is barfing on? I had some error messages in my first message. Let me expand on these: AFAICS this is all about attributes that xml2rfc does not accept on = specific SVG elements. Consolidating these messages a bit, I get: y.xml(722): Error: Invalid attribute shape-rendering for element svg, = [=E2=80=A6] y.xml(776): Error: Invalid attribute stroke for element path, [=E2=80=A6] y.xml(818): Error: Invalid attribute stroke for element text, [=E2=80=A6] (And then, apparently as a result of these: y.xml(14): Error: Invalid document before running preptool. .) Well, this is not the whole story, as stroke needs to be a valid = attribute for path; this seems to be about the value stroke=3D"#000000=E2=80= =9D for path (which probably needs to be replaced by stroke=3D=E2=80=9Cbla= ck=E2=80=9D) and stroke=3D"none=E2=80=9D for text (which probably is = default anyway). This was for ditaa. With mscgen, I additionally get: ymscgen.xml(87): Error: Invalid attribute text-rendering for element = svg, [=E2=80=A6] > I'm curious because I've done some personal patching of svgcheck and = discovered what a minefield this all is. Indeed, some drawing tools = produce stuff that others don't, so there is a strong element of = crapshoot. Yes, those words describe it pretty well. Of course, I could easily integrate my own additions of svgcheck-like = processing into kramdown-rfc. Unfortunately, adding serious XML processing adds some deployment = considerations (one would normally use a gem that causes some = installation difficulties on older platforms as it requires compiling = native code). Gr=C3=BC=C3=9Fe, Carsten >=20 > Regards > Brian >=20 > On 30-May-20 09:29, Carsten Bormann wrote: >> On 2020-05-29, at 21:56, Carsten Bormann wrote: >>>=20 >>> I no longer get SVG through this version that has been = =E2=80=9Crepaired=E2=80=9D by svgcheck -qra; the SVG processing now = seems very picky. (I haven=E2=80=99t updated since 2.39, so this might = have happened earlier.) >>=20 >> Well, OK, this is now SVG generated by ditaa instead of goat, and = ditaa seems to want to show of its knowledge of SVG some more. So that = may not be a change in xml2rfc at all. My question is mostly still = valid, though: >>=20 >>> Is svgcheck still intended to be the tool to be used with xml2rfc to = make SVG palatable to it? Is that being updated along with xml2rfc ...? >>=20 >> Gr=C3=BC=C3=9Fe, Carsten >>=20 >> _______________________________________________ >> xml2rfc mailing list >> xml2rfc@ietf.org >> https://www.ietf.org/mailman/listinfo/xml2rfc >>=20 >=20 > _______________________________________________ > Rfc-markdown mailing list > Rfc-markdown@ietf.org > https://www.ietf.org/mailman/listinfo/rfc-markdown From nobody Sat May 30 04:56:38 2020 Return-Path: X-Original-To: xml2rfc@ietfa.amsl.com Delivered-To: xml2rfc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B68E23A0A3C; Sat, 30 May 2020 04:56:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 zdmkdW0T6FG1; Sat, 30 May 2020 04:56:31 -0700 (PDT) Received: from durif.tools.ietf.org (durif.tools.ietf.org [IPv6:2001:1900:3001:11::3d]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BBDDF3A09DD; Sat, 30 May 2020 04:56:31 -0700 (PDT) Received: from henrik by durif.tools.ietf.org with local (Exim 4.80) (envelope-from ) id 1jf06J-0000A8-Hw; Sat, 30 May 2020 04:56:31 -0700 To: xml2rfc-dev@ietf.org, xml2rfc@ietf.org Cc: rfc-markdown@ietf.org Message-Id: From: Henrik Levkowetz Date: Sat, 30 May 2020 04:56:31 -0700 X-SA-Exim-Connect-IP: X-SA-Exim-Rcpt-To: rfc-markdown@ietf.org, xml2rfc-dev@ietf.org, xml2rfc@ietf.org X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Scanned: No (on durif.tools.ietf.org); SAEximRunCond expanded to false X-Clacks-Overhead: GNU Terry Pratchett Archived-At: Subject: [xml2rfc] New xml2rfc release: v2.45.1 X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 May 2020 11:56:37 -0000 Hi, This is an automatic notification about a new xml2rfc release, v2.45.1, generated when running the mkrelease script. Release notes: xml2rfc (2.45.1) ietf; urgency=medium * Changed the handling of hyphens in table cells, so as to introduce line breaks on hyphens if necessary to keep a table from becoming too wide (but not otherwise). The --table-hyphen-breaks switch can be used to permit line breaks on hyphens in table cells also for tables that would not otherwise become too wide. * Added a switch --table-hyphen-breaks that will make the text renderer more eager to break on hyphens in table cells. * Using a pilcrow on an otherwise empty element added unwanted vertical space in the HTML output; avoid this. Related to issue #508. * Added a parameter to TextSplitter to control whether text is split on hyphens or not. -- Henrik Levkowetz 30 May 2020 11:52:33 +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 http://svn.tools.ietf.org/svn/tools/xml2rfc/tags/cli/2.45.1' Regards, Henrik (via the mkrelease script) From nobody Sat May 30 09:23:30 2020 Return-Path: X-Original-To: xml2rfc@ietfa.amsl.com Delivered-To: xml2rfc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A66913A0BFE; Sat, 30 May 2020 09:23:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.897 X-Spam-Level: X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 MkGNU6ZdMhRA; Sat, 30 May 2020 09:23:16 -0700 (PDT) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D7AEC3A0B83; Sat, 30 May 2020 09:23:15 -0700 (PDT) Received: from [172.16.42.112] (p5089ae91.dip0.t-ipconnect.de [80.137.174.145]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 49Z6DZ21lPzywH; Sat, 30 May 2020 18:23:10 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) From: Carsten Bormann In-Reply-To: <3E78C586-228A-457E-BADD-D66117FFD1C0@tzi.org> Date: Sat, 30 May 2020 18:23:04 +0200 Cc: xml2rfc@ietf.org, xml2rfc-dev@ietf.org X-Mao-Original-Outgoing-Id: 612548584.348489-409d5241980178212151b0d797ef191e Content-Transfer-Encoding: quoted-printable Message-Id: References: <93E5295E-CE96-4121-B3F5-C04540D542FD@tzi.org> <1a5cfced-2718-0a4a-41ef-b366543ec5a2@gmail.com> <3E78C586-228A-457E-BADD-D66117FFD1C0@tzi.org> To: rfc-markdown@ietf.org X-Mailer: Apple Mail (2.3608.80.23.2.2) Archived-At: Subject: [xml2rfc] 1.3.7: supporting ditaa, mscgen in -3 mode X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 May 2020 16:23:21 -0000 On 2020-05-30, at 08:42, Carsten Bormann wrote: >=20 > Of course, I could easily integrate my own additions of svgcheck-like = processing into kramdown-rfc. > Unfortunately, adding serious XML processing adds some deployment = considerations (one would normally use a gem that causes some = installation difficulties on older platforms as it requires compiling = native code). Well, I chose an older gem that doesn=E2=80=99t have this problem (but = is quite slow and less tested); I can now do svgcheck workarounds and am = doing those for the breakage I have seen for ditaa and mscgen. So kramdown-rfc2629 version 1.3.7 now supports ditaa and mscgen (in = addition to goat, which was added in 1.3.2) for automatic artset = generation. =20 So, for instance, you can now write ~~~ mscgen msc { a,b,c; a->b [label=3D"ab()"] ; b->c [label=3D"bc(TRUE)"]; c=3D>c [label=3D"process(1)"]; c=3D>c [label=3D"process(2)"]; ...; c=3D>c [label=3D"process(n)"]; c=3D>c [label=3D"process(END)"]; a<<=3Dc [label=3D"callback()"]; --- [label=3D"If more to run", ID=3D"*"]; a->a [label=3D"next()"]; a->c [label=3D"ac()"]; b<-c [label=3D"cb(TRUE)"]; b->b [label=3D"stalled(...)"]; a<-b [label=3D"ab() =3D FALSE"]; } ~~~ and get what you can see at http://www.tzi.de/~cabo/1-3-7-mscgen.png . As usual, update with gem update kramdown-rfc2629 The tool that you want to use (goat, mscgen, or ditaa) needs to be = installed and on the path of the process that runs kramdown-rfc. If there is any other tool like that that you=E2=80=99d like to see = supported, and it produces SVG that can be made palatable to xml2rfc = without superhuman effort, please tell me. There is no doubt that you can write ditaa that will break svgcheck=E2=80=99= s (and my workarounds=E2=80=99) little mind; e.g., preferably, try to = stay black-and-white. Note that for mscgen, the mscgen source may not exactly be what you want = in a plaintext-based RFC (but the SVG output is probably what you do = want in your HTML renderings); I=E2=80=99d appreciate any proposals on = how to turn mscgen into ASCII art=E2=80=A6 Gr=C3=BC=C3=9Fe, Carsten From nobody Sat May 30 11:22:07 2020 Return-Path: X-Original-To: xml2rfc@ietfa.amsl.com Delivered-To: xml2rfc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F15D3A09D7; Sat, 30 May 2020 11:21:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.1 X-Spam-Level: X-Spam-Status: No, score=-2.1 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, 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=bangj.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 D19tK4bKbNxd; Sat, 30 May 2020 11:21:54 -0700 (PDT) Received: from oj.bangj.com (69-77-154-174.static.skybest.com [69.77.154.174]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 46EB03A09D3; Sat, 30 May 2020 11:21:50 -0700 (PDT) Received: from [172.16.25.146] (69-77-155-155.static.skybest.com [69.77.155.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by oj.bangj.com (Postfix) with ESMTPSA id 203521020B; Sat, 30 May 2020 14:21:49 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=bangj.com; s=201907; t=1590862909; bh=ARBH4ywnI5n0Z5oRdIt95nq1AkOuuXafQ03p/2xA44A=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=gQnMug1OBLA7Hhgh1/4q/h2jDtaHnFQ+lp1D9iAKKeThXExYnzRHDQp9fh+h1Z+BS b25YBm3KMh1Gb3c2XSNtW5V6O7M6+x3pLn4Ng+WHOZNH3ny3fI3vpsB/XNML/Lqmwg R1i0C9Au+h+mHkIwSOFw/8OtccS5FSlATx8t/IXdtCFH5uz5tXjlYwS+KpDvJGNinP k/NjTHryZqMAsSmIBdcxTrSzQicvNdvJxny6DYPM8nJQWLq7top7bp46DaZTkCQTG7 AwWpmNAK1GWB9kxx9lH9As+nMK5HkEDU9BYtmspDQJOi/0AoNDAfsodj9sXmLJJ38i gOPADFWdroe0Q== Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) From: Tom Pusateri In-Reply-To: Date: Sat, 30 May 2020 14:21:48 -0400 Cc: rfc-markdown@ietf.org, XML2RFC Interest Group , XML Developer List Content-Transfer-Encoding: quoted-printable Message-Id: <669B51B2-54F0-4C56-8620-16B6203F62C5@bangj.com> References: <93E5295E-CE96-4121-B3F5-C04540D542FD@tzi.org> <1a5cfced-2718-0a4a-41ef-b366543ec5a2@gmail.com> <3E78C586-228A-457E-BADD-D66117FFD1C0@tzi.org> To: Carsten Bormann X-Mailer: Apple Mail (2.3608.80.23.2.2) Archived-At: Subject: Re: [xml2rfc] [xml2rfc-dev] 1.3.7: supporting ditaa, mscgen in -3 mode X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 May 2020 18:21:57 -0000 > On May 30, 2020, at 12:23 PM, Carsten Bormann wrote: >=20 > If there is any other tool like that that you=E2=80=99d like to see = supported, and it produces SVG that can be made palatable to xml2rfc = without superhuman effort, please tell me. I use Boxy SVG (https://boxy-svg.com) and need to make some drawings for = a draft so I=E2=80=99ll try it when I get a chance. Tom From nobody Sat May 30 17:15:38 2020 Return-Path: X-Original-To: xml2rfc@ietfa.amsl.com Delivered-To: xml2rfc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E48B03A0DF5; Sat, 30 May 2020 17:15:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.897 X-Spam-Level: X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 dHtxZhR7ygAv; Sat, 30 May 2020 17:15:25 -0700 (PDT) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 528933A064C; Sat, 30 May 2020 17:15:25 -0700 (PDT) Received: from [192.168.217.116] (p5089ae91.dip0.t-ipconnect.de [80.137.174.145]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 49ZJjM3v07zywP; Sun, 31 May 2020 02:15:19 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) From: Carsten Bormann In-Reply-To: <669B51B2-54F0-4C56-8620-16B6203F62C5@bangj.com> Date: Sun, 31 May 2020 02:15:18 +0200 Cc: rfc-markdown@ietf.org, XML2RFC Interest Group , XML Developer List X-Mao-Original-Outgoing-Id: 612576918.7554719-ca9b76b7875c8b6cd3fa10357be89cb0 Content-Transfer-Encoding: quoted-printable Message-Id: <1823D3E2-0AE0-442C-8F78-B615302FFB65@tzi.org> References: <93E5295E-CE96-4121-B3F5-C04540D542FD@tzi.org> <1a5cfced-2718-0a4a-41ef-b366543ec5a2@gmail.com> <3E78C586-228A-457E-BADD-D66117FFD1C0@tzi.org> <669B51B2-54F0-4C56-8620-16B6203F62C5@bangj.com> To: Tom Pusateri X-Mailer: Apple Mail (2.3608.80.23.2.2) Archived-At: Subject: Re: [xml2rfc] [xml2rfc-dev] 1.3.7: supporting ditaa, mscgen in -3 mode X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 May 2020 00:15:29 -0000 On 2020-05-30, at 20:21, Tom Pusateri wrote: >=20 >=20 >=20 >> On May 30, 2020, at 12:23 PM, Carsten Bormann wrote: >>=20 >> If there is any other tool like that that you=E2=80=99d like to see = supported, and it produces SVG that can be made palatable to xml2rfc = without superhuman effort, please tell me. >=20 > I use Boxy SVG (https://boxy-svg.com) and need to make some drawings = for a draft so I=E2=80=99ll try it when I get a chance. Hi Tom, I=E2=80=99m using that, too, occasionally (outside of RFCs). Does that come with a command line tool for transforming a =E2=80=9Csource= =E2=80=9D (e.g., ASCII art)? This is the use case that I was addressing first, as the source then = stands in fine as a plaintext replacement for the graphics. I could clearly add ~~~ svg {::include boxy-output.svg} ~~~ as a shortcut for all the things that need to be done to include SVG, = but where would the plaintext stand-in come from? (And what might be good markdown for the =E2=80=9Cartset=E2=80=9D = approach used by beta v3?) Gr=C3=BC=C3=9Fe, Carsten From nobody Sat May 30 23:01:02 2020 Return-Path: X-Original-To: xml2rfc@ietfa.amsl.com Delivered-To: xml2rfc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5B113A125D for ; Sat, 30 May 2020 23:00:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.897 X-Spam-Level: X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=miek-nl.20150623.gappssmtp.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 sGhUV3fTh5Qf for ; Sat, 30 May 2020 23:00:49 -0700 (PDT) Received: from mail-ed1-x536.google.com (mail-ed1-x536.google.com [IPv6:2a00:1450:4864:20::536]) (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 3698D3A1264 for ; Sat, 30 May 2020 23:00:44 -0700 (PDT) Received: by mail-ed1-x536.google.com with SMTP id m21so4784226eds.13 for ; Sat, 30 May 2020 23:00:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=miek-nl.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to; bh=vBfOXFxiirJkx0x3WOxlmGBwZy5jxEoqf7LV0XSLGYY=; b=v/0MaStqnF+1loT/JlMz5OkoqO0vxWoQqs0B90rydcJTw+6P2vmjrGEaGhR4VsQUpW cVpab7LyAsncSbvwadtEY5Pd7pdKYjiiX8R4Nee4ukcbT8JiLnVQNyXQEWYuIFaqacl3 MaedvPpgqBqut3Lsvhm8ZRZoVceplkZXCJZiTvKFCXjiRDlZh+qpeYoqgo+PwfVdDahR xkzB9dSRUqyw9mffEgQepLVx6JgEyb+rNk22Wu5JbrzccZSdxe4dugT3pI15UKtKwzjb SZr/P+HffLjZRU6bTO1Cli0JHKHh9VtVSY4RzIzBkZq/9qZNJfhrrSsHX3tOuegvCt69 Edtg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to; bh=vBfOXFxiirJkx0x3WOxlmGBwZy5jxEoqf7LV0XSLGYY=; b=YQJQnU2DXydWg5hrUPnstekNjlX1nm5QNwtMQ0N/RECw9SO0iIh5s/IlvkICvcxJDl 6cuWdbQs/VYgDkiOIcEcjZas6F4ofNvBLMKNyL9pICa2eNcdkbX6COTG5qyP39qbw0HG wHBWAnAC4VUgYsnHXIh5zqLEQQ+RAlBBxQyaWyPzXz+PABytCEzeXGgkz3kxdA5UIiE8 Ef7c+BsbwjUdX1Dvpz+EOViPgeD1f36y4xdYVRIP/aWUZp2lesNbb0wrbUPPe7m1zlNJ NEwZ0T/qio+8bP2Xuv9gJXCsXrtmjYmFYIbTgjMLc3r5214XTi8YkUZ8sDRbKQ0l5MVU YCmA== X-Gm-Message-State: AOAM533JuTgrdszkDABqWC1w2pDYx0n1xwfvJJWH64VESCNkFxi/dMBM 34OdeYrr60VMRS2qDv25aQlX2Q== X-Google-Smtp-Source: ABdhPJxc6XvHgpdN8urWIyq5NCLaY9ldQviCEiaduiW9gP7tLbQSWJ6wyUOIcTU1Pf6EgPNFp6oH2w== X-Received: by 2002:aa7:d999:: with SMTP id u25mr16081926eds.339.1590904843356; Sat, 30 May 2020 23:00:43 -0700 (PDT) Received: from miek.nl (dhcp-077-251-206-012.chello.nl. [77.251.206.12]) by smtp.gmail.com with ESMTPSA id y13sm11503857ejm.107.2020.05.30.23.00.41 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 30 May 2020 23:00:42 -0700 (PDT) Date: Sun, 31 May 2020 08:00:40 +0200 From: Miek Gieben To: Carsten Bormann Cc: rfc-markdown@ietf.org, xml2rfc@ietf.org, xml2rfc-dev@ietf.org Message-ID: <20200531060040.GA136848@miek.nl> Mail-Followup-To: Carsten Bormann , rfc-markdown@ietf.org, xml2rfc@ietf.org, xml2rfc-dev@ietf.org References: <93E5295E-CE96-4121-B3F5-C04540D542FD@tzi.org> <1a5cfced-2718-0a4a-41ef-b366543ec5a2@gmail.com> <3E78C586-228A-457E-BADD-D66117FFD1C0@tzi.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: Archived-At: Subject: Re: [xml2rfc] [Rfc-markdown] 1.3.7: supporting ditaa, mscgen in -3 mode X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 May 2020 06:00:52 -0000 [ Quoting in "[Rfc-markdown] 1.3.7: supporting di..." ] >So, for instance, you can now write > >~~~ mscgen >msc { > a,b,c; > >} >~~~ I've had a similar idea and implemented it as a separate binary that manipulates the markdown: https://mmark.miek.nl/post/markdown-filter/ This allows you to create pipelines, example one that uses a python program called 'protocol': https://github.com/mmarkdown/filter/tree/master/plugins/protocol ``` protocol Source:16,TTL:8,Reserved:40 ``` Figure: This is a protocol. Will be transformed with `filter -p protocol < protocol.md | mmark -markdown`, to: We describe the following protocol: ``` 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Source | TTL | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ``` Figure: This is a protocol. /Miek -- Miek Gieben From nobody Sun May 31 12:56:46 2020 Return-Path: X-Original-To: xml2rfc@ietfa.amsl.com Delivered-To: xml2rfc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9149D3A0A1C; Sun, 31 May 2020 12:56:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.1 X-Spam-Level: X-Spam-Status: No, score=-2.1 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, 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=bangj.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 mNwUhTqloMZ6; Sun, 31 May 2020 12:56:34 -0700 (PDT) Received: from oj.bangj.com (69-77-154-174.static.skybest.com [69.77.154.174]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 70D4F3A0A1A; Sun, 31 May 2020 12:56:34 -0700 (PDT) Received: from [172.16.25.103] (69-77-155-155.static.skybest.com [69.77.155.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by oj.bangj.com (Postfix) with ESMTPSA id CA091104F5; Sun, 31 May 2020 15:56:32 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=bangj.com; s=201907; t=1590954992; bh=9B/fnCObs9w9kz69xEmID4lw2qCOPVxdxXraju0VJlg=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=JcSRqFTfrM7ihR4ls/gHZ7A4R+g/oPgvgvp1249JSBy5YPZmgsr8ywdvSNJCvjHAG nJeiojRvMMzK2/c9018jmabNX8ZiTDW2ciNxQrr1Rz/fQuFsOa9hpR0bjXkFdENfK3 xL/yFDVtQN9mmHfdkaZ2PSG82MN6FJTh+lwSnbW+jCTppH0ldNVRaYeOY2yguxRaEz S26VS5VLYdt/5iZ+alPGxQOpFmytPFmhp7g18sL4rb6KpsT1xiR2i1cXtRpLs/7yVp Bm/FkuiCeZHUgBSKqN6EQJ2CfI2/WyJef/RSe8/AqgXsymv2yadqP5hqU/NMFR5UFT l1F+d7y5KS7uw== Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) From: Tom Pusateri In-Reply-To: <1823D3E2-0AE0-442C-8F78-B615302FFB65@tzi.org> Date: Sun, 31 May 2020 15:56:31 -0400 Cc: rfc-markdown@ietf.org, XML2RFC Interest Group , XML Developer List Content-Transfer-Encoding: quoted-printable Message-Id: <81B26A82-79C1-458F-B7F4-5FB524183F0F@bangj.com> References: <93E5295E-CE96-4121-B3F5-C04540D542FD@tzi.org> <1a5cfced-2718-0a4a-41ef-b366543ec5a2@gmail.com> <3E78C586-228A-457E-BADD-D66117FFD1C0@tzi.org> <669B51B2-54F0-4C56-8620-16B6203F62C5@bangj.com> <1823D3E2-0AE0-442C-8F78-B615302FFB65@tzi.org> To: Carsten Bormann X-Mailer: Apple Mail (2.3608.80.23.2.2) Archived-At: Subject: Re: [xml2rfc] [xml2rfc-dev] 1.3.7: supporting ditaa, mscgen in -3 mode X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 May 2020 19:56:38 -0000 > On May 30, 2020, at 8:15 PM, Carsten Bormann wrote: >=20 > On 2020-05-30, at 20:21, Tom Pusateri wrote: >>=20 >>=20 >>=20 >>> On May 30, 2020, at 12:23 PM, Carsten Bormann wrote: >>>=20 >>> If there is any other tool like that that you=E2=80=99d like to see = supported, and it produces SVG that can be made palatable to xml2rfc = without superhuman effort, please tell me. >>=20 >> I use Boxy SVG (https://boxy-svg.com) and need to make some drawings = for a draft so I=E2=80=99ll try it when I get a chance. >=20 > Hi Tom, >=20 > I=E2=80=99m using that, too, occasionally (outside of RFCs). > Does that come with a command line tool for transforming a = =E2=80=9Csource=E2=80=9D (e.g., ASCII art)? > This is the use case that I was addressing first, as the source then = stands in fine as a plaintext replacement for the graphics. >=20 > I could clearly add >=20 > ~~~ svg > {::include boxy-output.svg} > ~~~ >=20 > as a shortcut for all the things that need to be done to include SVG, = but where would the plaintext stand-in come from? >=20 > (And what might be good markdown for the =E2=80=9Cartset=E2=80=9D = approach used by beta v3?) >=20 > Gr=C3=BC=C3=9Fe, Carsten >=20 oh, I see. My case was simpler because I was taking an existing ASCII = art and redrawing it in SVG. I don=E2=80=99t have a way to generate both from scratch and Boxy SVG = doesn=E2=80=99t have a command line option. Tom