--
Steven R. Loomis
Code Hive Tx, LLC
https://codehivetx.us
> On Mar 9, 2022, at 12:33 PM, Tom Honermann via SG16 <sg16_at_[hidden]> wrote:
> 
> Thank you, Corentin!
> 
> On 3/9/22 5:01 AM, Corentin Jabot via SG16 wrote:
>> A few random comments that may be useful
>> A relatively new project, icu4x - aims to provide similar features to ICU while rethinking some of the fundamental design decisions (for example, ICU has a UTF16-first interface, which isn't optimal) https://github.com/unicode-org/icu4x <https://github.com/unicode-org/icu4x> 
>> Currency/Number/Date/Time formatting in ICU/Unicode/CLDR are significantly different from what std::locale can offer, and would deserve further consideration in that is is not "already provided by chrono"
> That's fair. I meant more that base facilities exist for these feature categories. I agree we don't have feature parity with ICU here.
>> In addition to ICU, ecma402 is worth considering - https://tc39.es/ecma402/ <https://tc39.es/ecma402/> and https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl <https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl> 
> Thank you. It looks like, at a very high level, ECMA 402 provides features that overlap with those provided by ICU though the details differ considerably. Does that sound right?
The ECMA 402 API is often implemented by ICU4C, currently. I would say that ECMA 402 has and is developing the high runner functionality used in both front end and server JavaScript. 
>> Case mapping seems to be missing from the document, and may be worth considering
> Good catch. It looks like that falls under the "Strings and Character Iteration" feature set within the ICU module list. I made a note in the doc.
> 
>> A lot of algorithms (casing, clusterization) have both locale dependant, and locale independent algorithms
>> A locale identifier object is certainly a prerequisite for further unicode locale work - https://unicode.org/reports/tr35/tr35.html#Unicode_locale_identifier <https://unicode.org/reports/tr35/tr35.html#Unicode_locale_identifier> https://unicode-org.github.io/icu4x-docs/doc/icu_locid/struct.Locale.html <https://unicode-org.github.io/icu4x-docs/doc/icu_locid/struct.Locale.html> 
> Yes. Locale work will be fundamentally required for complete support of some of the categories I marked as "yes". Perhaps that is an argument for making locale related work a higher priority; at least with regard to locale identification.
> 
It would be worth noting which services depend on which.
> Tom.
> 
>> 
>> Regards, 
>> Corentin
>> 
>> On Tue, Mar 8, 2022 at 10:07 PM Tom Honermann via SG16 <sg16_at_[hidden] <mailto:sg16_at_[hidden]>> wrote:
>> This is your friendly reminder that this telecon is taking place tomorrow.
>> 
>> If you haven't yet, please review the linked Google Doc <https://docs.google.com/document/d/1f-CLhYZIf_L0q1QBEqe2sVHyAofGx8Akt_xJKDGhcgA/edit?usp=sharing>. Please add comments; especially with regard to any feature sets that you would like to discuss during the telecon.
>> 
>> Tom.
>> 
>> On 3/7/22 12:23 AM, Tom Honermann via SG16 wrote:
>>> SG16 will hold a telecon on Wednesday, March 9th at 19:30 UTC (timezone conversion <https://www.timeanddate.com/worldclock/converter.html?iso=20220309T193000&p1=1440&p2=tz_pst&p3=tz_mst&p4=tz_cst&p5=tz_est&p6=tz_cet>).
>>> 
>>> The agenda is:
>>> 
>>> ICU features to consider for C++26
>>> During our last telecon <https://github.com/sg16-unicode/sg16-meetings#february-23rd-2022>, Jens suggested the possibility of a roadmap towards providing support for the ICU feature set in the C++ standard. To that end, I put together a Google Doc <https://docs.google.com/document/d/1f-CLhYZIf_L0q1QBEqe2sVHyAofGx8Akt_xJKDGhcgA/edit?usp=sharing> that lists categories of features that ICU provides. The doc contains a table in which I have pre-populated indications of which features I think might be reasonable for standardization in C++26. This is intended to be less of a roadmap and more a list of features for which papers are encouraged and that we would like to spend time on. Please feel free to edit the doc to add comments or challenge my yes, no, and maybe indications. The feature list is derived from the documented ICU Module List <https://unicode-org.github.io/icu-docs/apidoc/released/icu4c/#Module>. It may be useful to peruse the ICU Feature Comparison Chart <https://icu.unicode.org/charts/comparison> for additional features to add (I haven't done so yet due to time limitations). It is likely that I have misinterpreted what is provided by some of the feature categories so if you see something that surprises you, please speak up!
>>> 
>>> Tom.
>>> 
>>> 
>>> 
>> -- 
>> SG16 mailing list
>> SG16_at_[hidden] <mailto:SG16_at_[hidden]>
>> https://lists.isocpp.org/mailman/listinfo.cgi/sg16 <https://lists.isocpp.org/mailman/listinfo.cgi/sg16>
>> 
> -- 
> SG16 mailing list
> SG16_at_[hidden]
> https://lists.isocpp.org/mailman/listinfo.cgi/sg16