C++ Logo

SG16

Advanced search

Subject: Re: [SG16-Unicode] Draft SG16 direction paper
From: Tom Honermann (tom_at_[hidden])
Date: 2018-10-08 00:07:53


The final paper has been submitted. Many thanks to JeanHeyd for
converting it to Bikeshed!  It's much easier on the eyes now :)
- https://rawgit.com/sg16-unicode/sg16/master/papers/p1238r0.html

Tom.

On 10/07/2018 01:35 AM, Tom Honermann wrote:
> Another updated draft has been posted.  This completes my planned changes.
>
> Changes include:
> - Added additional author names for those that explicitly consented.
> - Added some discussion to the direction section regarding interaction
> of char8_t (and char16_t) to existing code.
> - Added an acknowledgement section.
> - Added references.
>
> I'll hold off on submitting this until tomorrow evening.
>
> Tom.
>
> On 10/06/2018 03:47 AM, Tom Honermann wrote:
>> An updated draft of the direction paper (now designated P1238) is
>> available in our github repo:
>> - https://github.com/sg16-unicode/sg16/tree/master/papers
>> - (viewable link)
>> https://rawgit.com/sg16-unicode/sg16/master/papers/d1238r0.html
>>
>> I've incorporated some, but not all, of the feedback from the meeting
>> on Wednesday:
>> - Added timeline information and clarified what is and is not
>> targeting C++20.
>> - Added some more discussion about implementation defined encodings
>> on Windows and z/OS.
>> - Poached some content from Steve's draft for the std::text section.
>> - Added a brief mention of std::locale in the generic interface section.
>> - Other misc fixups and re-wordings.
>>
>> I have not yet addressed discussion surrounding char8_t, but plan to
>> do so.
>>
>> Zach, in the meeting, you expressed some concern regarding the
>> generic interfaces and support of segmented text.  My notes from the
>> meeting aren't great regarding this and I'm afraid I'm not clear on
>> what you would like to see updated.  Can you offer a suggestion?
>>
>> Tom.
>>
>> On 10/03/2018 01:13 AM, Tom Honermann wrote:
>>> Enclosed is a draft of an SG16 direction paper to be discussed at
>>> our meeting tomorrow.  It's rough, but I think in sufficient shape
>>> for discussion.
>>>
>>> If we manage to get through that paper, we'll discuss the paper
>>> Steve just posted to our mailing list [1] and/or Markus' feedback
>>> paper [2].
>>>
>>> Tom.
>>>
>>> [1]: http://www.open-std.org/pipermail/unicode/2018-October/000144.html
>>> [2]:
>>> https://docs.google.com/document/d/1aI0mBcH-d3BLjs8NRHgGECbA320LGFgo-SrNJ6VnLKE/edit
>>>
>>>
>>>
>>> _______________________________________________
>>> SG16 Unicode mailing list
>>> Unicode_at_[hidden]
>>> http://www.open-std.org/mailman/listinfo/unicode
>>
>>
>>
>>
>> _______________________________________________
>> SG16 Unicode mailing list
>> Unicode_at_[hidden]
>> http://www.open-std.org/mailman/listinfo/unicode
>
>
>
>
> _______________________________________________
> SG16 Unicode mailing list
> Unicode_at_[hidden]
> http://www.open-std.org/mailman/listinfo/unicode



SG16 list run by herb.sutter at gmail.com