My notes indicate that it's narrative text about the implications and
consequences for putting the three characters into the set. I can have
that. I don't think we found wording changes.

On Sat, Apr 23, 2022, 09:04 Tom Honermann via SG16 <sg16_at_[hidden]>
wrote:

> SG16 will hold a telecon on Wednesday, April 27th, at 19:30 UTC (timezone
> conversion
> <https://www.timeanddate.com/worldclock/converter.html?iso=20220427T193000&p1=1440&p2=tz_pdt&p3=tz_mdt&p4=tz_cdt&p5=tz_edt&p6=tz_cest>
> ).
>
> The agenda is:
>
> - P2286R7: Formatting Ranges
> <https://wiki.edg.com/pub/Wg21telecons2022/LibraryWorkingGroup/p2286r7.html>
> - Review recent updates and confirm direction.
> - (The link is to a draft revision attached to the LWG wiki page)
> - P2558R0: Add @, $, and ` to the basic character set
> <https://wg21.link/p2558>
> - Continue review pending the availability of an updated revision.
> - D2572R0: std::format() fill character allowances
> <https://rawgit.com/tahonermann/std-proposals/master/d2572r0.html>
> - Continue review pending the availability of an updated revision.
>
> LWG has tentatively approved
> <https://github.com/cplusplus/papers/issues/977#issuecomment-1107071392>
> P2286R7 as linked above pending SG16 confirmation of design intent and
> wording for non-Unicode encodings. Please review the SG16 2022-01-26
> meeting summary
> <https://github.com/sg16-unicode/sg16-meetings#january-26th-2022> for
> previously discussed concerns. A few wording details are still being
> discussed outside of the mailing lists, so the paper revision linked above
> may still receive some updates prior to our meeting.
>
> Further review of P2558R0 and D2572R0 are scheduled pending updates from
> the authors to address feedback from the SG16 2022-04-13 telecon
> <https://github.com/sg16-unicode/sg16-meetings#april-13th-2022> (which I
> have yet to publish).
>
> Tom.
> --
> SG16 mailing list
> SG16_at_[hidden]
> https://lists.isocpp.org/mailman/listinfo.cgi/sg16
>