Skip to content

Commit

Permalink
runtime: RFC 2119 SHOULDs in the "Character encodings" section
Browse files Browse the repository at this point in the history
These slipped through e41ffc1 (Use RFC 2119's keywords (MUST, MAY,
...), 2015-12-02, opencontainers#9).

Signed-off-by: W. Trevor King <wking@tremily.us>
  • Loading branch information
wking committed Jul 5, 2016
1 parent 60148f0 commit b7429c8
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions runtime.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,8 +17,8 @@ If the runtime is invoked with an unrecognized command, it MUST exit with a nonz

## Character encodings

This API specification does not cover character encodings, but runtimes should conform to their native operating system.
For example, POSIX systems define [`LANG` and related environment variables][posix-lang] for [declaring][posix-locale-encoding] [locale-specific character encodings][posix-encoding], so a runtime in an `en_US.UTF-8` locale should write its [version](#version) to stdout in [UTF-8][].
This API specification does not cover character encodings, but runtimes SHOULD conform to their native operating system.
For example, POSIX systems define [`LANG` and related environment variables][posix-lang] for [declaring][posix-locale-encoding] [locale-specific character encodings][posix-encoding], so a runtime in an `en_US.UTF-8` locale SHOULD write its [version](#version) to stdout in [UTF-8][].

## Commands

Expand Down

0 comments on commit b7429c8

Please sign in to comment.