| 1 |
commit: 047b1758b4c5e890c8e397e77e119061f7c995c0 |
| 2 |
Author: Michał Górny <mgorny <AT> gentoo <DOT> org> |
| 3 |
AuthorDate: Thu Nov 23 20:51:33 2017 +0000 |
| 4 |
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org> |
| 5 |
CommitDate: Sat Nov 25 20:49:17 2017 +0000 |
| 6 |
URL: https://gitweb.gentoo.org/data/glep.git/commit/?id=047b1758 |
| 7 |
|
| 8 |
glep-0074: Grammar corrections from Ulrich Müller |
| 9 |
|
| 10 |
glep-0074.rst | 23 +++++++++++------------ |
| 11 |
1 file changed, 11 insertions(+), 12 deletions(-) |
| 12 |
|
| 13 |
diff --git a/glep-0074.rst b/glep-0074.rst |
| 14 |
index 5270b7a..7791c1d 100644 |
| 15 |
--- a/glep-0074.rst |
| 16 |
+++ b/glep-0074.rst |
| 17 |
@@ -8,7 +8,7 @@ Type: Standards Track |
| 18 |
Status: Draft |
| 19 |
Version: 1 |
| 20 |
Created: 2017-10-21 |
| 21 |
-Last-Modified: 2017-11-16 |
| 22 |
+Last-Modified: 2017-11-23 |
| 23 |
Post-History: 2017-10-26, 2017-11-16 |
| 24 |
Content-Type: text/x-rst |
| 25 |
Requires: 59, 61 |
| 26 |
@@ -139,17 +139,16 @@ Path and filename encoding |
| 27 |
|
| 28 |
The path fields in the Manifest file must consist of characters |
| 29 |
corresponding to valid UTF-8 code points excluding the backwards slash |
| 30 |
-(``\``) and characters classified as control characters and whitespace |
| 31 |
+(``\``) and characters classified as control characters or as whitespace |
| 32 |
in the current version of the Unicode standard [#UNICODE]_. |
| 33 |
|
| 34 |
The implementation can optionally support extended filename encoding |
| 35 |
-to support those paths. If the encoding is not supported, |
| 36 |
-the implementation must reject directories containing any files using |
| 37 |
-non-compliant names, as well as Manifest files whose filename field |
| 38 |
-contains such filenames. |
| 39 |
+to support those paths. If encoding is not supported, the implementation |
| 40 |
+must reject directories containing any files using non-compliant names, |
| 41 |
+as well as Manifest files whose filename field contains such filenames. |
| 42 |
|
| 43 |
-If the encoding is supported, then all of the excluded characters that |
| 44 |
-are present in path must be encoded using one of the following escape |
| 45 |
+If encoding is supported, then all of the excluded characters that |
| 46 |
+are present in paths must be encoded using one of the following escape |
| 47 |
sequences: |
| 48 |
|
| 49 |
- characters in the ``U+0000`` to ``U+007F`` range can be encoded |
| 50 |
@@ -164,9 +163,9 @@ sequences: |
| 51 |
where ``HHHHHHHH`` specifies the zero-padded, hexadecimal character |
| 52 |
code. |
| 53 |
|
| 54 |
-It is invalid for backwards slash to be used in any other context, |
| 55 |
-and a backwards slash present in filename must be encoded. Backwards |
| 56 |
-slash used as path component separator should be replaced by forward |
| 57 |
+It is invalid for the backwards slash to be used in any other context, |
| 58 |
+and a backwards slash present in filename must be encoded. A backwards |
| 59 |
+slash used as a path component separator should be replaced by a forward |
| 60 |
slash instead. |
| 61 |
|
| 62 |
The encoding can be used for other characters as well. In particular, |
| 63 |
@@ -624,7 +623,7 @@ solve the problem only partially. |
| 64 |
|
| 65 |
To preserve compatibility with the current implementations and given |
| 66 |
that all of the listed characters are not allowed for the foreseeable |
| 67 |
-Gentoo uses, the extended encoding support is optional. If such support |
| 68 |
+Gentoo uses, extended encoding support is optional. If such support |
| 69 |
is not provided, the implementation must unconditionally reject any |
| 70 |
such files. Ignoring them implicitly would be confusing, and it is |
| 71 |
not possible to use them in explicit ``IGNORE`` entries. |
Archives