My interpretation:
Option 2 is to disallow tabs in the output, but leave it to the
implementation to decide how to handle tabs in the input document, so a
script would be allowed to do a, b, or c.
Just supporting "option 2(a)" is the same as "option 1":
1) RFC disallows TABS in both the source-input and folded-output.
***This is what we currently have***
Perhaps you mean that you prefer option 1?
Thanks,
Rob
On 26/09/2018 16:22, Juergen Schoenwaelder wrote:
On Wed, Sep 26, 2018 at 02:09:52PM +0000, Kent Watsen wrote:
I recommend that we select "option-2" (see bottom).
[...]
2) RFC disallows TABS only in the folded-output, per RFC 7991,
leaving it to the folding-logic (the script) to decide if it
wants to:
a) disallow TABS in the source input (curr script does this)
b) detect TABS exist and prompt user for TAB stop info
c) detect TABS and query environment for cur TAB stop info
(but tab-stops may differ in the shell the text editor,
or whatever was used to create the text, right?)
Given that 2) has a)-c), I do not understand what the recommendation
actually is. The recommendation is hopefully 2a) and we are done.
/js
_______________________________________________
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
