Skip to content

Commit 6832908

Browse files
committed
glossary: Specify UTF-8 for all our JSON
I wish there was a cleaner reference for what UTF-8 was. But [1] seems too glib, and I can't find a more targetted link than just dropping folks into a Unicode chapter (which is what [1] does): The Unicode Standard, Version 6.0, §3.9 D92, §3.10 D95 (2011) With the current v8.0 (2015-06-17), it's still §3.9 D92 and §3.10 D95. I'd rather put this normative requirement in the configuration-spec files, but maintainer consensus was to put it in the glossary [2,3]. [1]: https://en.wikipedia.org/wiki/UTF-8 [2]: #146 (comment) [3]: #146 (comment) Signed-off-by: W. Trevor King <[email protected]>
1 parent 677dfe2 commit 6832908

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

glossary.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,14 @@ The [`config.json`](config.md) and [`runtime.json`](runtime-config.md) files in
1212

1313
An environment for executing processes with configurable isolation and resource limitations (namespaces, resource limits, mounts, …).
1414

15+
## JSON
16+
17+
All configuration [JSON][] MUST be encoded in [UTF-8][].
18+
1519
## Runtime
1620

1721
An implementation of this specification.
1822
It reads the [configuration files](#configuration) from a [bundle](#bundle), uses that information to create a [container](#container), launches an [application](#application) inside the container, and performs other [lifecycle actions](runtime.md).
23+
24+
[JSON]: http://json.org/
25+
[UTF-8]: http://www.unicode.org/versions/Unicode8.0.0/ch03.pdf

0 commit comments

Comments
 (0)