Re: [Rfc-markdown] [xml2rfc] Imaginary vspace?

Julian Reschke <julian.reschke@gmx.de> Thu, 22 June 2023 11:55 UTC

Return-Path: <julian.reschke@gmx.de>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78F11C13737E for <rfc-markdown@ietfa.amsl.com>; Thu, 22 Jun 2023 04:55:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.093
X-Spam-Level:
X-Spam-Status: No, score=-2.093 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, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmx.de
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tqujG47R-WUz for <rfc-markdown@ietfa.amsl.com>; Thu, 22 Jun 2023 04:55:35 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 21EB4C13737F for <rfc-markdown@ietf.org>; Thu, 22 Jun 2023 04:55:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.de; s=s31663417; t=1687434933; x=1688039733; i=julian.reschke@gmx.de; bh=U1GLnbgWyDdnQ+gv29sXNB7YlhQ0QghflwvvBR/6eQY=; h=X-UI-Sender-Class:Date:Subject:To:References:From:In-Reply-To; b=f3HgILOOWd7EWYb5pMhes0hMJ+kMBuX1PyqHBtytDgUZGGGHGII90zqwrCTcfWHgB4wZvV8 LJsu+A5zeQXAMb0CnKsIBvZxrG/ZeFIpOldWBBg4pbvjbbV4/Yn3UcUPcxzAtmiI62IxxKRF9 iBYgGBDjWPqD03NQT4oKqYSWA9PYFKPVnKY9ctrPzyZ9ugokHY+hMK7se/F7hjVTQPCRNvIV3 sQ+eEGlTwkE6ifrw+gnKjuUzBCt9TWB9tnIveBrl+J9MyQYxLpoFSawDE3Pj1hsay6hj25Q+T DMafeYPBgewtqlf1l3lJloKKsIDejFXWNeUUEVbT6FkvhGTHSenQ==
X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a
Received: from [192.168.178.192] ([91.61.62.227]) by mail.gmx.net (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1M1Ycr-1qFKus1Dn1-0035xU for <rfc-markdown@ietf.org>; Thu, 22 Jun 2023 13:55:33 +0200
Message-ID: <d39d7efa-3386-b562-a120-a3860e00277d@gmx.de>
Date: Thu, 22 Jun 2023 13:55:32 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.12.0
Content-Language: en-US
To: rfc-markdown@ietf.org
References: <24451a52-5848-d33f-1496-50fa0a998d0c@gmail.com> <CAD2=Z85jycbqdeo3fz1jAwedMbPPwpyi9MJ6r0bJFSjstGrwDg@mail.gmail.com> <b8fe31bc-9d1c-04b9-e729-f4c55b3ef91d@gmail.com> <CAD2=Z87s24XtaO9i2sRB=o_qWg+OWZHwS2Cy1gG6BoqPtHNd3g@mail.gmail.com> <CAD2=Z84Vt4w4bteeshj7+gu-Ua8SVyoxCbtS6_S7MmV=Cnspqg@mail.gmail.com> <a2024a19-acb8-b93e-a94b-76af6d86cbae@gmail.com> <7FF96E34-7B7C-4F13-B644-E5AFDA4C1E7E@tzi.org>
From: Julian Reschke <julian.reschke@gmx.de>
In-Reply-To: <7FF96E34-7B7C-4F13-B644-E5AFDA4C1E7E@tzi.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:TQxbg4Y/vTCOJGoeqQP42xVEHUT77g3jOYKq44mC0EYonFE7Dct cBdQlE7TwhKaBdsN+yEYOGhRl286JvNiKW8xrLrVLUWZl2kswFDsgcLEBjuC+XcFzVYOMs6 XC6lnwt6LhNFAhJiZJE6iiSTm2Cx/RP9eM2NSMpAz6G2/wNjHUleH26zVXRwj4/r76Yoz0F mO7tHnWTvu+fdNDwi2MPQ==
UI-OutboundReport: notjunk:1;M01:P0:cZ9/1MNo6y0=;2A8wM1NGWcA5Gp4Juu9+pBU/IyN lc5MkSDIe5oYWMiS9KdfvunSz9l3UdFjPpzFoADEkNfBO7cPE1j6LiHY+GGxOkrbmuAHdPiz9 OsenF7AOpy12y8AnGbPwxFtVmSzLB4IyEdW46ljfWl15WJCR0gFk/3m6s9oRSGdF2zAG7dXou tIVh7J1enzeXDF/DVu2Q50Y05vVYdO3wuCcCZhT+RILL0+Ene94A8P3f5/9cgoRH4drcr2L/F 0OJKXo4tS3qQ1c9c8o8omX6nnW2FNYuUZSkY5pp87EcNJkMqXdUmQpKgYGDbcUCY18RImPIip xvrM8Sg0ZXiM8t9c6DP/FjNKes//jRa+i3rDfa+rpQFpxS0GCHgdpt6dw+iZawHDJHt5UaUxa LRlDs8Nfs6nUmKTXsCM48bbKxFzYKRUWzoruOIQGej4uIluSbpkcoRUQrL05Utmkr3DxMNhie tDo5qfMHHoxc2g1h6mDl0iIVFaLLexBPF2dZyf5Zmy9xcE63bLPOrsniMNWdxet7K/v5oj+WP ymAUmKwpqDeOwfTiDm/JpY5F0zUZ12k8+GaEws16Bli3yv2AY+b+eXT5IWVoUYpl9UtWiCazQ 5hThERK39iveqLrG660J2rlEAsCJKBOoZoHx2iWVqyZnp6WF0YvErr3EtA5SGkMThRQNqBrI5 Ln4p2lzAxi0u5ZoFkFXaRhJv7vyWC9lXcEgd2NDltx5lPrFWuV4yeJ5TQtawI0svVOUwjqILC d5Bic4+MbJaYDEekIN5mhws/0uNQls7DtOyzw4BUP4sIDgJMDgo90Vh3ildxupmu4Vf6G51zS tffybgrr2XvpScZ+KlzXcZ9G5rJ+m3mbDLZdAGotT9tlvXwQdB/8T0MV+t5vyoyyWu3ROTGKM HwgM8GQropMrCiJnN4+/gmmGpXYue9EDwUAWiREgkQh3Aslb8+bvwcwEpuOXVBz2Jzs/Ym+Bb RrzmNA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/V0wNz6MMa6OIh33NVIl_e1QWIO4>
Subject: Re: [Rfc-markdown] [xml2rfc] Imaginary vspace?
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Jun 2023 11:55:39 -0000

On 21.06.2023 23:29, Carsten Bormann wrote:
> On 21. Jun 2023, at 22:50, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>>
>>>> It's kramdown-rfc that adds the vspace.
>>>> Use of `-----------` in line 74 is the line that adds the space.
>>>> I couldn't find any documentation on kramdown-rfc about adding vspace this way.
>
> In markdown, `———` on a line of its own, surrounded by vertical blank space, is a horizontal rule (<hr in HTML).
> (There are a few similar syntaxes to do the same [1].)
>
> There are no horizontal rules in RFCXML, so I used this syntactic element to indicate a page break, which has a similar separating function in paginated documents to what you would be trying to achieve with a horizontal rule in HTML.
>
> The way to effect a page break in RFCXMLv2 was to do a large vspace (e.g., with 999 lines).
> This is what you see here.
>
> RFCXMLv3 does not provide the author with functionality to influence page breaks (*), so the v2v3 converter we employ to generate RFCXMLv3 throws out the page break (and correctly indicates in a warning that it is simply not doing as told).
> ...

Out of curiosity: is there a good reason why it still emits a mix of v2
and v3?

Best regards, Julian