Date: Tue, 8 Sep 2020 11:18:38 -0400
This is your friendly reminder that an SG16 telecon will be held
tomorrow, Wednesday September 9th, at 19:30 UTC (timezone conversion
<https://www.timeanddate.com/worldclock/converter.html?iso=20200909T193000&p1=1440&p2=tz_pt&p3=tz_mt&p4=tz_ct&p5=tz_et&p6=tz_cest>).
This meeting will be conducted via Zoom. To attend, visit
https://iso.zoom.us/j/8414530059 at the start of the meeting. Please
contact me privately if necessary for the meeting password.
The agenda is:
* P2178R1: Misc lexing and string handling improvements
<https://wg21.link/p2178r1>
o Discuss proposal 1: Mandating support for UTF-8 encoded source
files in phase 1
* P2194R0: The character set of C++ source code is Unicode
<https://isocpp.org/files/papers/P2194R0.pdf>
For the UTF-8 discussion, please take some time ahead of the meeting to
consider the following concerns:
* Migration strategies for non-UTF-8 projects to transition to UTF-8,
possibly incrementally.
* Migration strategies for implementors to transition system headers
to UTF-8, possibly incrementally.
* Support for differently encoded source files within a single
translation unit.
* Support for differently encoded primary source file within a single
project.
* Error handling for ill-formed UTF-8 sequences in each of:
o Comments
o String literals
o Elsewhere.
* Handling of BOMs.
* Whether an in-source encoding annotation is needed and what form is
should take:
o A magic comment (like Python)
o A pragma directive (like xlC)
A very rough draft of a paper discussing these concerns is available at
https://rawgit.com/tahonermann/sg16/master/papers/dyyyyr0-utf-8-source-files.html.
We will **not** discuss this paper at this meeting, but the Existing
Practice section
<https://rawgit.com/tahonermann/sg16/master/papers/dyyyyr0-utf-8-source-files.html#existing_practice>
may be informative (please ignore the rest of the draft for now).
No decisions will be made at this meeting, but direction polls are expected.
Tom.
tomorrow, Wednesday September 9th, at 19:30 UTC (timezone conversion
<https://www.timeanddate.com/worldclock/converter.html?iso=20200909T193000&p1=1440&p2=tz_pt&p3=tz_mt&p4=tz_ct&p5=tz_et&p6=tz_cest>).
This meeting will be conducted via Zoom. To attend, visit
https://iso.zoom.us/j/8414530059 at the start of the meeting. Please
contact me privately if necessary for the meeting password.
The agenda is:
* P2178R1: Misc lexing and string handling improvements
<https://wg21.link/p2178r1>
o Discuss proposal 1: Mandating support for UTF-8 encoded source
files in phase 1
* P2194R0: The character set of C++ source code is Unicode
<https://isocpp.org/files/papers/P2194R0.pdf>
For the UTF-8 discussion, please take some time ahead of the meeting to
consider the following concerns:
* Migration strategies for non-UTF-8 projects to transition to UTF-8,
possibly incrementally.
* Migration strategies for implementors to transition system headers
to UTF-8, possibly incrementally.
* Support for differently encoded source files within a single
translation unit.
* Support for differently encoded primary source file within a single
project.
* Error handling for ill-formed UTF-8 sequences in each of:
o Comments
o String literals
o Elsewhere.
* Handling of BOMs.
* Whether an in-source encoding annotation is needed and what form is
should take:
o A magic comment (like Python)
o A pragma directive (like xlC)
A very rough draft of a paper discussing these concerns is available at
https://rawgit.com/tahonermann/sg16/master/papers/dyyyyr0-utf-8-source-files.html.
We will **not** discuss this paper at this meeting, but the Existing
Practice section
<https://rawgit.com/tahonermann/sg16/master/papers/dyyyyr0-utf-8-source-files.html#existing_practice>
may be informative (please ignore the rest of the draft for now).
No decisions will be made at this meeting, but direction polls are expected.
Tom.
Received on 2020-09-08 10:22:12