Re: [xml2rfc] Imaginary vspace?

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 21 June 2023 22:40 UTC

Return-Path: <brian.e.carpenter@gmail.com>
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 F21AAC14CEFD; Wed, 21 Jun 2023 15:40:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.097
X-Spam-Level:
X-Spam-Status: No, score=-7.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, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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=gmail.com
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 BB6jJto5ezK2; Wed, 21 Jun 2023 15:40:38 -0700 (PDT)
Received: from mail-pg1-x535.google.com (mail-pg1-x535.google.com [IPv6:2607:f8b0:4864:20::535]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 244DEC14F693; Wed, 21 Jun 2023 15:40:38 -0700 (PDT)
Received: by mail-pg1-x535.google.com with SMTP id 41be03b00d2f7-54f75f85a17so3510168a12.0; Wed, 21 Jun 2023 15:40:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1687387237; x=1689979237; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=bHBsI+0uGR0qxWmWEgLMzA+afUwFqLZXnvNFvWl7UUU=; b=Okom5GO6oYWlFF23+Y7+2r2ahmn/vfF9DXi+kHaBKnRxZsWPl3+TqOwzfzSdk2FpRB Aesci1YZHan4zFl+3xazLs5tugx51k7gqwRXcuZVnV3d7mqAJVM4UhOVv/yTh67i1ohq y1PEE8+hrEUbkxRVUZZmWgdu7BhrX/akZvcJarTijnX5BPRSX9H111/cW/14KMGGoYH3 tMc6ETaR7d7bKm3e2Ej2W2nwCPJgi9Ek0uOpYA4olgb44SCtOVzFceZrFt+G3t9IjWag UDs5mkNjlDx7G5sFPtLRVFjbIUTyyUvjXRMMMLA+SRFrGrdTVo2ZShUAIlMpspO0vqVU XBMg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687387237; x=1689979237; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=bHBsI+0uGR0qxWmWEgLMzA+afUwFqLZXnvNFvWl7UUU=; b=AYJ2h44mspMfq4mnDzs8viootu3ZcQWqXvoRvvvGzZzOLdpc528PVnfz77rsenZF64 GI4xhXQgA2BmXar/CDf3VM06xUAJDVR4XVd6W1n5uqfuxmlnHOly8mxK04IJ4B79E7IE SWf62O39WP36zGoxuNQejxUsV7xqWUZYDdK1rEjquZ2/LUpscZAkaKf4K7Tno9UjY0Vv sWGSHRfDHGTCKQxqgR1JOP+jjXPdBjRzimDtl/I0kpAXVtbuUneKqVeycJ5deahhBPUs 8blDKp9peTdqa7/IhUXQyW8GZ4xLNEUD3gKZ5BFmKLpBQHCqeKzy2IM5ksXnlNIymA4R LAQQ==
X-Gm-Message-State: AC+VfDxI79pf5KDUegeHs6jhnuMpBE9IRwQLufX+oCFN8UD0rcH/4kV1 5kpp53OfTT1fO+uF4vC76eN0QCdMb3iO5g==
X-Google-Smtp-Source: ACHHUZ58f7W8Jbp31YP3d5DAv1FC47uRcNKv7xp8U/pbd4yw+uEIegsr+7br+YQ9RALj5863REfW7g==
X-Received: by 2002:a05:6a20:7d8b:b0:122:6de4:125d with SMTP id v11-20020a056a207d8b00b001226de4125dmr7116104pzj.19.1687387237021; Wed, 21 Jun 2023 15:40:37 -0700 (PDT)
Received: from ?IPV6:2406:e003:1184:f001:9991:d1ad:8c20:42bd? ([2406:e003:1184:f001:9991:d1ad:8c20:42bd]) by smtp.gmail.com with ESMTPSA id t1-20020a170902e84100b001a6a6169d45sm3978787plg.168.2023.06.21.15.40.34 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 21 Jun 2023 15:40:36 -0700 (PDT)
Message-ID: <5ad61bf8-c7d0-c657-2774-720802f466a9@gmail.com>
Date: Thu, 22 Jun 2023 10:40:31 +1200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0
Content-Language: en-US
To: Carsten Bormann <cabo@tzi.org>
Cc: Kesara Rathnayake <kesara@staff.ietf.org>, xml2rfc <xml2rfc@ietf.org>, 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: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <7FF96E34-7B7C-4F13-B644-E5AFDA4C1E7E@tzi.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/2GjaiRHLAzj1Bvh9HAHmRUJOC8k>
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 22:40:42 -0000

> What did you want to express with the horizontal rule?

Nothing at all, I suspect. I was just trying to fix up an early version of a draft by a newcomer to kramdown, and it included that line.

Regards
    Brian

On 22-Jun-23 09: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).
> 
> 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.
>