Re: [netmod] artwork folding: dual support modes?

Martin Bjorklund <mbj@tail-f.com> Mon, 04 March 2019 21:52 UTC

Return-Path: <mbj@tail-f.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1866131084 for <netmod@ietfa.amsl.com>; Mon, 4 Mar 2019 13:52:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=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 MhW8aFzyMAVg for <netmod@ietfa.amsl.com>; Mon, 4 Mar 2019 13:52:25 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 9877813108F for <netmod@ietf.org>; Mon, 4 Mar 2019 13:52:25 -0800 (PST)
Received: from localhost (h-4-215.A165.priv.bahnhof.se [158.174.4.215]) by mail.tail-f.com (Postfix) with ESMTPSA id 9F49B1AE0443; Mon, 4 Mar 2019 22:52:23 +0100 (CET)
Date: Mon, 04 Mar 2019 22:52:23 +0100 (CET)
Message-Id: <20190304.225223.810570484724895529.mbj@tail-f.com>
To: kent+ietf@watsen.net
Cc: rwilton@cisco.com, netmod@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <010001694a9bd6f5-87034dff-c252-4e16-8028-f38e9184d2da-000000@email.amazonses.com>
References: <0100016949d802d6-ccf713c5-df75-4f24-b479-4bc94b4138ec-000000@email.amazonses.com> <20190304.193540.1020759172873811211.mbj@tail-f.com> <010001694a9bd6f5-87034dff-c252-4e16-8028-f38e9184d2da-000000@email.amazonses.com>
X-Mailer: Mew version 6.7 on Emacs 25.2 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/8wxzm5rcDyX4Ki_Sskjfvsedq-0>
Subject: Re: [netmod] artwork folding: dual support modes?
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Mar 2019 21:52:28 -0000

Kent Watsen <kent+ietf@watsen.net> wrote:
> 
> 
> >> Now that IETF has officially moved to XML as the sole format
> > 
> > I'm not sure what you mean, can you provide a pointer?  AFAICT, the
> > latest published RFC is still only available as txt and pdf.
> 
> I meant that XML is the sole *input* format, per RFC 7990, but you're
> right about the XML not currently being easily accessed.   I've signed
> up for the IETF 104 CodeSprint to fix this, as well as to introduce
> folding support into the publishing process.
> 
> 
> >> No, there are cases where this fails.  We went thru this before.
> > 
> > Only if you have data with > 69 spaces in a row that needs to be
> > preserved.
> 
> More generally, anytime the fold occurs where space characters
> follow.  

No, b/c you wouldn't fold there.

> But why are you arguing for this? - the double-backslash approach
> works great for when indents are desired.   

Let's agree that it works :)

I'm arguing that *if* we are to define two solutions, we should use
this one.  (And as I explained, my preference is this one over the
double-backslash solution, but I accept the WG consensus for the
double-backslash solution)

> My interest in this thread was/is only to cover the common case 
> when there are no indents, and the continuation line always begins
> on column 1, in which case the 2nd backslash is unneeded and 
> somewhat counterintuitive.

But your continuation line will not start at column 1 (since artwork
is indented with 3 spaces by default).  So this solution doesn't
really work.



/martin