Date: Wed, 14 Aug 2019 22:16:48 -0400
The summary for the SG16 meeting held July 31st, 2019 is now available.
For those that attended, please review and suggest corrections:
- https://github.com/sg16-unicode/sg16-meetings#july-31st-2019
The next meeting is scheduled for Wednesday, August 21st, from
3:30-5:00pm EDT. An invitation (from invite_at_[hidden]
<mailto:invite_at_[hidden]>) has been sent to the mailing list and
prior attendees. The draft agenda is:
- Discuss P1108, "web_view". Our focus will be, unsurprisingly,
character encodings and the use of iostreams with (presumably) UTF-8 data.
- Goals for WG14 in Ithaca (October 21st-25th).
- Goals for Belfast (November 4th-9th).
- Discuss a few follow up items from P1689, "Format for describing
dependencies of source files", following discussion in SG15.
- Bikeshed "data". What do we call the code unit equivalent in path
names?
- Are we ok stating that JSON readers/writers are not allowed to
apply Unicode normalization?
- Are we ok with allowing a BOM (JSON doesn't permit one)?
- Is "execution character set" the right term for the run-time locale
dependent encoding used by the character classification and conversion
functions?
For any new attendees: The meetings are video conferences conducted via
BlueJeans. If you are planning to attend, please test your system by
visiting https://bluejeans.com/111 before the scheduled meeting time.
Tom.
For those that attended, please review and suggest corrections:
- https://github.com/sg16-unicode/sg16-meetings#july-31st-2019
The next meeting is scheduled for Wednesday, August 21st, from
3:30-5:00pm EDT. An invitation (from invite_at_[hidden]
<mailto:invite_at_[hidden]>) has been sent to the mailing list and
prior attendees. The draft agenda is:
- Discuss P1108, "web_view". Our focus will be, unsurprisingly,
character encodings and the use of iostreams with (presumably) UTF-8 data.
- Goals for WG14 in Ithaca (October 21st-25th).
- Goals for Belfast (November 4th-9th).
- Discuss a few follow up items from P1689, "Format for describing
dependencies of source files", following discussion in SG15.
- Bikeshed "data". What do we call the code unit equivalent in path
names?
- Are we ok stating that JSON readers/writers are not allowed to
apply Unicode normalization?
- Are we ok with allowing a BOM (JSON doesn't permit one)?
- Is "execution character set" the right term for the run-time locale
dependent encoding used by the character classification and conversion
functions?
For any new attendees: The meetings are video conferences conducted via
BlueJeans. If you are planning to attend, please test your system by
visiting https://bluejeans.com/111 before the scheduled meeting time.
Tom.
Received on 2019-08-15 04:16:57