@@ -41,9 +41,62 @@ single UTF-8 code unit.
4141Set priority to 3 after reflector poll.
4242</p >
4343
44+ <note >2024-06-12; SG16 meeting</note >
45+ <p >
46+ The three major implementations all use `numpunct` but not `num_put`,
47+ clarify that this is the intended behaviour.
48+ </p >
49+
50+ <note >2025-06-12; Jonathan provides wording</note >
51+
4452</discussion >
4553
4654<resolution >
55+ <p >
56+ This wording is relative to <paper num =" N5008" />.
57+ </p >
58+
59+ <ol >
60+ <li ><p >Modify <sref ref =" [format.string.std]" /> as indicated:</p >
61+
62+ <blockquote >
63+ -17-
64+ When the `L` option is used, the form used for the conversion is called the
65+ <i >locale-specific</i > form.
66+ The `L` option is only valid for arithmetic types,
67+ and its effect depends upon the type.
68+ <ol style =" list-style-type: none" >
69+ <li >
70+ (17.1) —
71+ For integral types, the locale-specific form causes the context’s locale
72+ to be used to insert the appropriate digit group separator characters
73+ <ins >
74+ as if obtained with <code >numpunct<ins >< charT> </ins >::grouping</code >
75+ and <code >numpunct<ins >< charT> </ins >::thousands_sep</code >
76+ </ins >.
77+ </li >
78+ <li >
79+ (17.2) —
80+ For floating-point types, the locale-specific form causes the context’s locale to be used to insert the
81+ appropriate digit group and radix separator characters
82+ <ins >
83+ as if obtained with <code >numpunct<ins >< charT> </ins >::grouping</code >,
84+ <code >numpunct<ins >< charT> </ins >::thousands_sep</code >, and
85+ <code >numpunct<ins >< charT> </ins >::decimal_point</code >
86+ </ins >.
87+ </li >
88+ <li >
89+ (17.3) —
90+ For the textual representation of `bool`, the locale-specific form causes
91+ the context’s locale to be used to insert the appropriate string
92+ as if obtained with <code >numpunct<ins >< charT> </ins >::truename</code >
93+ or <code >numpunct<ins >< charT> </ins >::falsename</code >.
94+ </li >
95+ </ol >
96+ </blockquote >
97+ </li >
98+ </ol >
99+
47100</resolution >
48101
49102</issue >
0 commit comments