Changeset 458 for draft-ietf-httpbis/latest/p3-payload.html

Timestamp:

28/02/09 19:39:48 (13 years ago)

Author:

julian.reschke@…

Message:

make indentation of examples consistent

File:

• draft-ietf-httpbis/latest/p3-payload.html (modified) (3 diffs)

draft-ietf-httpbis/latest/p3-payload.html

@@ -815 +815 @@
          by the IANA. Example tags include:
       </p>
-      <div id="rfc.figure.u.11"></div><pre class="text">    en, en-US, en-cockney, i-cherokee, x-pig-latin
+      <div id="rfc.figure.u.11"></div><pre class="text">  en, en-US, en-cockney, i-cherokee, x-pig-latin
 </pre><p id="rfc.section.2.4.p.6">where any two-letter primary-tag is an ISO-639 language abbreviation and any two-letter initial subtag is an ISO-3166 country
          code. (The last three tags above are not registered tags; all but the last are examples of tags which could be registered
@@ -856 +856 @@
          and Content-Encoding. These define a two-layer, ordered encoding model:
       </p>
-      <div id="rfc.figure.u.14"></div><pre class="text">    entity-body := Content-Encoding( Content-Type( data ) )
+      <div id="rfc.figure.u.14"></div><pre class="text">  entity-body := Content-Encoding( Content-Type( data ) )
 </pre><p id="rfc.section.3.2.1.p.3">Content-Type specifies the media type of the underlying data. Content-Encoding may be used to indicate any additional content
          codings applied to the data, usually for the purpose of data compression, that are a property of the requested resource. There
@@ -1657 +1657 @@
   <a href="#content-disposition" class="smpl">disp-extension-parm</a> = <a href="#core.rules" class="smpl">token</a> "=" ( <a href="#core.rules" class="smpl">token</a> / <a href="#core.rules" class="smpl">quoted-string</a> )
 </pre><p id="rfc.section.B.1.p.3">An example is</p>
-      <div id="rfc.figure.u.39"></div><pre class="text">   Content-Disposition: attachment; filename="fname.ext"
+      <div id="rfc.figure.u.39"></div><pre class="text">  Content-Disposition: attachment; filename="fname.ext"
 </pre><p id="rfc.section.B.1.p.5">The receiving user agent <em class="bcp14">SHOULD NOT</em> respect any directory path information present in the filename-parm parameter, which is the only parameter believed to apply
          to HTTP implementations at this time. The filename <em class="bcp14">SHOULD</em> be treated as a terminal component only.