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

Kent Watsen <> Mon, 04 March 2019 22:39 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 2D9941311D8 for <>; Mon, 4 Mar 2019 14:39:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id NdxDEP5jOYiG for <>; Mon, 4 Mar 2019 14:39:34 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id ECBBA1311D1 for <>; Mon, 4 Mar 2019 14:39:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=ug7nbtf4gccmlpwj322ax3p6ow6yfsug;; t=1551739172; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References:Feedback-ID; bh=zSKveyhs4QcrjkzsgF0LZNOjmgXVqfS1i4cDr8W1pYM=; b=Hsm5nLHqm0Auup0V1U+sXf8SEwGdbEWvrwxUQo47ux5s7FtCdCVsNHJ0Hl93m5IZ YqyRqKakJAcdikjk+4xfQg1UQc9wXqV4th0wZn4uukygNi/XDUkyOs+rZtINqecwWfu Xl7s0xeQ5frshuSdes4AG+frGiUG6KdK0BTG41jM=
From: Kent Watsen <>
Message-ID: <>
Content-Type: multipart/alternative; boundary="Apple-Mail=_ACC5CA42-5143-41B5-9F62-6C10E30B4B6F"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Mon, 04 Mar 2019 22:39:32 +0000
In-Reply-To: <>
To: Martin Bjorklund <>
References: <> <> <> <>
X-Mailer: Apple Mail (2.3445.102.3)
X-SES-Outgoing: 2019.03.04-
Archived-At: <>
Subject: Re: [netmod] artwork folding: dual support modes?
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 04 Mar 2019 22:39:36 -0000

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

A human wouldn't, but an automated folding solution sure could.

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

Okay, now I understand your position, but I don't agree with it and,
as mentioned before, how to support indents was thoroughly debated
before.   I can't recall if you were sailing then, but I'm guessing you
were which is why you're raising this now.

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

Not in the XML.   If rfcstrip/xym wish to extract from plain-text, then
they should detect the artwork-level indent/outdent and apply that
adjustment to the entire content prior to running the unfolding logic.

Kent // contributor