BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Sabre//Sabre VObject 4.5.8//EN
CALSCALE:GREGORIAN
LAST-MODIFIED:20230329T193705Z
BEGIN:VTIMEZONE
TZID:Europe/London
X-MICROSOFT-CDO-TZID:1
BEGIN:STANDARD
DTSTART:20221030T010000
TZOFFSETFROM:+0100
TZOFFSETTO:+0000
TZNAME:GMT
END:STANDARD
BEGIN:STANDARD
DTSTART:20231029T010000
TZOFFSETFROM:+0100
TZOFFSETTO:+0000
TZNAME:GMT
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20230326T010000
TZOFFSETFROM:+0000
TZOFFSETTO:+0100
TZNAME:BST
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:dcb21af5-6796-49aa-9a5c-88b2454316a3
DTSTAMP:20230329T193705Z
SUMMARY:W3C Internationalization Working Group Teleconference
DTSTART;TZID=Europe/London:20230330T150000
DTEND;TZID=Europe/London:20230330T160000
DESCRIPTION:https://www.w3.org/events/meetings/dcb21af5-6796-49aa-9a5c-88b2
 454316a3/20230330T150000/\n\n***NOTE WELL*** This meeting is scheduled in 
 the `Europe/London` time zone. That time zone observes Daylight Savings/Su
 mmer Time. Your local time for this call may vary due to differences in yo
 ur local time zone's observation of DST/ST from that of the UK.\n\nAgenda\
 n\n#### BE PREPARED \nThings to do before the meeting:\n\n* _things to do 
 here_\n\n#### AGENDA\n\n**Topic: Agenda Review**\n_Send `agenda+` requests
  to the public-i18n-core@ list in advance of the meeting!_\n\n**Topic: Act
 ion Items**\n_Review of open action items from previous meetings_\n* [Trac
 kbot](https://www.w3.org/International/track/actions/open)\n\n**Topic: Inf
 o Share**\n_Share information of interest to the working group or pertaini
 ng to internationalization in general._\n\n**Topic: RADAR Review**\n_Time 
 to review new and on-going requests for specification review. Incoming req
 uests are assigned to shepherds in this part of the call._\n_In addition\,
  we review the status of specifications that have received comments. *Plea
 se review your issues and owned items in advance of the call*_\n* [RADAR](
 https://github.com/w3c/i18n-request/projects/1)\n\n**Topic: Pending Issue 
 Review**\n_Review of new and pending issues raised by working group member
 s or via the various bots._\n* [Pending Issues](https://github.com/w3c/i18
 n-activity/issues?q=is%3Aissue+is%3Aopen+label%3Apending)\n\n**Topic: Righ
 t-to-Left terminology**\n_Let's discuss `right-to-left` vs. `right to left
 `_\n\n* https://lists.w3.org/Archives/Member/member-i18n-core/2023Mar/0005
 .html\n\n**Topic: DOM Range advice?**\n_CSS Highlights accepted our commen
 t and are trying to make changes to address it. Have a look at my response
 ._\n\n* https://github.com/w3c/csswg-drafts/pull/8647\n\n**Topic: Discuss 
 guidance about bidi**\n_Richard [noted](https://github.com/w3c/bp-i18n-spe
 cdev/pull/89#discussion_r1152147281):_\n\n> Several things are unclear to 
 me here\, and rather than provide text suggestions that may be barking up 
 the wrong tree\, we should perhaps discuss during our telecon. Questions i
 nclude:\n> * do you mean bidrectional text or text that generally runs in 
 a particular direction (eg. RTL)? i suspect\, but i'm not sure\, that we a
 re talking solely about strings that contain bidirectional text within the
 m\, or about correctly displaying any string that is inserted into a targe
 t location by the consumer?\n> * if the latter\, we're focusing on what pr
 oducers need to do\, we should mention dirname or using other metadata\n> 
 Basically\, i think we need a little more clarity about the role of produc
 ers vs consumers\, and in-string direction vs how a string will be inserte
 d into a target location. It seems a little vague at the moment. The secti
 on title\, Concatenation of Strings\, doesn't make it sound like we're con
 cerned with string internal direction\, but rather strings being inserted 
 into the target location. The example shows one scenario that fits the sec
 tion title\, but the preceding text needs to be clearer before we get to t
 he example\, and needs to clarify whether we are also talking about string
 -internals.\n\n_This refers to the prose found in the new "string concaten
 ation" section [here](https://aphillips.github.io/bp-i18n-specdev/#strcat)
 _\n\n* https://github.com/w3c/bp-i18n-specdev/pull/89#discussion_r11521472
 81\n* https://aphillips.github.io/bp-i18n-specdev/#strcat\n\n**Topic: AOB?
 **\n\n---\n\n#### REMINDER \nGetting 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.\n\n\n#### SCRIBE
  \nIf you are set to scribe and cannot make it\, please send regrets to th
 e chair. Volunteers to act as scribe cheerfully accepted.\n\nFelix [2023-0
 2-23]\nFuqiao [2023-03-09]\nAtsushi [2023-03-16]\nBert [2023-03-23]\n\n###
 # Chair's Link Farm\nhttps://www.w3.org/International/track/actions/open\n
 https://github.com/w3c/i18n-request/projects/1\nhttps://github.com/w3c/i18
 n-activity/issues?q=is%3Aissue+is%3Aopen+label%3Apending
STATUS:CONFIRMED
CREATED:20230323T165726Z
LAST-MODIFIED:20230329T193705Z
SEQUENCE:9
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Internationalizati
 on Working Group:mailto:public-i18n-core@w3.org
LOCATION:Location: https://www.w3.org/2017/09/i18n-meeting-info.html
RECURRENCE-ID;TZID=Europe/London:20230330T150000
END:VEVENT
END:VCALENDAR