<div dir="ltr"><div>Not sure how to do that proceduraly but here is some alternative wording. </div><div>The "runtime" locale-tied encoding is *assumed to be* a super set of the execution encoding - to the extent the standard doesn't distinguish between the two <br></div><div><br></div><div><br></div><div>If Period::type is micro, but the <ins>abstract</ins> character <ins>µ , which has the universal character name </ins> U+00B5 cannot be represented in the <ins>execution</ins> encoding <del>used for</del><ins> associated with the character type </ins> charT, the unit suffix "us" is used instead of "µs".<br></div><div><br></div><div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 4 Nov 2019 at 15:42, Tom Honermann via Lib-Ext <<a href="mailto:lib-ext@lists.isocpp.org">lib-ext@lists.isocpp.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<p>A new LWG issue was filed for this question today:<br>
- <a href="https://cplusplus.github.io/LWG/issue3314" target="_blank">https://cplusplus.github.io/LWG/issue3314</a></p>
<p>This issue concerns the ostream inserters added for <tt>std::chrono::duration</tt>
in C++20 and what the intended behavior is for a duration when <tt>period::type</tt>
is <tt>micro</tt>.</p>
<p><a href="http://eel.is/c++draft/time.duration.io#4" target="_blank">[time.duration.io]p4</a>
states:<br>
</p>
<p>
</p><blockquote type="cite">
<p>If <tt><span>Period<span>::</span>type</span></tt>
is <tt><span>micro</span></tt>,
but the character U+00B5 cannot be represented in
the encoding used for <tt><span>charT</span></tt>,
the unit suffix <tt><span><span>"us"</span></span></tt> is used instead
of <tt><span><span>"μs"</span></span></tt>.</p>
</blockquote>
<p></p>
<p>The question is with regard to which one of the encodings used
for <tt>charT</tt> is referred to here; the compile-time
execution character set or the run-time locale dependent native
character set?<br>
</p>
<p>The proposed resolution specifies that the compile-time execution
character set is the intended one. My expectation is that this
aligns with existing implementations, but I haven't checked.</p>
<p>Tom.<br>
</p>
</div>
_______________________________________________<br>
Lib-Ext mailing list<br>
<a href="mailto:Lib-Ext@lists.isocpp.org" target="_blank">Lib-Ext@lists.isocpp.org</a><br>
Subscription: <a href="https://lists.isocpp.org/mailman/listinfo.cgi/lib-ext" rel="noreferrer" target="_blank">https://lists.isocpp.org/mailman/listinfo.cgi/lib-ext</a><br>
Link to this post: <a href="http://lists.isocpp.org/lib-ext/2019/11/13309.php" rel="noreferrer" target="_blank">http://lists.isocpp.org/lib-ext/2019/11/13309.php</a><br>
</blockquote></div>