Thanks for putting together meeting notes. All looks good with two minor comments:
* Russian console encoding is CP866, not CP868.
Ah, good catch! Thank you and fixed.
* I can confirm that there was a mistake in the Java experiment results in the slides presented at the meeting (sorry for that): Java didn't produce a correct UTF-8 file but a file that was in CP1251 with replacement characters. I see the notes already mention that which is great. The paper will contain the correct results and I've added validation code to make sure that the strings are actually in some UTF as discussed at the meeting.
Thank you for confirming that and no need to apologize of course!
As an aside, I've been doing some experiments with the Windows console and I'm now considerably less confident about the preference I previously expressed about wanting std::print() to transcode to the system/run-time encoding; at least some utilities are more apt to use the console encoding over the system/ACP encoding (or no encoding; just bytes) than I realized. I need to experiment more, but will start a new email thread with some details soon.
Happy New Year!
Happy New Year!Victor
On Mon, Dec 28, 2020 at 10:11 PM Tom Honermann via SG16 <email@example.com> wrote:
The summary for the SG16 meeting held December 9th, 2020 is now available. For those that attended, please review and suggest corrections:
No decisions were made at this meeting.
The next meeting is scheduled for Wednesday, January 13th, from 19:30-21:00 UTC (timezone conversion). The draft agenda is:
- P2246R0: Character encoding of diagnostic text
- And companion paper: WG14 N2563: Character encoding of diagnostic text
- SG16, SG22, and WG14 coordination.
- Priority and owners for SG16's open WG14 issues
- WG14 N2620: Restartable and Non-Restartable Functions for Efficient Character Conversions | r4
Discussion of coordination with SG22 and WG14 is expected to be short; perhaps 15 minutes. Please review the SG16 open issues tagged as WG14 ahead of time and consider whether you can offer assistance moving them along. In particular, I'd like to find owners for the WG14 equivalents of P1949 (C++ Identifier Syntax using Unicode Standard Annex 31) and P1041 (Make char16_t/char32_t string literals be UTF-16/32).
The remainder of the telecon will focus on socializing and reviewing JeanHeyd's work on WG14 N2620. This is a fairly long paper, so please set aside some time to read it. We won't delve into the proposed wording, but for the standardeze lovers out there, reading just the wording will give you a good sense of what the paper is about (but please try and read sections 2-4 as well).
Polls to forward P2246R0 to EWG are expected. Direction polls for WG14 N2620 may be taken.
For any new attendees: The meetings are video conferences conducted via Zoom. If you are planning to attend, please test your system by visiting https://zoom.us/test before the scheduled meeting time.
SG16 mailing list