- From: W3C Calendar <noreply+calendar@w3.org>
- Date: Wed, 03 Aug 2022 15:05:40 +0000
- To: Internationalization Working Group <public-i18n-core@w3.org>
- Message-ID: <8e553e9705ecdbf65a57dd0ca9dcd03b@w3.org>
[View this event in your browser](https://www.w3.org/events/meetings/59c53b6b-4dcc-4d0e-9b1f-13949f19a6ac/20220804T150000) W3C Internationalization Working Group Teleconference Upcoming Confirmed ========================================================================= 04 August 2022, 15:00 -16:00 Europe/London Event is recurring weekly on Thursday, starting from 2022-08-04, until 2022-10-28 Location: https://www.w3.org/2017/09/i18n-meeting-info.html [ Internationalization Working Group ](https://www.w3.org/groups/wg/i18n-core/calendar) Agenda ------ #### Pending Issue Review <https://github.com/w3c/i18n-activity/issues?q=is%3Aissue+is%3Aopen+label%3Apending> #### String-Search Review of the various edits and discussion of next steps <https://w3c.github.io/string-search/> #### "Document Conventions" sections Review of Richard/Addison's changes to document conventions See for example: <https://w3c.github.io/string-search/#conventions> #### String-Meta Preparation for meeting with ECMA-402 and TC39 <https://github.com/w3c/i18n-discuss/blob/gh-pages/explainers/string-meta-explainer-402.md> #### Changes to vertical text article <https://w3c.github.io/i18n-drafts/articles/vertical-text/index.en.html> #### WebShare going to CR: check outstanding issue <https://github.com/w3c/transitions/issues/444#issuecomment-1199887209> <https://github.com/w3c/web-share/issues/152> <https://github.com/w3c/i18n-activity/issues/901> #### Whitespace best practices Specdev currently has: [https://deploy-preview-77--bp-i18n-specdev.netlify.app/#char\_whitespace](https://deploy-preview-77--bp-i18n-specdev.netlify.app/#char_whitespace) But this recommends 3 approaches, only 2 of which make it to the mustard, and it's still not clear which to use when. Other questions include: - do we really want to recommend the use of the `Z` property, especially given that it doesn't include obvious ASCII whitespace characters? Where did this recommendation come from? - why are RLM and LRM included as whitespace in some definitions, but not RLI, LRI, PDI, etc.? - - - - - - ### BE PREPARED Read the string-meta ECMA-402 explainer: <https://github.com/w3c/i18n-discuss/blob/gh-pages/explainers/string-meta-explainer-402.md> Also read string-meta. Review text about `auto`. ### REMINDER Getting too many of these notifications? Read [this](https://lists.w3.org/Archives/Member/member-i18n-core/2022Mar/0013.html) email from Richard on how to manage notifications. ### SCRIBE If you are set to scribe and cannot make it, please send regrets to the chair. Volunteers to act as scribe cheerfully accepted. Felix \[2022-07-07\] Fuqiao \[2022-07-14\] Atsushi \[2022-07-21\] Bert \[2022-07-28\] ### MEETING INFO <https://www.w3.org/2017/09/i18n-meeting-info.html> (Member Only Link) ### AGENDA (for agendabot) Topic: Agenda Review Topic: Action Items Topic: Info Share Topic: RADAR Review Topic: Pending Issue Review Topic: String-Search Topic: "Document Conventions" sections Topic: String-Meta Topic: Changes to vertical text article Topic: WebShare going to CR: check outstanding issue Topic: Whitespace best practices Topic: AOB? ### Chair's Link Farm <https://www.w3.org/International/track/actions/open> <https://github.com/w3c/i18n-request/projects/1> <https://github.com/w3c/i18n-activity/issues?q=is%3Aissue+is%3Aopen+label%3Apending> Joining Instructions -------------------- Instructions are restricted to meeting participants. You need to [ log in](https://www.w3.org/accounts/login?redirect_url=/events/meetings/59c53b6b-4dcc-4d0e-9b1f-13949f19a6ac/20220804T150000/edit) to see them. Participants ------------ ### Groups - [Internationalization Working Group](https://www.w3.org/groups/wg/i18n-core) ([View Calendar](https://www.w3.org/groups/wg/i18n-core/calendar)) Report feedback and issues on [ GitHub](https://github.com/w3c/calendar "W3C Calendar GitHub repository").
Attachments
- text/calendar attachment: event.ics
Received on Wednesday, 3 August 2022 15:05:42 UTC