Re: Last Call: <draft-ietf-netmod-artwork-folding-07.txt> (Handling Long Lines in Inclusions in Internet-Drafts and RFCs) to Best Current Practice

[Kent Watsen <kent@xxxxxxxxxx>]

Hi Paul,

Thanks for your comments!

1) Section 6.2 recommends only using double backslash folding if single backslash folding doesn't work. But all the examples in section 9 violate this.

True, but these example illustrate the algorithm itself, and so seem okay, or is your suggestion to add text stating this?

FWIW, the `rfcfold` script in the appendix of the draft was used on all the examples in Section 9.  By default, the `rfcfold` script follows the recommendation (i.e., single before double), but also accepts a command-line option to specify the folding strategy to use.  For the examples in section 9, this command-line option  was used.

2) Regarding forced folding in section 8.2.1: step 1 (Determine where the fold will occur) could benefit from some elaboration regarding lines that require forced folding. In particular, when an input line flagged for forced folding ends in backslash, then it must indeed be folded before the last character, while in all other cases it can be folded at any position prior to the max line length. (While this is obvious if you think about it, some might miss this.)

Your comment goes to step 1, are you suggesting a modification such as the following?

OLD

    1. Determine where the fold will occur. This location MUST be before or at the desired maximum column.

NEW

    1. Determine where the fold will occur. This location MUST be before or at the desired maximum column.  In the case of a forced folding, the location MUST be before or at the end of the line.

Also, there should be examples of forced folding.

Agreed.

Kent // co-author