Addition of the new flag "file-read-mode" into the analysis server to fix the offset bug with Intel…

pkg/analysis_server/doc/api.html

Index: pkg/analysis_server/doc/api.html
diff --git a/pkg/analysis_server/doc/api.html b/pkg/analysis_server/doc/api.html
index c3214a9c54a7ea1416aaa17f152e8f2be384ff55..0e5945043530d8d0df35a089b3d90a6449700a25 100644
--- a/pkg/analysis_server/doc/api.html
+++ b/pkg/analysis_server/doc/api.html
@@ -173,6 +173,22 @@ dt.typeDefinition {
       errors produced for all files in the actual analysis roots.
       </dd>
     </dl>
+    <dl>
+      <dt>--file-read-mode</dt>
+      <dd>
+      An enumeration of the ways files can be read from disk. Some clients
+      normalize end of line characters which would make the file offset and
+      range information incorrect. The default option is <tt>as-is</tt>, but
+      can also be set to <tt>normalize-eol-always</tt>. The default option
+      (<tt>as-is</tt>) reads files as they are on disk. The
+      <tt>normalize-eol-always</tt> option does the following:
+      <ul>
+        <li>'\r\n' is converted to '\n';</li>
+        <li>'\r' by itself is converted to '\n';</li>
+        <li>this happens regardless of the OS editor is running on.</li>
+      </ul>
+      </dd>
+    </dl>
     </blockquote>
     <h2 class="domain"><a name="domain_server">Domain: server</a></h2>
       <p>