IETF Logo Mail Archive

Re: [Rfc-markdown] Kramdown bug?

"Andrew G. Malis" <agmalis@gmail.com> Thu, 13 June 2019 20:04 UTC

Return-Path: <agmalis@gmail.com>
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 EE2241206FD; Thu, 13 Jun 2019 13:04:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 FyhhoDuOZRzv; Thu, 13 Jun 2019 13:04:16 -0700 (PDT)
Received: from mail-qt1-x833.google.com (mail-qt1-x833.google.com [IPv6:2607:f8b0:4864:20::833]) (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 CB1D81206CA; Thu, 13 Jun 2019 13:04:15 -0700 (PDT)
Received: by mail-qt1-x833.google.com with SMTP id p15so4688041qtl.3; Thu, 13 Jun 2019 13:04:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=KMgVFrhlZS8GEzzIJNh7EBCTRbBsh4zV8pTEDcoWwPY=; b=LkI6n7mjVNwftC4lFu5cd2WjJat5a1z6hfI2GO1SwpW1iYMDHgSZb0vv7HOa3pELtt TMoEsNuXw9Gd0e6tDF5gLjgG+qWIUZcv/DbCR2zS1z/ptPGHHwOuNzasdgKIoH9h2UTx Ah8mHTGoVQ/NMhSWaAyMkSMyVZ3xZp+nxN6ttr2TkbtOUni7aIv7uV2VD1EdSh7K3rkN 6nGIiyztmYDYvE2kGauAw1Qa7OhgbQa51voDbswG4H4xf9DYyWh9H4l7G4AcbK6/aTwZ UlRIeSeFjd+dmQZH2QgOrYFtk3PTCqEnW3F6YfA5D4X/NUx52Cs4mZ9Mtc7vrPIYM2Bg gZ7w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=KMgVFrhlZS8GEzzIJNh7EBCTRbBsh4zV8pTEDcoWwPY=; b=si0pz3NDLHu/53PRgjqIK5J4BhhNiJDICIgwF1l+7RBkdByrenD1Re5TMvTgA5cn3Q 7YJVEbqhrYv/z9G6Gnpjdff9cAlc04qVgpYl+MeGDZRgQO2eXhNjEKShlFTORUXhAw/h GvmcqXJCcfou439CNa01I1DEm6Q9bsKJh0cE3X09uCxi+04dv3snrxNNAFiEuKZNxEnv BBVsPg47RjYoXhqsd2z0pEfZWvV8UxvKB0H0fcDB+3FS0YrOQdngLy1FMhFKd9N9XN2+ UDpjCyHuCoB2RUwVYn3nPdCKgN1GpCMgchxp9wK1FRte59eFB14fipXCifodKovnax01 K2WA==
X-Gm-Message-State: APjAAAW2peKqXg8rZ9wNnRllpU4jM+4BOpCAeR0bE1ZY1H3L+OLbJTuM hFv1+cZVxtv7s0cM7Hg8NpTqEe3v3b0SSro5ZkkbFe4Y
X-Google-Smtp-Source: APXvYqyf5x+jIXrF0jZaftzGEmjf7Z/tSlCl1xjjt73m56UHDjBv76/SX3jcVn5Ts7PX70J5sQik04XETsQ0CssR1YA=
X-Received: by 2002:ac8:2194:: with SMTP id 20mr31435301qty.203.1560456254930; Thu, 13 Jun 2019 13:04:14 -0700 (PDT)
MIME-Version: 1.0
References: <CAA=duU31_4ZjG5UefpEMyEVaOyNqcXVAJU1Q0cjrk_04-GEVcw@mail.gmail.com> <EA7DD415-99A3-4AFE-A45E-0F0A9748EB8B@tzi.org>
In-Reply-To: <EA7DD415-99A3-4AFE-A45E-0F0A9748EB8B@tzi.org>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Thu, 13 Jun 2019 16:04:03 -0400
Message-ID: <CAA=duU3HB0iwj6m4RHQeWG5eXjawfPjX3a7a-GJAVC4j_4NbLw@mail.gmail.com>
To: Carsten Bormann <cabo@tzi.org>
Cc: RFC Markdown <rfc-markdown@ietf.org>, tools-discuss <tools-discuss@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c343c4058b3a086d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/vkRrT4TOgu1ucL0wSGicAIALEOM>
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 20:04:18 -0000

Carsten,

Thanks, that fixed it!

   [OPENFLOW]
              Open Networking Foundation, "OpenFlow Switch
              Specification, Version 1.5.1 (Protocol version 0x06)",
              ONF TS-025, March 2015, <https://www.opennetworking.org/
              wp-content/uploads/2014/10/openflow-switch-v1.5.1.pdf>.

Cheers,
Andy

On Thu, Jun 13, 2019 at 3:56 PM Carsten Bormann <cabo@tzi.org> wrote:

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

v2.23.0 | Report a Bug | By Email