<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:"Yu Gothic";
        panose-1:2 11 4 0 0 0 0 0 0 0;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:"\@Yu Gothic";
        panose-1:2 11 4 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;
        color:windowtext;}
.MsoChpDefault
        {mso-style-type:export-only;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
--></style>
<div class="WordSection1">
<p class="MsoNormal">Considering it would break compatibility with every non-EN_US batch file on the planet, I’m betting that the probability is still going to be close to 0 even 10 – 20 years from now. It certainly won’t be more than 50%.</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Keep in mind even on the latest Win10 bits that’s an experimental switch hidden deep within pages of options menus; I don’t know of any plans to change the defaults to UTF-8 for any of the default locales. The appcompat fallout would be
quite high given the previous assumption that multibyte code pages could use at most 2 encoding units. (I don’t work in Windows and don’t *<b>know</b>* about plans or lack thereof to make such a change but it would surprise me)</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Case in point: if the program in question is compiled with a VS version older than 2017 Update 9 and the user tries to turn that option on, then iostreams + locales assert in debug mode and corrupt memory in release mode.</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Billy3</p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Tom Honermann <tom@honermann.net><br>
<b>Sent:</b> Monday, September 9, 2019 12:46:13 PM<br>
<b>To:</b> Billy O'Neal (VC LIBS) <bion@microsoft.com>; Corentin <corentin.jabot@gmail.com><br>
<b>Cc:</b> Zach Laine <whatwasthataddress@gmail.com>; Library Working Group <lib@lists.isocpp.org>; Victor Zverovich <victor.zverovich@gmail.com>; unicode@isocpp.open-std.org <unicode@open-std.org><br>
<b>Subject:</b> Re: [isocpp-lib] New issue: Are std::format field widths code units, code points, or something else?</font>
<div> </div>
</div>
<div>
<div class="moz-cite-prefix">On 9/9/19 3:33 PM, Billy O'Neal (VC LIBS) wrote:<br>
</div>
<blockquote type="cite" cite="mid:DM6PR21MB1226F2E0870062B582A0A5C7CBB70@DM6PR21MB1226.namprd21.prod.outlook.com">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:"Yu Gothic";
        panose-1:2 11 4 0 0 0 0 0 0 0;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:"\@Yu Gothic";
        panose-1:2 11 4 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;
        color:windowtext;}
.MsoChpDefault
        {mso-style-type:export-only;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
--></style>
<div class="WordSection1">
<p class="MsoNormal">> everything within the programs assumes ACP, if you are trying to say output to the console, and the ACP is utf8, the console has to expect utf8<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The probability of ACP being UTF-8 is approximately zero.</p>
</div>
</blockquote>
<p>Today, yes. What does your crystal ball say about 10 or 20 years from now?</p>
<p>Tom.</p>
</div>
</body>
</html>