Re: [xml2rfc] Imaginary vspace?

Carsten Bormann <cabo@tzi.org> Wed, 21 June 2023 21:29 UTC

Return-Path: <cabo@tzi.org>
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 4B62CC14CE4B; Wed, 21 Jun 2023 14:29:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.896
X-Spam-Level:
X-Spam-Status: No, score=-6.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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
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 XaNWtL-fb_mC; Wed, 21 Jun 2023 14:29:19 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [134.102.50.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98057C14F75F; Wed, 21 Jun 2023 14:29:17 -0700 (PDT)
Received: from smtpclient.apple (p548dc15c.dip0.t-ipconnect.de [84.141.193.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4Qmc8B141kzDCd2; Wed, 21 Jun 2023 23:29:14 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.600.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <a2024a19-acb8-b93e-a94b-76af6d86cbae@gmail.com>
Date: Wed, 21 Jun 2023 23:29:03 +0200
Cc: Kesara Rathnayake <kesara@staff.ietf.org>, xml2rfc <xml2rfc@ietf.org>, rfc-markdown@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <7FF96E34-7B7C-4F13-B644-E5AFDA4C1E7E@tzi.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>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3731.600.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/Ax3_kVhT0D1yXQg5BtPShHk0T6I>
Subject: Re: [xml2rfc] Imaginary vspace?
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: XML2RFC discussion list <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Jun 2023 21:29:23 -0000

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).

What did you want to express with the horizontal rule?

Grüße, Carsten

[1]: https://kramdown.gettalong.org/quickref.html#horizontal-rules

(*) at least not directly for creating page breaks; there is a keepWithNext and a keepWithPrevious attribute, weirdly only on <t, which can be used to avoid a page break in specific places.
I have not spent time to check whether there is another trick in xml2rfcv3 that could be employed to create a page break.