SG16 meetings are typically held on Wednesdays from 19:30-21:00 UTC on the 2nd and 4th weeks of each month, but scheduling conflicts or other time pressures sometimes force alternative scheduling. Meeting invitations are sent to the mailing list and prior attendees. To request an invitation, please contact tom@honermann.net.
The next SG16 meeting is scheduled for Wednesday, January 14th, 2026, from 19:30-21:00 UTC (timezone conversion).
Draft agenda:
- Continue discussion of P3688R5: ASCII character utilities.
- December 10th, 2025
- November 19th, 2025
- October 22nd, 2025
- October 8th, 2025
- September 24th, 2025
- September 10th, 2025
- August 27th, 2025
- July 30th, 2025
- July 16th, 2025
- June 11th, 2025
- May 28th, 2025
- May 14th, 2025
- April 23rd, 2025
- April 9th, 2025
- March 26th, 2025
- March 12th, 2025
- February 26th, 2025
- February 5th, 2025
- January 22nd, 2025
- Meetings held in 2024
- Meetings held in 2023
- Meetings held in 2022
- Meetings held in 2021
- Meetings held in 2020
- Meetings held in 2019
- Meetings held in 2018
- Prior std-text-wg meetings
- Attendees:
- Braden Ganetsky
- Corentin Jabot
- Eddie Nolan
- Hubert Tong
- Jan Schultke
- Jens Maurer
- Matthias Wippich
- Matthew Taylor
- Steve Downey
- Tom Honermann
- Victor Zverovich
- [ Editor's note: The SG16 chair has fallen far behind his obligations but will publish a proper summary of this meeting in due time. ]
- P3688R5: ASCII character utilities:
- [ Editor's note: D3688R5 was the active paper under discussion at the telecon. The agenda and links used here reference P3688R5 since the links to the draft paper were ephemeral. The published document may differ from the reviewed draft revision. ]
- Poll 1: D3688R5: Drop the char8_t and char16_t overloads due to code unit and code point confusion
- Attendance: 11 (2 abstentions)
SF F N A SA 0 1 1 4 3 - Consensus against.
- Attendance: 11 (2 abstentions)
- P3695R2: Deprecate implicit conversions between Unicode character types.
- P3688R4: ASCII character utilities.
- Attendees:
- Corentin Jabot
- Eddie Nolan
- Fraser Gordon
- Hubert Tong
- Jan Schultke
- Jens Maurer
- Peter Bindels
- Steve Downey
- Tom Honermann
- Victor Zverovich
- [ Editor's note: The SG16 chair has fallen far behind his obligations but will publish a proper summary of this meeting in due time. ]
- P3695R2: Deprecate implicit conversions between Unicode character types:
- Poll 1: P3695R2: Recommend deprecating conversions between char8_t and wchar_t.
- Attendees: 10
SF F N A SA 3 3 3 1 0 - Consensus.
- Attendees: 10
- Poll 2: P3695R2: Forward to EWG.
- Attendees: 10
SF F N A SA 4 4 2 0 0 - Strong consensus.
- Attendees: 10
- Poll 1: P3695R2: Recommend deprecating conversions between char8_t and wchar_t.
- P3688R4: ASCII character utilities:
- US 5-018: 5 [lex] Define "whitespace character".
- US 189-304: 31.12.6.1, 31.12.6.5.6, 31.12.6.5.7, D.22.2 rename
filesystem::pathmethods.
- Attendees:
- Alisdair Meredith
- Braden Ganetsky
- Corentin Jabot
- Eddie Nolan
- Fraser Gordon
- Jan Schultke
- Jens Maurer
- Peter Bindels
- Robin Leroy
- Steve Downey
- Tom Honermann
- Victor Zverovich
- [ Editor's note: The SG16 chair has fallen far behind his obligations but will publish a proper summary of this meeting in due time. ]
- US 5-018: 5 [lex] Define "whitespace character":
- Poll 1: Forward P3657R1 to CWG as a recommended resolution for US 5-018.
- Attendees: 11 (one abstention)
SF F N A SA 4 5 1 0 0 - Strong consensus.
- Attendees: 11 (one abstention)
- Poll 1: Forward P3657R1 to CWG as a recommended resolution for US 5-018.
- US 189-304: 31.12.6.1, 31.12.6.5.6, 31.12.6.5.7, D.22.2 rename
filesystem::pathmethods:- Poll 2: Recommend resolving US 189-304 by renaming
\[generic_\]system_encoded_string()to\[generic_\]native_encoded_string().- Attendees: 10
SF F N A SA 2 8 0 0 0 - Unanimous consensus.
- Attendees: 10
- Poll 2: Recommend resolving US 189-304 by renaming
- US 8-021: 5.5p1 [lex.pptoken] Allow skipping non-preprocessing tokens via #if.
- CA-022: 5.5p1 [lex.pptoken] Add example for ill-formed non-preprocessing tokens.
- US 63-115: 16.3.3.3.4.1p01.2 [character.seq.general] Move [character.seq.general] to the core wording.
- US 189-304: 31.12.6.1, 31.12.6.5.6, 31.12.6.5.7, D.22.2 rename filesystem::path methods.
- US 5-018: 5 [lex] Define "whitespace character".
- Attendees:
- Braden Ganetsky
- Corentin Jabot
- Eddie Nolan
- Fraser Gordon
- Hubert Tong
- Jan Schultke
- Peter Bindels
- Robin Leroy
- Steve Downey
- Tom Honermann
- Victor Zverovich
- [ Editor's note: The SG16 chair has fallen far behind his obligations but will publish a proper summary of this meeting in due time. ]
- US 8-021: 5.5p1 [lex.pptoken] Allow skipping non-preprocessing tokens via #if:
- Poll 1: US 8: Recommend rejecting US 8 as evolutionary; the standard is intentional in specifying these preprocessing tokens as ill-formed.
- Attendees: 11 (one abstention)
SF F N A SA 5 4 1 0 0 - Strong consensus.
- Attendees: 11 (one abstention)
- Poll 1: US 8: Recommend rejecting US 8 as evolutionary; the standard is intentional in specifying these preprocessing tokens as ill-formed.
- CA-022: 5.5p1 [lex.pptoken] Add example for ill-formed non-preprocessing tokens:
- Poll 2: CA-22: Recommend accepting CA-22.
- Attendees: 11 (one abstention)
SF F N A SA 5 4 1 0 0 - Strong consensus.
- Attendees: 11 (one abstention)
- Poll 2: CA-22: Recommend accepting CA-22.
- US 63-115: 16.3.3.3.4.1p01.2 [character.seq.general] Move [character.seq.general] to the core wording:
- Poll 3: US 63: Recommend rejecting US 63; the execution character sets are not relevant to lexing and depend on library concepts such as locale.
- Attendees: 11 (one abstention)
SF F N A SA 8 1 0 0 0 - Unanimous consensus.
- Attendees: 11 (one abstention)
- Poll 3: US 63: Recommend rejecting US 63; the execution character sets are not relevant to lexing and depend on library concepts such as locale.
- US 189-304: 31.12.6.1, 31.12.6.5.6, 31.12.6.5.7, D.22.2 rename filesystem::path methods:
- Discussion started, but not concluded due to lack of time.
- US 5-018: 5 [lex] Define "whitespace character":
- Not discussed due to lack of time.
- P3733R0: More named universal character escapes.
- P3695R1: Deprecate implicit conversions between Unicode character types.
- P3688R3: ASCII character utilities.
- Attendees:
- Braden Ganetsky
- Eddie Nolan
- Hubert Tong
- Jan Schultke
- Jens Maurer
- Peter Bindels
- Robin Leroy
- Steve Downey
- Tom Honermann
- Victor Zverovich
- [ Editor's note: The SG16 chair has fallen far behind his obligations but will publish a proper summary of this meeting in due time. ]
- P3733R0: More named universal character escapes:
- Poll 1: P3733R0: Forward to EWG with a recommendation to adopt this feature as a defect report.
- Attendees: 10
SF F N A SA 7 3 0 0 0 - Unanimous consensus.
- Attendees: 10
- Poll 1: P3733R0: Forward to EWG with a recommendation to adopt this feature as a defect report.
- P3695R1: Deprecate implicit conversions between Unicode character types:
- Poll 2: P3695R1: Recommend deprecating conversions between char and the charN_t types.
- Attendees: 10
- No objection to unanimous dissent.
- Poll 3: P3695R1: Recommend deprecating conversions between char8_t and wchar_t.
- Attendees: 10
- No objection to unanimous consent.
- Poll 4: P3695R1: Recommend deprecating conversions between char16_t and char32_t.
- Attendees: 10
SF F N A SA 0 0 3 7 0 - Consensus against.
- Attendees: 10
- Poll 2: P3695R1: Recommend deprecating conversions between char and the charN_t types.
- P3688R3: ASCII character utilities:
- Not discussed due to lack of time.
- P3681R0: char_traits: Stop the bleeding!.
- P3672R0: On Windows, Systems APIs, Text Encodings, and Pragmatism.
- Attendees:
- Braden Ganetsky
- Corentin Jabot
- Eddie Nolan
- Fraser Gordon
- Hubert Tong
- Jan Schultke
- Jens Maurer
- Marco Foco
- Peter Bindels
- Tom Honermann
- Victor Zverovich
- [ Editor's note: The SG16 chair has fallen far behind his obligations but will publish a proper summary of this meeting in due time. ]
- P3681R0: char_traits: Stop the bleeding!:
- Poll 1: P3681R0: Deprecate use of types other than std::char_traits specializations for
the Traits template argument when CharT is a core language character type.
- Attendees: 11
SF F N A SA 5 3 1 1 1 - SA: We shouldn't deprecate code that works according to its intent due to preferences among committee members.
- A: We should't break existing code that works as intended.
- Consensus in favor.
- Attendees: 11
- Poll 1: P3681R0: Deprecate use of types other than std::char_traits specializations for
the Traits template argument when CharT is a core language character type.
- P3672R0: On Windows, Systems APIs, Text Encodings, and Pragmatism:
- Not discussed due to lack of time.
- LWG issue 4090: Underspecified use of locale facets for locale-dependent std::format.
- P3681R0: char_traits: Stop the bleeding!.
- Attendees:
- Braden Ganetsky
- Eddie Nolan
- Fraser Gordon
- Peter Bindels
- Steve Downey
- Tom Honermann
- Victor Zverovich
- [ Editor's note: The SG16 chair has fallen far behind his obligations but will publish a proper summary of this meeting in due time. ]
- LWG issue 4090: Underspecified use of locale facets for locale-dependent std::format:
- Poll 1: LWG 4090: Adopt Victor's suggested wording as the proposed resolution
- Attendees: 7
- No objection to unanimous consent.
- P3681R0: char_traits: Stop the bleeding!:
- Not discussed; author not present due to failure of the chair to properly coordinate.
- LWG issue 4070: Transcoding by std::formatter<std::filesystem::path>.
- LWG issue 4090: Underspecified use of locale facets for locale-dependent std::format.
- P3677R0: Preserving LC_CTYPE at program start for UTF-8 locales.
- Attendees:
- Braden Ganetsky
- Corentin Jabot
- Eddie Nolan
- Peter Bindels
- Robin Leroy
- Tom Honermann
- Victor Zverovich
- [ Editor's note: The SG16 chair has fallen far behind his obligations but will publish a proper summary of this meeting in due time. ]
- LWG issue 4070: Transcoding by std::formatter<std::filesystem::path>:
- POLL 1: Adopt the suggested replacement in place of the proposed resolution modification to
[fs.path.fmtr.funcs], retain the modification to the index of implementation-defined behavior,
and forward to LWG.
- Attendees: 7
- No objection to unanimous consent.
- POLL 1: Adopt the suggested replacement in place of the proposed resolution modification to
[fs.path.fmtr.funcs], retain the modification to the index of implementation-defined behavior,
and forward to LWG.
- LWG issue 4090: Underspecified use of locale facets for locale-dependent std::format:
- P3677R0: Preserving LC_CTYPE at program start for UTF-8 locales:
- POLL 2: Encourage WG14 to adopt P3677R0/N3539.
- Attendees: 6 (1 abstention)
SF F N A SA 4 1 0 0 0 - Strong consensus.
- Attendees: 6 (1 abstention)
- POLL 2: Encourage WG14 to adopt P3677R0/N3539.
- P2843R2: Preprocessing is never undefined.
- LWG issue 4070: Transcoding by std::formatter<std::filesystem::path>.
- LWG issue 4090: Underspecified use of locale facets for locale-dependent std::format.
- Attendees:
- Alisdair Meredith
- Braden Ganetsky
- Corentin Jabot
- Eddie Nolan
- Fraser Gordon
- Iain Sandoe
- Robin Leroy
- Tom Honermann
- Victor Zverovich
- [ Editor's note: The SG16 chair has fallen far behind his obligations but will publish a proper summary of this meeting in due time. ]
- P2843R2: Preprocessing is never undefined.
- LWG issue 4070: Transcoding by std::formatter<std::filesystem::path>.
- This issue was not discussed due to time constraints and lack of quorum.
- LWG issue 4090: Underspecified use of locale facets for locale-dependent std::format.
- This issue was not discussed due to time constraints and lack of quorum.
- CWG2843: Undated reference to Unicode makes C++ a moving target.
- P3727R0: Update Annex E onto Unicode 15.1.
- P3717R0: Update Annex E onto Unicode 16.
- Attendees:
- Braden Ganetsky
- Eddie Nolan
- Jens Maurer
- Peter Bindels
- Robin Leroy
- Steve Downey
- Tom Honermann
- [ Editor's note: The SG16 chair has fallen far behind his obligations but will publish a proper summary of this meeting in due time. ]
- CWG2843: Undated reference to Unicode makes C++ a moving target
P3727R0: Update Annex E onto Unicode 15.1
P3717R0: Update Annex E onto Unicode 16:- [ Editor's note: D3727R0 was the active paper under discussion at the telecon. The agenda and links used here reference P3727R0 since the links to the draft paper were ephemeral. The published document may differ from the reviewed draft revision. ]
- Poll 1: CWG 2843: Recommend adoption of the May 2025 proposed resolution.
- Attendees: 6 (one attendee had to leave early)
- No objection to unanimous consent.
- P3671R0: Clarifying the interaction of the literal and execution encodings.
- P3677R0: Preserving LC_CTYPE at program start for UTF-8 locales.
- Attendees:
- Corentin Jabot
- Eddie Nolan
- Hubert Tong
- Jens Maurer
- Steve Downey
- Tom Honermann
- Victor Zverovich
- [ Editor's note: The SG16 chair has fallen far behind his obligations but will publish a proper summary of this meeting in due time. ]
- P3671R0: Clarifying the interaction of the literal and execution encodings:
- P3677R0: Preserving LC_CTYPE at program start for UTF-8 locales:
- P3658R0: Adjust identifier following new Unicode recommendations.
- P3556R0: Input files are source files.
- P3657R0: A Grammar for Whitespace Characters.
- Attendees:
- Alisdair Meredith
- Braden Ganetsky
- Corentin Jabot
- Eddie Nolan
- Fraser Gordon
- Jens Maurer
- Peter Bindels
- Robin Leroy
- Steve Downey
- Tom Honermann
- [ Editor's note: The SG16 chair has fallen far behind his obligations but will publish a proper summary of this meeting in due time. ]
- P3658R0: Adjust identifier following new Unicode recommendations:
- Poll 1: P3658R0: Forward to EWG.
- Attendees: 9 (1 abstention)
SF F N A SA 6 2 0 0 0 - Strong consensus.
- Attendees: 9 (1 abstention)
- Poll 1: P3658R0: Forward to EWG.
- P3556R0: Input files are source files:
- P3657R0: A Grammar for Whitespace Characters:
- P3655R0: std::zstring_view.
- P2873R3: Remove Deprecated locale category facets for Unicode from C++26.
- Attendees:
- Braden Ganetsky
- Eddie Nolan
- Hana DusĂková
- Jens Maurer
- Jeremy Rifkin
- Peter Bindels
- Steve Downey
- Tom Honermann
- [ Editor's note: The SG16 chair has fallen far behind his obligations but will publish a proper summary of this meeting in due time. ]
- P3655R0: std::zstring_view:
- Poll 1: P3655R0: No objection to use of std::char_traits for consistency and compatibility with std::string_view.
- Attendees: 8 (no abstentions)
SF F N A SA 7 1 0 0 0 - Strong consensus.
- Attendees: 8 (no abstentions)
- Poll 2: P3655R0: Forward to LEWG with encouragement to add analysis of overload resolution and techniques to address ambiguity.
- Attendees: 8 (no abstentions)
SF F N A SA 8 0 0 0 0 - Strong consensus.
- Attendees: 8 (no abstentions)
- Poll 1: P3655R0: No objection to use of std::char_traits for consistency and compatibility with std::string_view.
- P2873R3: Remove Deprecated locale category facets for Unicode from C++26:
- Poll 3: P2873R3: Recommend to retain the deprecated std::codecvt<charN_t, char8_t> facets in C++26 based on observations of existing use.
- Attendees: 7 (no abstentions)
SF F N A SA 0 7 0 0 0 - Strong consensus.
- Attendees: 7 (no abstentions)
- Poll 3: P2873R3: Recommend to retain the deprecated std::codecvt<charN_t, char8_t> facets in C++26 based on observations of existing use.
- Attendees:
- Braden Ganetsky
- Corentin Jabot
- Eddie Nolan
- Hana DusĂková
- Jeremy Rifkin
- Jens Maurer
- Nevin Liber
- Peter Bindels
- Steve Downey
- Tiago Freire
- Tom Honermann
- Victor Zverovich
- [ Editor's note: The SG16 chair has fallen far behind his obligations but will publish a proper summary of this meeting in due time. ]
- P3474R1: std::arguments:
- [ Editor's note: D3474R1 was the active paper under discussion at the telecon. The agenda and links used here reference P3474R1 since the links to the draft paper were ephemeral. The published document may differ from the reviewed draft revision. ]
- P3655R0: std::zstring_view:
- Attendees:
- Barry Revzin
- Braden Ganetsky
- Eddie Nolan
- Fraser Gordon
- Jens Maurer
- Steve Downey
- Victor Zverovich
- Tom Honermann
- [ Editor's note: The SG16 chair has fallen far behind his obligations but will publish a proper summary of this meeting in due time. ]
- P3491R2: define_static_{string,object,array}:
- Poll 1: Forward P3491R2 to LWG/CWG with the understanding that LEWG has already forwarded this for inclusion in C++26.
- Attendees: 8
SF F N A SA 2 6 0 0 0 - Strong consensus.
- Attendees: 8
- Poll 1: Forward P3491R2 to LWG/CWG with the understanding that LEWG has already forwarded this for inclusion in C++26.
- P3391R0: constexpr std::format:
- Poll 2: Forward P3391R1 to LEWG.
- Attendees: 8
SF F N A SA 5 3 0 0 0 - Strong consensus.
- Attendees: 8
- Poll 2: Forward P3391R1 to LEWG.
- P3395R0: Formatting of std::error_code.
- P2873R2: Remove Deprecated locale category facets for Unicode from C++26.
- Attendees:
- Alisdair Meredith
- Corentin Jabot
- Eddie Nolan
- Hubert Tong
- Jens Maurer
- Robin Leroy
- Steve Downey
- Tom Honermann
- Victor Zverovich
- [ Editor's note: The SG16 chair has fallen far behind his obligations but will publish a proper summary of this meeting in due time. ]
- P3395R0: Formatting of std::error_code:
- Poll 1: Forward P3395R0 to LEWG amended to specify an encoding for
std::error_category::name()and for transcoding to be to UTF-8 if that matches the ordinary literal encoding and to an implementation-defined encoding otherwise.- Attendees: 9 (two abstentions)
SF F N A SA 1 6 0 0 0 - Strong consensus.
- Attendees: 9 (two abstentions)
- Poll 1: Forward P3395R0 to LEWG amended to specify an encoding for
- P2873R2: Remove Deprecated locale category facets for Unicode from C++26:
- Poll 2: Forward D2873R3 to LWG with the acknowledgement that LEWG has already forwarded it pending
SG16 approval.
- Attendees: 8 (two abstentions)
SF F N A SA 2 4 0 0 0 - Strong consensus.
- Attendees: 8 (two abstentions)
- Poll 2: Forward D2873R3 to LWG with the acknowledgement that LEWG has already forwarded it pending
SG16 approval.
- Attendees:
- Alisdair Meredith
- Bengt Gustafsson
- Braden Ganetsky
- Eddie Nolan
- Hubert Tong
- Jens Maurer
- Peter Bindels
- Steve Downey
- Tiago Freire
- Tom Honermann
- Victor Zverovich
- Ville Voutilainen
- [ Editor's note: The SG16 chair has fallen far behind his obligations but will publish a proper summary of this meeting in due time. ]
- P3263R0: Encoding annotated char:
- P3412R1: String interpolation:
- [ Editor's note: Bengt Gustafsson's presentation slides are avilable here. ]
- Attendees:
- Barry Revzin
- Braden Ganetsky
- Corentin Jabot
- Eddie Nolan
- Inbal Levi
- Robin Leroy
- Steve Downey
- Tom Honermann
- Victor Zverovich
- [ Editor's note: The SG16 chair has fallen far behind his obligations but will publish a proper summary of this meeting in due time. ]
- P3560R0: Error Handling in Reflection:
- Poll 1: P3560R0: std::meta::exception should support both char and char8_t-based construction and accessors.
- Attendees: 8 (one abstention)
SF F N A SA 1 2 3 1 0 - No consensus (too many neutrals).
- Attendees: 8 (one abstention)
- Poll 2: P3560R0: Forward to LEWG as is.
- Attendees: 9 (one abstention)
SF F N A SA 3 4 0 1 0 - Consensus.
- Attendees: 9 (one abstention)
- Poll 1: P3560R0: std::meta::exception should support both char and char8_t-based construction and accessors.
- P2758R4: Emitting messages at compile time:
- Poll 3: P2758R4: Add overloads that allow the message to be passed as std::u8string_view.
- Attendees: 9 (two abstentions)
SF F N A SA 4 2 1 0 0 - Consensus.
- Attendees: 9 (two abstentions)
- Poll 4: P2758R4: Add overloads that allow the message to be passed as std::wstring_view.
- Attendees: 9 (two abstention)
SF F N A SA 0 2 2 2 1 - No consensus.
- A/SA:
std::wstring_viewis mostly useful on Windows at run-time, we don't really need it at compile-time.
- Attendees: 9 (two abstention)
- Poll 5: P2758R4: Add overloads that allow the message to be passed as std::u16string_view and std::u32string_view.
- Attendees: 9 (two abstention)
SF F N A SA 0 1 5 1 0 - No consensus.
- Attendees: 9 (two abstention)
- Poll 6: P2758R4: Forward to LEWG modified to include std::u8string_view overloads.
- Attendees: 9 (two abstention)
SF F N A SA 3 4 0 0 0 - Strong consensus.
- Attendees: 9 (two abstention)
- Poll 3: P2758R4: Add overloads that allow the message to be passed as std::u8string_view.
- Decide on a meeting schedule for before/after the Hagenberg meeting.
- P2019R7: Thread attributes.
- Attendees:
- Braden Ganetsky
- Corentin Jabot
- Eddie Nolan
- Lauri Vasama
- Jens Maurer
- Peter Bindels
- Steve Downey
- Tom Honermann
- Victor Zverovich
- [ Editor's note: The SG16 chair has fallen far behind his obligations but will publish a proper summary of this meeting in due time. ]
- P2019R7: Thread attributes:
- Poll 1: P2019R7: Forward to LEWG modified to use the ordinary literal encoding for name hint.
- Attendees: 9 (one abstention)
SF F N A SA 4 3 1 0 0 - Strong consensus in favor.
- Attendees: 9 (one abstention)
- Poll 1: P2019R7: Forward to LEWG modified to use the ordinary literal encoding for name hint.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2024.md#november-6th-2024.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2024.md#october-23rd-2024.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2024.md#october-9th-2024.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2024.md#september-25th-2024.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2024.md#september-11th-2024.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2024.md#august-14th-2024.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2024.md#july-31st-2024.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2024.md#june-12th-2024.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2024.md#may-22nd-2024.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2024.md#may-8th-2024.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2024.md#april-24th-2024.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2024.md#april-10th-2024.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2024.md#march-13th-2024.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2024.md#february-21st-2024.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2024.md#february-7th-2024.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2024.md#january-24th-2024.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2024.md#january-10th-2024.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2023.md#november-29th-2023.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2023.md#october-25th-2023.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2023.md#october-11th-2023.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2023.md#september-27th-2023.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2023.md#september-13th-2023.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2023.md#august-23rd-2023.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2023.md#july-26th-2023.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2023.md#july-12th-2023.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2023.md#june-7th-2023.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2023.md#may-24th-2023.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2023.md#may-10th-2023.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2023.md#april-26th-2023.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2023.md#april-12th-2023.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2023.md#march-22nd-2023.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2023.md#march-8th-2023.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2023.md#february-22nd-2023.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2023.md#february-1st-2023.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2023.md#january-25th-2023.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2023.md#january-11th-2023.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2022.md#december-14th-2022.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2022.md#november-30th-2022.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2022.md#november-2nd-2022.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2022.md#october-19th-2022.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2022.md#october-12th-2022.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2022.md#september-28th-2022.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2022.md#september-14th-2022.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2022.md#august-24th-2022.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2022.md#july-27th-2022.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2022.md#june-22nd-2022.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2022.md#june-8th-2022.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2022.md#may-25th-2022.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2022.md#may-11th-2022.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2022.md#april-27th-2022.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2022.md#april-13th-2022.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2022.md#march-9th-2022.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2022.md#february-23rd-2022.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2022.md#february-9th-2022.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2022.md#january-26th-2022.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2022.md#january-12th-2022.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2021.md#december-15th-2021.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2021.md#december-1st-2021.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2021.md#november-17th-2021.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2021.md#november-3rd-2021.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2021.md#october-20th-2021.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2021.md#october-6th-2021.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2021.md#september-22nd-2021.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2021.md#september-8th-2021.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2021.md#august-25th-2021.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2021.md#july-28th-2021.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2021.md#july-14th-2021.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2021.md#june-23rd-2021.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2021.md#june-9th-2021.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2021.md#may-26th-2021.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2021.md#may-12th-2021.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2021.md#april-28th-2021.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2021.md#april-14th-2021.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2021.md#march-24th-2021.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2021.md#march-10th-2021.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2021.md#february-24th-2021.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2021.md#february-10th-2021.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2021.md#january-27th-2021.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2021.md#january-13th-2021.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2020.md#december-9th-2020.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2020.md#november-11th-2020.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2020.md#october-28th-2020.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2020.md#october-14th-2020.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2020.md#september-23rd-2020.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2020.md#september-9th-2020.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2020.md#august-26th-2020.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2020.md#august-12th-2020.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2020.md#july-22nd-2020.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2020.md#july-8th-2020.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2020.md#june-17th-2020.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2020.md#june-10th-2020.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2020.md#may-27th-2020.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2020.md#may-13th-2020.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2020.md#april-22nd-2020.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2020.md#april-8th-2020.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2020.md#march-25th-2020.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2020.md#march-11th-2020.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2020.md#february-26th-2020.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2020.md#february-5th-2020.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2020.md#january-22nd-2020.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2020.md#january-8th-2020.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2019.md#december-11th-2019.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2019.md#november-20th-2019.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2019.md#october-23rd-2019.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2019.md#october-9th-2019.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2019.md#september-25th-2019.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2019.md#september-4th-2019.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2019.md#august-21st-2019.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2019.md#july-31st-2019.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2019.md#june-26th-2019.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2019.md#june-12th-2019.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2019.md#may-22nd-2019.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2019.md#may-15th-2019.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2019.md#april-24th-2019.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2019.md#april-10th-2019.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2019.md#march-27th-2019.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2019.md#march-13th-2019.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2019.md#february-13th-2019.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2019.md#january-23rd-2019.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2019.md#january-9th-2019.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2018.md#december-19th-2018.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2018.md#december-5th-2018.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2018.md#october-17th-2018.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2018.md#october-3rd-2018.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2018.md#august-29th-2018.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2018.md#july-25th-2018.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2018.md#july-11th-2018.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2018.md#june-20th-2018.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2018.md#may-30th-2018.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2018.md#may-16th-2018.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2018.md#april-25th-2018.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2018.md#april-11th-2018.
See https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2018.md#march-28th-2018.
Meetings held by the informal std-text-wg working group prior to the formation of SG16 are available at: