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

Miek Gieben <miek@miek.nl> Fri, 04 October 2019 15:43 UTC

Return-Path: <miek@miek.nl>
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 695771208F6 for <rfc-markdown@ietfa.amsl.com>; Fri, 4 Oct 2019 08:43:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=miek-nl.20150623.gappssmtp.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 HQ-rLB74pBpm for <rfc-markdown@ietfa.amsl.com>; Fri, 4 Oct 2019 08:43:30 -0700 (PDT)
Received: from mail-wr1-x42a.google.com (mail-wr1-x42a.google.com [IPv6:2a00:1450:4864:20::42a]) (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 969781208EA for <rfc-markdown@ietf.org>; Fri, 4 Oct 2019 08:43:30 -0700 (PDT)
Received: by mail-wr1-x42a.google.com with SMTP id r3so7821682wrj.6 for <rfc-markdown@ietf.org>; Fri, 04 Oct 2019 08:43:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=miek-nl.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to; bh=3fKVTbIMUjA89T6JFoZPxLgnbEEQdOjITpN/eKULVCM=; b=sePaNk7j0gSQ5ido9QruTL5hXxLkWZWKgR83ZxO6a7FiSfyHEGoZpJdg+TUjJc6AqF fLTqSWy1W9SEq6ygHmzYyqEMw83YnqdMF7B53TDqvQlAyX8ZRww6cgon8WRKznDNUb1a tVyl5blXul2goAXSoBhU0s9NoDpey+5mWSK7mc7Zb0eb8Yu1eeKJoA6a7B3PrgmM4wxR 3+/0ae9HfPIGR48NJNagDcy8+VaE3D6e04eH9/4F9y3zgsl7RdeIZ+TXCKwLj6oJbB4c CCqpnUpg9gnjVLKUhzk4zJ2mwnKEvkuAhDAr5Z6A8cBefwhjBBMYW0v2AJnggBuQ4nvd 7R2w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to; bh=3fKVTbIMUjA89T6JFoZPxLgnbEEQdOjITpN/eKULVCM=; b=lCr+gug9nXxhH5Zg0j63qKHcpB21ZWVnGJhsvkeu0wlNQeBb5YhyyzhBEib5a7XMgJ NVgCy1RMPnHRBquK+cukhimPpKnSj2on7FHVJSevVXGnG3DbhexyT1IPtcGDtNQrVdhs NgtXyLoYmHfGrH34PNJc6hI+Y82YIGKc/NYFsy6i+jw4cPNZ7Zo4eG77telriaowbbUZ 1KGgBlbyffW6Pu2bP02ib7eoFfCL3EcUT0eR/KqBqbXbRIugaP28/flzLuMGMHAatS68 TEZGe/PKdwA8vh1buKRrRPj1xVMzuo49PDnX0UiyGtaHsJWHOr/fi1G/iuEGvUKPcp7L hk3Q==
X-Gm-Message-State: APjAAAUGagDEQ5DP68teO4nOGFZSpOvvLhMQgqWLRnNbNq4x1UvITs5r Cc9Tq3X65baC5RKImNMmkM1G7w==
X-Google-Smtp-Source: APXvYqw+ohd3V0uYd9RxLEZzA5Vasy5zMQSSE52G7GRCE4PUZNA0x3YlOJcfShh2xFkIkGfjHjztlw==
X-Received: by 2002:a5d:5183:: with SMTP id k3mr11378010wrv.55.1570203808905; Fri, 04 Oct 2019 08:43:28 -0700 (PDT)
Received: from miek.nl ([91.103.19.50]) by smtp.gmail.com with ESMTPSA id 3sm4799964wmo.22.2019.10.04.08.43.27 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 04 Oct 2019 08:43:28 -0700 (PDT)
Date: Fri, 4 Oct 2019 16:43:27 +0100
From: Miek Gieben <miek@miek.nl>
To: Carsten Bormann <cabo@tzi.org>
Cc: Henrik Levkowetz <henrik@levkowetz.com>, "rfc-markdown@ietf.org" <rfc-markdown@ietf.org>, "xml2rfc-dev@ietf.org" <xml2rfc-dev@ietf.org>, "xml2rfc@ietf.org" <xml2rfc@ietf.org>
Message-ID: <20191004154327.GA19635@miek.nl>
Mail-Followup-To: Carsten Bormann <cabo@tzi.org>, Henrik Levkowetz <henrik@levkowetz.com>, "rfc-markdown@ietf.org" <rfc-markdown@ietf.org>, "xml2rfc-dev@ietf.org" <xml2rfc-dev@ietf.org>, "xml2rfc@ietf.org" <xml2rfc@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> <AFB054CA-71C4-48FA-8097-9242E7E104E4@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
In-Reply-To: <AFB054CA-71C4-48FA-8097-9242E7E104E4@tzi.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/eEXt9-VrXEu9Q1kwXutWAqoUq7k>
Subject: Re: [Rfc-markdown] [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 15:43:32 -0000

[ Quoting <cabo@tzi.org> in "Re: [xml2rfc-dev] <br> is back, was..." ]
>Something is not right with the process if we have a clear requirement and an obvious solution, but instead have to resort to using an obscure, widely shunned Unicode feature so we appear not to violate the specification.

+1