Fossil SCM
un-duplicate 'in the'
Commit
261c132280b2064e22dc3dd85e139dbdca52993d
Parent
8ab08d32c777129…
1 file changed
+1
-1
+1
-1
| --- src/utf8.c | ||
| +++ src/utf8.c | ||
| @@ -179,11 +179,11 @@ | ||
| 179 | 179 | ** |
| 180 | 180 | ** On Windows, characters in the range U+0001 to U+0031 and the |
| 181 | 181 | ** characters '"', '*', ':', '<', '>', '?' and '|' are invalid |
| 182 | 182 | ** to be used, except in the 'extended path' prefix ('?') and |
| 183 | 183 | ** as drive specifier (':'). Therefore, translate those to characters |
| 184 | -** in the in the range U+F001 - U+F07F (private use area), so those | |
| 184 | +** in the range U+F001 - U+F07F (private use area), so those | |
| 185 | 185 | ** characters never arrive in any Windows API. The filenames might |
| 186 | 186 | ** look strange in Windows explorer, but in the cygwin shell |
| 187 | 187 | ** everything looks as expected. |
| 188 | 188 | ** |
| 189 | 189 | ** See: <http://cygwin.com/cygwin-ug-net/using-specialnames.html> |
| 190 | 190 |
| --- src/utf8.c | |
| +++ src/utf8.c | |
| @@ -179,11 +179,11 @@ | |
| 179 | ** |
| 180 | ** On Windows, characters in the range U+0001 to U+0031 and the |
| 181 | ** characters '"', '*', ':', '<', '>', '?' and '|' are invalid |
| 182 | ** to be used, except in the 'extended path' prefix ('?') and |
| 183 | ** as drive specifier (':'). Therefore, translate those to characters |
| 184 | ** in the in the range U+F001 - U+F07F (private use area), so those |
| 185 | ** characters never arrive in any Windows API. The filenames might |
| 186 | ** look strange in Windows explorer, but in the cygwin shell |
| 187 | ** everything looks as expected. |
| 188 | ** |
| 189 | ** See: <http://cygwin.com/cygwin-ug-net/using-specialnames.html> |
| 190 |
| --- src/utf8.c | |
| +++ src/utf8.c | |
| @@ -179,11 +179,11 @@ | |
| 179 | ** |
| 180 | ** On Windows, characters in the range U+0001 to U+0031 and the |
| 181 | ** characters '"', '*', ':', '<', '>', '?' and '|' are invalid |
| 182 | ** to be used, except in the 'extended path' prefix ('?') and |
| 183 | ** as drive specifier (':'). Therefore, translate those to characters |
| 184 | ** in the range U+F001 - U+F07F (private use area), so those |
| 185 | ** characters never arrive in any Windows API. The filenames might |
| 186 | ** look strange in Windows explorer, but in the cygwin shell |
| 187 | ** everything looks as expected. |
| 188 | ** |
| 189 | ** See: <http://cygwin.com/cygwin-ug-net/using-specialnames.html> |
| 190 |