| 1 |
W dniu wto, 21.11.2017 o godzinie 19∶20 +0100, użytkownik Ulrich Mueller |
| 2 |
napisał: |
| 3 |
> > > > > > On Tue, 21 Nov 2017, Michał Górny wrote: |
| 4 |
> > All paths specified in the Manifest file must consist of characters |
| 5 |
> > corresponding to valid UTF-8 code points excluding the NULL character |
| 6 |
> > (``U+0000``), the backwards slash (``\``) and characters classified |
| 7 |
> > as whitespace in the current version of the Unicode standard |
| 8 |
> > [#UNICODE]_. It is an error to use Manifest files in directories |
| 9 |
> > containing files whose names contain the disallowed characters. |
| 10 |
> > The forward slash (``/``) must be used as path separator. |
| 11 |
> |
| 12 |
> In addition to whitespace, you should also exclude C0 controls (U+0000 |
| 13 |
> to U+001F), DEL (U+007F), and C1 controls (U+0080 to U+009F). |
| 14 |
> |
| 15 |
> Rationale, these control characters can leave the user's terminal |
| 16 |
> in an unusable state when a package manager tries to output such a |
| 17 |
> filename in a message. As you reserve the backslash for a future |
| 18 |
> escape mechanism, this shouldn't be a too severe restriction. |
| 19 |
> |
| 20 |
|
| 21 |
Works for me. I'll update the spec later. Can you think of any other |
| 22 |
sequences that should be explicitly forbidden? |
| 23 |
|
| 24 |
-- |
| 25 |
Best regards, |
| 26 |
Michał Górny |
Archives