Charsets are registered by IANA. 
https://tools.ietf.org/html/rfc2978
https://www.iana.org/assignments/character-sets/character-sets.xhtml

Another good resource is ICU's converter explorer:

http://demo.icu-project.org/icu-bin/convexp

Tom.

Of course, it doesn't particularly help in this case because filesystems for the most part (*) just care about octets and don't interpret them. The filesystem isn't going to tell you an encoding scheme for a name. 

(*) Some filesystems do for example case folding or unicode normalizations. However for opening a file pretty much the only guarantee is that the octets you got from a directory listing of filesystem can be used to open the file. 

On Thu, Mar 7, 2019 at 11:32 AM Ben Boeckel via Modules <modules@lists.isocpp.org> wrote:

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
_______________________________________________
Modules mailing list
Modules@lists.isocpp.org
Subscription: http://lists.isocpp.org/mailman/listinfo.cgi/modules
Link to this post: http://lists.isocpp.org/modules/2019/03/0208.php

_______________________________________________
Modules mailing list
Modules@lists.isocpp.org
Subscription: http://lists.isocpp.org/mailman/listinfo.cgi/modules
Link to this post: http://lists.isocpp.org/modules/2019/03/0209.php