diff options
| author | Junio C Hamano <gitster@pobox.com> | 2018-10-30 16:34:40 +0900 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2018-10-30 16:34:40 +0900 |
| commit | 94d00a5c4ebb12f2552118f261d8f82c05c2501d (patch) | |
| tree | 89cfa22e35b5476dd4ae8ab79277fa6f2eb25557 /gitattributes.txt | |
| parent | a4df8edd688285dc532353d4075d979d5ec20306 (diff) | |
| download | git-htmldocs-94d00a5c4ebb12f2552118f261d8f82c05c2501d.tar.gz | |
Autogenerated HTML docs for v2.19.1-708-g4ede3
Diffstat (limited to 'gitattributes.txt')
| -rw-r--r-- | gitattributes.txt | 30 |
1 files changed, 15 insertions, 15 deletions
diff --git a/gitattributes.txt b/gitattributes.txt index 92010b062..b8392fc33 100644 --- a/gitattributes.txt +++ b/gitattributes.txt @@ -303,21 +303,21 @@ number of pitfalls: attribute. If you decide to use the `working-tree-encoding` attribute in your repository, then it is strongly recommended to ensure that all clients working with the repository support it. - - 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. - - If a Git client, that does not support the `working-tree-encoding` - attribute, adds a new file `bar.ps1`, then `bar.ps1` will be - stored "as-is" internally (in this example probably as UTF-16). - A client with `working-tree-encoding` 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. ++ +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. ++ +If a Git client, that does not support the `working-tree-encoding` +attribute, adds a new file `bar.ps1`, then `bar.ps1` will be +stored "as-is" internally (in this example probably as UTF-16). +A client with `working-tree-encoding` 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. - Reencoding content to non-UTF encodings can cause errors as the conversion might not be UTF-8 round trip safe. If you suspect your |