<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-netmod-artwork-folding" target="https://datatracker.ietf.org/doc/html/draft-ietf-netmod-artwork-folding-12">
   <front>
      <title>Handling Long Lines in Content of Internet-Drafts and RFCs</title>
      <author initials="K." surname="Watsen" fullname="Kent Watsen">
         <organization>Watsen Networks</organization>
      </author>
      <author initials="E." surname="Auerswald" fullname="Erik Auerswald">
         <organization>Individual Contributor</organization>
      </author>
      <author initials="A." surname="Farrel" fullname="Adrian Farrel">
         <organization>Old Dog Consulting</organization>
      </author>
      <author initials="Q." surname="Wu" fullname="Qin Wu">
         <organization>Huawei Technologies</organization>
      </author>
      <date month="January" day="20" year="2020" />
      <abstract>
	 <t>This document defines two strategies for handling long lines in width-bounded text content.  One strategy, called the &quot;single backslash&quot; strategy, is based on the historical use of a single backslash (&#x27;\&#x27;) character to indicate where line-folding has occurred, with the continuation occurring with the first character that is not a space character (&#x27; &#x27;) on the next line.  The second strategy, called the &quot;double backslash&quot; strategy, extends the first strategy by adding a second backslash character to identify where the continuation begins and is thereby able to handle cases not supported by the first strategy.  Both strategies use a self-describing header enabling automated reconstitution of the original content.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-netmod-artwork-folding-12" />
   
</reference>
