| .. |
|
utf16be.json
|
1d007c26a4
- TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false).
|
12 år sedan |
|
utf16bebom.json
|
1d007c26a4
- TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false).
|
12 år sedan |
|
utf16le.json
|
1d007c26a4
- TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false).
|
12 år sedan |
|
utf16lebom.json
|
1d007c26a4
- TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false).
|
12 år sedan |
|
utf32be.json
|
1d007c26a4
- TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false).
|
12 år sedan |
|
utf32bebom.json
|
1d007c26a4
- TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false).
|
12 år sedan |
|
utf32le.json
|
1d007c26a4
- TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false).
|
12 år sedan |
|
utf32lebom.json
|
1d007c26a4
- TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false).
|
12 år sedan |
|
utf8.json
|
1d007c26a4
- TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false).
|
12 år sedan |
|
utf8bom.json
|
1d007c26a4
- TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false).
|
12 år sedan |
MelvMay-GG
1d007c26a4
- TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false).