Event Updated: I18N ⇔ CSS

[View this event in your browser](https://www.w3.org/events/meetings/d737b1d9-bb00-4b14-9507-0338465ee8ed/20230926T220000/)

 I18N ⇔ CSS Upcoming Confirmed
==============================

 26 September 2023, 22:00 -23:00 America/Los\_Angeles

 Event is recurring monthly on Tuesday, but only the 4th instance of this set, starting from 2023-09-26, until 2023-11-29

[ Internationalization Working Group ](https://www.w3.org/groups/wg/i18n-core/calendar/)**What:** A meeting between some members of the I18N and CSS working groups to discuss open issues.

**When:** Monthly on the *fourth* Tuesday @ 2200 in the `America/Los_Angeles` time zone. (DST/Summer time will affect the wall time of this call for Beijing/Tokyo beginning in November: we'll review the schedule in the October call)

See [here](https://www.timeanddate.com/worldclock/meetingdetails.html?year=2023&month=6&day=5&hour=5&min=0&sec=0&p1=224&p2=248&p3=136&p4=179&p5=33&p6=101&p7=268) for time comparison

LocationTimeRegular ParticipantSan Francisco10 PMAddisonNew York1 AMElikaBeijing1 PMFuqiaoTokyo2 PMFlorian, AtsushiLondon6 AMRichard**Please send agenda+ items to public-i18n-core@**

 Agenda
------

**Topic: Agenda**
*Review the agenda*

**Topic: Action Items**
*Briefly review action items and progress on them*

**Topic: Info Share and Progress Reports**
*Any news of interest to the "other" group?*

**Topic: Review on-going issues**
*Review issues we've discussed in previous calls. We can break out topics from this agenda item as needed.*

- - - - - -

- TPAC fallout
- Status of `sideways-lr` and `sideways-rl` in Writing Modes
- Cutting Note (aka `warichu` in Japanese) is not supported
  
  
  - <https://github.com/w3c/clreq/issues/243>
  - This is a gap analysis issue. We raised a CSS issue to make sure you know it is "coming". We do not yet have full understanding of what Chinese needs.
- Status of "characters to skip for emphasis marks"
  
  
  - <https://github.com/w3c/csswg-drafts/issues/839>
  - *I can't tell if this was ever raised with Unicode. The CSS issue is closed with no spec changes apparently? Do we need to chase something here?*

*Note: this iteration was updated during TPAC and has new items that we think should be discussed in this smaller forum.*

Chair's Link Farm
-----------------

<https://www.w3.org/International/track/actions/open>
Needs Resolution issues: <https://github.com/w3c/i18n-activity/issues?q=is%3Aissue+is%3Aopen+css+label%3Aneeds-resolution> (16 of these)
Tracker issues: <https://github.com/w3c/i18n-activity/issues?q=is%3Aissue+is%3Aopen+css+label%3Atracker> (150 of these)

 Joining Instructions
--------------------

 Instructions are restricted to meeting participants. You need to [ log in](https://auth.w3.org/?url=https%3A%2F%2Fwww.w3.org%2Fevents%2Fmeetings%2Fd737b1d9-bb00-4b14-9507-0338465ee8ed%2F%3FrecurrenceId%3D20230926T220000) to see them.

 Participants
------------

### Organizers

- Elika Etemad
- Richard Ishida
- Addison Phillips
- Florian Rivoal
- Fuqiao Xue

### Groups

- [Internationalization Working Group](https://www.w3.org/groups/wg/i18n-core/) ([View Calendar](https://www.w3.org/groups/wg/i18n-core/calendar/))

### Invitees

- Rossen Atanassov
- Atsushi Shimono
- Alan Stearns

 Report feedback and issues on [ GitHub](https://github.com/w3c/calendar "W3C Calendar GitHub repository").