IETF Logo Mail Archive

Re: [Rfc-markdown] [xml2rfc] [xml2rfc-dev] <br> is back, was: New xml2rfc release: v2.32.0

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 04 October 2019 19:38 UTC

Return-Path: <brian.e.carpenter@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 2116D1200D6; Fri, 4 Oct 2019 12:38:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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 d9Ou178QX86V; Fri, 4 Oct 2019 12:38:07 -0700 (PDT)
Received: from mail-pf1-x42e.google.com (mail-pf1-x42e.google.com [IPv6:2607:f8b0:4864:20::42e]) (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 A1C041200B4; Fri, 4 Oct 2019 12:38:07 -0700 (PDT)
Received: by mail-pf1-x42e.google.com with SMTP id v4so4507126pff.6; Fri, 04 Oct 2019 12:38:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=k4zJ2jLucv+OX1aAOg9n0F5Kyv4TRGcLsjXiM+wG7Uc=; b=smcoqnKqb4/kev44dvgyz3D5AZ78P5lMEztlWnltRVuNAZmy7/zNFBl0GbgawqAOj2 GZ+b4XS3k6vL2V7jCU1rufwdYojpZnnECmxJkJMXWr7uWscnwA5+U3KNnQHARZJjffrr nzhg+BkaRzHJ+/5uIJlGhGb+P3iKCh7mvmHzQ6eKCnc/VlmrtyTt6rvAU/DQ2LC6brnJ pmhBjFFMEi5P22mpHczuVBNqLIBbwajUOzEaDx9o7ff103MkQuWMzvm6f6C1k9ZpnxY9 D+8WxbviKP7gTjt5vAmkgUqhom8Fp+aumIt4VyYeQJxlbiAPcFTeyzu2pDJ8JaDwO9IJ U3hA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=k4zJ2jLucv+OX1aAOg9n0F5Kyv4TRGcLsjXiM+wG7Uc=; b=t+UfuTEFM4gyfqw9aiqISmiDCtKYwVYVidwBXSftmizFBKh0Ah0Mwk1wMi4OE7R+M7 1cJ+fsvMX4Ny77y/TrQo+sCdgRUlE6Tak6Rhl54zMEyvsGW4C3pksBndiQnaGQ2l5VR9 K+c8GtsSm9SAd1nnNUDkQMQFiqgXpCjuVPvbd03S2Fs9wxItAX1pIBEs7WAbuQh+f4wY 0lcPLKkJc8jS4KNpFT5krId6zE4Mwr22vRmH9ILmJWuAfDdxF+RJlu0H57hhPXfPa21c 6MscYxBd9tvd+BF9gLJB5PlZqSJNWAig9ibyqvEohCgBXd4aJTnv5wKP25Zj0k7ZbeGZ +Ujg==
X-Gm-Message-State: APjAAAUOXm8l25BXETEh4xFPV7sysLL9G7Cg1AzMmuyku6PcdSPOa5ZR R35Fa5nakQQN9+u2oUJCwDlroDMm
X-Google-Smtp-Source: APXvYqwvxuP83eUVQgZumCwY6MlauWTrE1Eu61/9BTWl6ynreEUfJaX5cWBPIAip6cP//mZRZAp7pw==
X-Received: by 2002:a63:2d83:: with SMTP id t125mr9745289pgt.282.1570217886906; Fri, 04 Oct 2019 12:38:06 -0700 (PDT)
Received: from [192.168.178.30] (233.148.69.111.dynamic.snap.net.nz. [111.69.148.233]) by smtp.gmail.com with ESMTPSA id s202sm9521306pfs.24.2019.10.04.12.38.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 04 Oct 2019 12:38:06 -0700 (PDT)
To: Henrik Levkowetz <henrik@levkowetz.com>, "HANSEN, TONY L" <tony@att.com>, "xml2rfc-dev@ietf.org" <xml2rfc-dev@ietf.org>, "xml2rfc@ietf.org" <xml2rfc@ietf.org>
Cc: "rfc-markdown@ietf.org" <rfc-markdown@ietf.org>
References: <E1iGMu9-00055y-Ui@durif.tools.ietf.org> <8304e61d-c550-91ea-9e23-eef2cd31240b@gmx.de> <A3513970-EEB0-4DBD-9E6F-A87EBFAF886D@att.com> <de4feaff-8f71-cd38-545c-2d848749251b@levkowetz.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <e348a399-9e2e-a5be-9f42-67b2ed542845@gmail.com>
Date: Sat, 05 Oct 2019 08:38:03 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <de4feaff-8f71-cd38-545c-2d848749251b@levkowetz.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/9iy3aCoLF8eEKp_e1qbCu8v7q6g>
Subject: Re: [Rfc-markdown] [xml2rfc] [xml2rfc-dev] <br> is back, was: New xml2rfc release: v2.32.0
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: Fri, 04 Oct 2019 19:38:09 -0000

On 05-Oct-19 04:34, Henrik Levkowetz wrote:
...
> I'm strongly for having an explicit <br/> element.

I concur. My conclusion from 30+ years of using various markup languages is
that explicit line breaks are needed, even if they offend some ideal vision
of markup theory. Sometimes there is simply no alternative.

   Brian

v2.23.0 | Report a Bug | By Email