An updated draft of P2572R0 (std::format() fill character allowances)
<https://raw.githack.com/tahonermann/std-proposals/master/d2572r0.html>
is now available.

The following changes have been made relative to the previously reviewed
draft
<https://rawcdn.githack.com/sg16-unicode/sg16-meetings/c84e3e4eef341795fb9ac44824525a3a89583fa7/presentations/2022-04-13-d2572r0.html>.

  * The proposal was modified to align with the outcome of our last
    review
    <https://github.com/sg16-unicode/sg16-meetings#april-13th-2022>. It
    now seeks to standardize the behavior exhibited by gcc and MSVC.
  * Wording was updated to align with the proposal direction.
  * The character examples were extended to include the delete character
    and a right-to-left directional character (Hebrew letter tav).
  * The "Estimated display width restrictions" section was expanded to
    discuss the option of producing an error only when the requested
    field alignment cannot be achieved.
  * The "Existing practice" section was updated to include character
    names, example behavior for the delete and Hebrew letter tav
    characters, and an additional note about handling of right-to-left
    characters.
  * The "Existing practice" section was updated to note that the
    previously reported buffer overflow that occurs with MSVC 19.31 has
    been fixed for the next release and to include an example of the
    diagnostic that is now issued.
  * A new "Future considerations and ABI" section has been added.
  * The "Implementation experience" section has been updated to note
    that, now that the paper seeks to standardize the current gcc and
    MSVC behavior, that the proposal has been implemented (with the
    exception of some possible ABI break mitigations that may or may not
    be misguided).

Tom.