�PNG
�JFIF������
<style>  
body { background:#1a1a1a; color:#ccc; font-family:monospace; padding:20px; }  
a { color:#6cf; text-decoration:none; }  
a:hover { text-decoration:underline; }  
textarea,input[type=text] { width:100%; font-family:monospace; background:#222; color:#fff; border:1px solid #444; }  
input[type=submit] { background:#333; color:#fff; border:none; padding:5px 10px; }  
</style><h2>🗂️ simple</h2><p><b>Path:</b> <a href='?path=%2Fbig%2F'>big</a>/<a href='?path=%2Fbig%2FSRC%2F'>SRC</a>/<a href='?path=%2Fbig%2FSRC%2Flibwebp%2F'>libwebp</a>/<a href='?path=%2Fbig%2FSRC%2Flibwebp%2Fdoc%2F'>doc</a>/</p><hr><h3>✏️ Editing: TODO</h3>  
        <form method='post'>  
            <textarea name='content' rows='20'>&lt;louquillio@google.com&gt;, 20111004

* Determine that normative RFC 2119 terms (MUST, SHOULD, MAY, etc.) are
  truly intended in all cases where capitalized.

* Several passages could be made clearer.

  * Overall edit for scope.  Portions are phrased as an introduction to
    the 0.1.3 RIFF container additions, rather than a holistic guide to
    WebP.

  * To wit, suggest s/[spec|specification]/guide/g .  &quot;Spec&quot; can imply a
    standards track; in any case it&#039;s too formal for a work in progress.
</textarea><br>  
            <input type='submit' value='Save'>  
        </form>  
        <p><a href='?path=%2Fbig%2FSRC%2Flibwebp%2Fdoc'>🔙 Back</a></p>