Autogenerated HTML docs for v2.19.1-708-g4ede3

1 files changed, 12 insertions, 18 deletions

diff --git a/gitattributes.html b/gitattributes.html
index 4278a03c8..4ba2bcc13 100644
--- a/gitattributes.html
+++ b/gitattributes.html
@@ -1091,25 +1091,19 @@ Alternative Git implementations (e.g. JGit or libgit2) and older Git
   in your repository, then it is strongly recommended to ensure that all

   clients working with the repository support it.

 </p>

-<div class="literalblock">

-<div class="content">

-<pre><code>For example, Microsoft Visual Studio resources files (`*.rc`) or

-PowerShell script files (`*.ps1`) are sometimes encoded in UTF-16.

-If you declare `*.ps1` as files as UTF-16 and you add `foo.ps1` with

-a `working-tree-encoding` enabled Git client, then `foo.ps1` will be

-stored as UTF-8 internally. A client without `working-tree-encoding`

-support will checkout `foo.ps1` as UTF-8 encoded file. This will

-typically cause trouble for the users of this file.</code></pre>

-</div></div>

-<div class="literalblock">

-<div class="content">

-<pre><code>If a Git client, that does not support the `working-tree-encoding`

-attribute, adds a new file `bar.ps1`, then `bar.ps1` will be

+<div class="paragraph"><p>For example, Microsoft Visual Studio resources files (<code>*.rc</code>) or

+PowerShell script files (<code>*.ps1</code>) are sometimes encoded in UTF-16.

+If you declare <code>*.ps1</code> as files as UTF-16 and you add <code>foo.ps1</code> with

+a <code>working-tree-encoding</code> enabled Git client, then <code>foo.ps1</code> will be

+stored as UTF-8 internally. A client without <code>working-tree-encoding</code>

+support will checkout <code>foo.ps1</code> as UTF-8 encoded file. This will

+typically cause trouble for the users of this file.</p></div>

+<div class="paragraph"><p>If a Git client, that does not support the <code>working-tree-encoding</code>

+attribute, adds a new file <code>bar.ps1</code>, then <code>bar.ps1</code> will be

 stored "as-is" internally (in this example probably as UTF-16).

-A client with `working-tree-encoding` support will interpret the

+A client with <code>working-tree-encoding</code> support will interpret the

 internal contents as UTF-8 and try to convert it to UTF-16 on checkout.

-That operation will fail and cause an error.</code></pre>

-</div></div>

+That operation will fail and cause an error.</p></div>

 </li>

 <li>

 <p>

@@ -2156,7 +2150,7 @@ frotz   unspecified</code></pre>
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2018-06-01 00:13:01 PDT

+ 2018-10-30 16:33:48 JST

 </div>

 </div>

 </body>