- From: Mark Nottingham <notifications@github.com>
- Date: Mon, 30 May 2016 18:31:23 -0700
- To: w3ctag/spec-reviews <spec-reviews@noreply.github.com>
- Cc:
Received on Tuesday, 31 May 2016 01:31:54 UTC
FYI: https://tools.ietf.org/html/draft-ietf-appsawg-file-scheme-10 4. File Name Encoding File systems use various encoding schemes to store file and directory names. Many modern file systems store file and directory names as arbitrary sequences of octets, in which case the representation as an encoded string often depends on the user's localization settings, or defaults to UTF-8 [STD63]. When a file URI is produced, characters not allowed by the syntax in Section 2 SHOULD be percent-encoded as characters using UTF-8 encoding, as per [RFC3986], Section 2.5. However, encoding information for file and/or directory names might not be available. In these cases, implementations MAY use heuristics to determine the encoding. If that fails, they SHOULD percent-encode the raw bytes of the label directly. @annevk seem sane(r)? --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/spec-reviews/issues/59#issuecomment-222574065
Received on Tuesday, 31 May 2016 01:31:54 UTC