<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 3/7/19 11:44 AM, Steve Downey wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAJEGDKokpnr73BvuaoThH_2m1bYujV-K5=dQ4a79azLPPM8rQQ@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">Charsets are registered by IANA. <br>
<a href="https://tools.ietf.org/html/rfc2978"
moz-do-not-send="true">https://tools.ietf.org/html/rfc2978</a><br>
<a
href="https://www.iana.org/assignments/character-sets/character-sets.xhtml"
moz-do-not-send="true">https://www.iana.org/assignments/character-sets/character-sets.xhtml</a><br>
</div>
</blockquote>
<p>Another good resource is ICU's converter explorer:</p>
<p><a class="moz-txt-link-freetext" href="http://demo.icu-project.org/icu-bin/convexp">http://demo.icu-project.org/icu-bin/convexp</a></p>
<p>Tom.<br>
</p>
<blockquote type="cite"
cite="mid:CAJEGDKokpnr73BvuaoThH_2m1bYujV-K5=dQ4a79azLPPM8rQQ@mail.gmail.com">
<div dir="ltr"><br>
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. <br>
<br>
(*) 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. </div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Mar 7, 2019 at 11:32
AM Ben Boeckel via Modules <<a
href="mailto:modules@lists.isocpp.org"
moz-do-not-send="true">modules@lists.isocpp.org</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">On Thu, Mar
07, 2019 at 11:16:15 -0500, Tom Honermann wrote:<br>
> Strawman update to the JSON schema to support this:<br>
> <br>
> {<br>
> ...<br>
> "definitions": {<br>
> + "filename-encoding": {<br>
> + "$id": "#filename-encoding",<br>
> + "type": [<br>
> + "string",<br>
> + ],<br>
> + "description": "The name of the character
encoding used to <br>
> interpret filenames",<br>
<br>
Which ISO/IETF standard are we referencing for encoding names?<br>
<br>
- utf-8<br>
- UTF-8<br>
- utf8<br>
- UTF8<br>
<br>
Do we need codepage information as well? Is that "standard"
anywhere?<br>
<br>
What happens if an encoding that cannot be losslessly
roundtripped is<br>
specified (e.g., Shift-JIS)?<br>
<br>
--Ben<br>
_______________________________________________<br>
Modules mailing list<br>
<a href="mailto:Modules@lists.isocpp.org" target="_blank"
moz-do-not-send="true">Modules@lists.isocpp.org</a><br>
Subscription: <a
href="http://lists.isocpp.org/mailman/listinfo.cgi/modules"
rel="noreferrer" target="_blank" moz-do-not-send="true">http://lists.isocpp.org/mailman/listinfo.cgi/modules</a><br>
Link to this post: <a
href="http://lists.isocpp.org/modules/2019/03/0208.php"
rel="noreferrer" target="_blank" moz-do-not-send="true">http://lists.isocpp.org/modules/2019/03/0208.php</a><br>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Modules mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Modules@lists.isocpp.org">Modules@lists.isocpp.org</a>
Subscription: <a class="moz-txt-link-freetext" href="http://lists.isocpp.org/mailman/listinfo.cgi/modules">http://lists.isocpp.org/mailman/listinfo.cgi/modules</a>
Link to this post: <a class="moz-txt-link-freetext" href="http://lists.isocpp.org/modules/2019/03/0209.php">http://lists.isocpp.org/modules/2019/03/0209.php</a>
</pre>
</blockquote>
<p><br>
</p>
</body>
</html>