tmp/tmpvq4jak0e/{from.md → to.md}
RENAMED
|
@@ -49,13 +49,13 @@ consisting solely of one and two period characters respectively, have
|
|
| 49 |
special meaning. The following characteristics of filenames are
|
| 50 |
operating system dependent:
|
| 51 |
|
| 52 |
- The permitted characters. \[*Example 1*: Some operating systems
|
| 53 |
prohibit the ASCII control characters (0x00 – 0x1F) in
|
| 54 |
-
filenames. — *end example*] \[*Note 1*:
|
| 55 |
-
|
| 56 |
-
Character Set:
|
| 57 |
`A B C D E F G H I J K L M N O P Q R S T U V W X Y Z`
|
| 58 |
`a b c d e f g h i j k l m n o p q r s t u v w x y z`
|
| 59 |
`0 1 2 3 4 5 6 7 8 9 . _ -` — *end note*]
|
| 60 |
- The maximum permitted length.
|
| 61 |
- Filenames that are not permitted.
|
|
@@ -80,11 +80,11 @@ A *root-name* identifies the starting location for pathname resolution
|
|
| 80 |
required.
|
| 81 |
|
| 82 |
[*Note 2*: Many operating systems define a name beginning with two
|
| 83 |
*directory-separator* characters as a *root-name* that identifies
|
| 84 |
network or other resource locations. Some operating systems define a
|
| 85 |
-
single letter followed by a colon as a drive specifier
|
| 86 |
identifying a specific device such as a disk drive. — *end note*]
|
| 87 |
|
| 88 |
If a *root-name* is otherwise ambiguous, the possibility with the
|
| 89 |
longest sequence of characters is chosen.
|
| 90 |
|
|
@@ -96,11 +96,11 @@ longest sequence of characters is chosen.
|
|
| 96 |
|
| 97 |
1. If the path is empty, stop.
|
| 98 |
2. Replace each slash character in the *root-name* with a
|
| 99 |
*preferred-separator*.
|
| 100 |
3. Replace each *directory-separator* with a *preferred-separator*.
|
| 101 |
-
\[*Note 4*: The generic pathname grammar
|
| 102 |
*directory-separator* as one or more slashes and
|
| 103 |
*preferred-separator*s. — *end note*]
|
| 104 |
4. Remove each dot filename and any immediately following
|
| 105 |
*directory-separator*.
|
| 106 |
5. As long as any appear, remove a non-dot-dot filename immediately
|
|
|
|
| 49 |
special meaning. The following characteristics of filenames are
|
| 50 |
operating system dependent:
|
| 51 |
|
| 52 |
- The permitted characters. \[*Example 1*: Some operating systems
|
| 53 |
prohibit the ASCII control characters (0x00 – 0x1F) in
|
| 54 |
+
filenames. — *end example*] \[*Note 1*: Wider portability can be
|
| 55 |
+
achieved by limiting *filename* characters to the POSIX Portable
|
| 56 |
+
Filename Character Set:
|
| 57 |
`A B C D E F G H I J K L M N O P Q R S T U V W X Y Z`
|
| 58 |
`a b c d e f g h i j k l m n o p q r s t u v w x y z`
|
| 59 |
`0 1 2 3 4 5 6 7 8 9 . _ -` — *end note*]
|
| 60 |
- The maximum permitted length.
|
| 61 |
- Filenames that are not permitted.
|
|
|
|
| 80 |
required.
|
| 81 |
|
| 82 |
[*Note 2*: Many operating systems define a name beginning with two
|
| 83 |
*directory-separator* characters as a *root-name* that identifies
|
| 84 |
network or other resource locations. Some operating systems define a
|
| 85 |
+
single letter followed by a colon as a drive specifier — a *root-name*
|
| 86 |
identifying a specific device such as a disk drive. — *end note*]
|
| 87 |
|
| 88 |
If a *root-name* is otherwise ambiguous, the possibility with the
|
| 89 |
longest sequence of characters is chosen.
|
| 90 |
|
|
|
|
| 96 |
|
| 97 |
1. If the path is empty, stop.
|
| 98 |
2. Replace each slash character in the *root-name* with a
|
| 99 |
*preferred-separator*.
|
| 100 |
3. Replace each *directory-separator* with a *preferred-separator*.
|
| 101 |
+
\[*Note 4*: The generic pathname grammar defines
|
| 102 |
*directory-separator* as one or more slashes and
|
| 103 |
*preferred-separator*s. — *end note*]
|
| 104 |
4. Remove each dot filename and any immediately following
|
| 105 |
*directory-separator*.
|
| 106 |
5. As long as any appear, remove a non-dot-dot filename immediately
|