From Jason Turner

[locale.money.put.virtuals]

Diff to HTML by rtfpessoa

tmp/tmpvjg1n5wn/{from.md → to.md} RENAMED
@@ -33,15 +33,17 @@ Calls `str.width(0)`.
33
  `(str.flags() & str.showbase)` is nonzero. If the number of characters
34
  generated for the specified format is less than the value returned by
35
  `str.width()` on entry to the function, then copies of `fill` are
36
  inserted as necessary to pad to the specified width. For the value `af`
37
  equal to `(str.flags() & str.adjustfield)`, if `(af == str.internal)` is
38
- true, the fill characters are placed where `none` or `space` appears in
39
- the formatting pattern; otherwise if `(af == str.left)` is true, they
40
- are placed after the other characters; otherwise, they are placed before
41
- the other characters. It is possible, with some combinations of format
42
- patterns and flag values, to produce output that cannot be parsed using
43
- `num_get<>::get`.
 
 
44
 
45
  *Returns:* An iterator pointing immediately after the last character
46
  produced.
47
 
 
33
  `(str.flags() & str.showbase)` is nonzero. If the number of characters
34
  generated for the specified format is less than the value returned by
35
  `str.width()` on entry to the function, then copies of `fill` are
36
  inserted as necessary to pad to the specified width. For the value `af`
37
  equal to `(str.flags() & str.adjustfield)`, if `(af == str.internal)` is
38
+ `true`, the fill characters are placed where `none` or `space` appears
39
+ in the formatting pattern; otherwise if `(af == str.left)` is `true`,
40
+ they are placed after the other characters; otherwise, they are placed
41
+ before the other characters.
42
+
43
+ [*Note 1*: It is possible, with some combinations of format patterns
44
+ and flag values, to produce output that cannot be parsed using
45
+ `num_get<>::get`. — *end note*]
46
 
47
  *Returns:* An iterator pointing immediately after the last character
48
  produced.
49