Re: [Rfc-markdown] [xml2rfc] bcp14, was: [xml2rfc-dev] New xml2rfc release: v2.25.0

Fred Baker <fredbaker.ietf@gmail.com> Mon, 26 August 2019 20:36 UTC

Return-Path: <fredbaker.ietf@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 953F1120FD8; Mon, 26 Aug 2019 13:36:54 -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 Z-vmMwUrw4vG; Mon, 26 Aug 2019 13:36:51 -0700 (PDT)
Received: from mail-ot1-x32e.google.com (mail-ot1-x32e.google.com [IPv6:2607:f8b0:4864:20::32e]) (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 8F4EB120FCF; Mon, 26 Aug 2019 13:36:51 -0700 (PDT)
Received: by mail-ot1-x32e.google.com with SMTP id z17so16464563otk.13; Mon, 26 Aug 2019 13:36:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=szcV9z3/Q92HwK5h9ZqkPfFDRW48710t4ieqQsCu7fI=; b=UttvhmZ5L5hFGpKeo4rxzgMgreRWn2NDJKtLLfz6yb9kibuoN/hj6kX1ysrkqCvItR 575ico1GAdyQR3sQpodWAFvKo37wA8fDlNrdZj6Th9GepiDJRDoF6Onq70ZFrOL6uhPq QqJoaX3v1CIjaLwAXQng37GI8vcC3OUgsnUQnFrKVUjqWMVNcFc0eAu0m8VdtmQaxway CQZk7Y4AvlPiM+hM+cGZfv9F/hGpp3RvFev8M5Vf/QMjo92G1mEatDtRHz5eJnwEkAJY qR5WrywUCAVbZSK4NvEnbFjerd4LW/oGgYz+UJl6bXFa+dB+gvIdKLhb6Bk6TgMoBKhP 4JZQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=szcV9z3/Q92HwK5h9ZqkPfFDRW48710t4ieqQsCu7fI=; b=f7a5v/jsVkZ42QLjI1H0mmAHtOSUK1wK5AagQw/QD8pnZ86sZgWfa5SbiLpDsr40sy W73hvdZzdtTtxGEwQnLe0HI0gqrSke0gflyZkJ1Up8vnNkK093M/Ix8hrCccT37wCN6B eGcpOFfn1rlaSOW6HBdMBcnHu6J2qZT1+5U18TzgIhTZZfOId4S+shxM2EPFvXi0qHFe KIDpTWwr8lDyd3RaqHQpBuyhU7gPJuNcKYLpagUJ+L+9DwGn4DhDx3Z6FG5SBCwbeYYE sg292njwkupN+rsw3bpuZ7tgILxZWKpwZukAspukhFNlasF0ic2aBEEoauQA4edy/5pm iSVQ==
X-Gm-Message-State: APjAAAWDa44H03it5zLOgrCnQ3QmKts1uhtsn8HWr4bbZDIFOfroAY5V MFbSpTwLiZKOxnaCyIXBP14=
X-Google-Smtp-Source: APXvYqxOIHCi/hrZ+HrkpC9vu0YRcGlyBGlo92gmuG1myGz/0de2OeY6FStafNs04oTT+yHjLvXk4g==
X-Received: by 2002:a9d:5601:: with SMTP id e1mr6770484oti.370.1566851810979; Mon, 26 Aug 2019 13:36:50 -0700 (PDT)
Received: from ?IPv6:2600:8802:5903:df16::1053? ([2600:8802:5903:df16::1053]) by smtp.gmail.com with ESMTPSA id q85sm3964321oic.52.2019.08.26.13.36.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 26 Aug 2019 13:36:50 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3578.1\))
From: Fred Baker <fredbaker.ietf@gmail.com>
In-Reply-To: <40d507f2-ed78-e09f-ae96-c64333a91547@levkowetz.com>
Date: Mon, 26 Aug 2019 13:36:45 -0700
Cc: Julian Reschke <julian.reschke@gmx.de>, xml2rfc-dev@ietf.org, xml2rfc@ietf.org, rfc-markdown@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <C9CFF4AB-5B52-49A9-B19D-60A26E9A13BB@gmail.com>
References: <E1i2EMD-0002SA-UW@durif.tools.ietf.org> <22880345-a324-8dfd-a08c-e8ec89aeb9b5@gmx.de> <20190826144520.GA19037@miek.nl> <40d507f2-ed78-e09f-ae96-c64333a91547@levkowetz.com>
To: Henrik Levkowetz <henrik@levkowetz.com>
X-Mailer: Apple Mail (2.3578.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/dYksBc7znB45ejB-XR7pH1piMMk>
Subject: Re: [Rfc-markdown] [xml2rfc] bcp14, was: [xml2rfc-dev] New xml2rfc release: v2.25.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: Mon, 26 Aug 2019 20:36:58 -0000


> On Aug 26, 2019, at 10:14 AM, Henrik Levkowetz <henrik@levkowetz.com> wrote:
> 
> It seems to me that future tools that process our XML should be prepared
> to deal with unicode whitespace generally, not only ASCII space.

That makes sense to me. The normative language is as seen by the eye and processed by the brain, not as processed by some random computer program. One implication is that it can be broken by a line feed or any other construct that the brain renders as white space.