Re: [Rfc-markdown] Kramdown bug?
Carsten Bormann <cabo@tzi.org> Thu, 13 June 2019 19:56 UTC
Return-Path: <cabo@tzi.org>
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 374301206F2; Thu, 13 Jun 2019 12:56:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=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 62IUOzf2asn1; Thu, 13 Jun 2019 12:56:49 -0700 (PDT)
Received: from smtp.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 28BB71206F0; Thu, 13 Jun 2019 12:56:49 -0700 (PDT)
Received: from [192.168.217.113] (p54A6CA4C.dip0.t-ipconnect.de [84.166.202.76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.uni-bremen.de (Postfix) with ESMTPSA id 45PvdV5lKszylv; Thu, 13 Jun 2019 21:56:46 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAA=duU31_4ZjG5UefpEMyEVaOyNqcXVAJU1Q0cjrk_04-GEVcw@mail.gmail.com>
Date: Thu, 13 Jun 2019 21:56:45 +0200
Cc: RFC Markdown <rfc-markdown@ietf.org>, tools-discuss <tools-discuss@ietf.org>
X-Mao-Original-Outgoing-Id: 582148602.2133501-e8db31a574d7677fdfa23d763cd2fc59
Content-Transfer-Encoding: quoted-printable
Message-Id: <EA7DD415-99A3-4AFE-A45E-0F0A9748EB8B@tzi.org>
References: <CAA=duU31_4ZjG5UefpEMyEVaOyNqcXVAJU1Q0cjrk_04-GEVcw@mail.gmail.com>
To: "Andrew G. Malis" <agmalis@gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/pX19KchoY2PouAge6IsKUv42lkY>
Subject: Re: [Rfc-markdown] Kramdown bug?
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.29
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, 13 Jun 2019 19:56:51 -0000
> seriesinfo:
> ONF TS-025
Probably best fix:
seriesinfo:
ONF: TS-025
Each seriesinfo entry always is a key-value pair (name=, value=), both of which are then shown, simply separated by a space.
Kramdown-rfc is a bit too permissive here, allowing an empty value. They key you gave and the empty value are separated by a space, causing a trailing space.
I don’t know a way to use seriesinfo to place a single string that does not have a space (but then I never actually needed that).
Grüße, Carsten
- [Rfc-markdown] Kramdown bug? Andrew G. Malis
- Re: [Rfc-markdown] Kramdown bug? Andrew G. Malis
- Re: [Rfc-markdown] Kramdown bug? Carsten Bormann