Date: Thu, 7 Mar 2019 11:32:07 -0500
On Thu, Mar 07, 2019 at 11:16:15 -0500, Tom Honermann wrote:
> Strawman update to the JSON schema to support this:
>
> {
> ...
> "definitions": {
> + "filename-encoding": {
> + "$id": "#filename-encoding",
> + "type": [
> + "string",
> + ],
> + "description": "The name of the character encoding used to
> interpret filenames",
Which ISO/IETF standard are we referencing for encoding names?
- utf-8
- UTF-8
- utf8
- UTF8
Do we need codepage information as well? Is that "standard" anywhere?
What happens if an encoding that cannot be losslessly roundtripped is
specified (e.g., Shift-JIS)?
--Ben
> Strawman update to the JSON schema to support this:
>
> {
> ...
> "definitions": {
> + "filename-encoding": {
> + "$id": "#filename-encoding",
> + "type": [
> + "string",
> + ],
> + "description": "The name of the character encoding used to
> interpret filenames",
Which ISO/IETF standard are we referencing for encoding names?
- utf-8
- UTF-8
- utf8
- UTF8
Do we need codepage information as well? Is that "standard" anywhere?
What happens if an encoding that cannot be losslessly roundtripped is
specified (e.g., Shift-JIS)?
--Ben
Received on 2019-03-07 17:32:12