W3C

– DRAFT –
Internationalization Working Group Teleconference

18 January 2024

Attendees

Present
Addison, Atsushi, Bert, Fuqiao, Richard
Regrets
JcK
Chair
Addison Phillips
Scribe
addison, Bert

Meeting minutes

Agenda Review

Action Items

gb, list open actions

<gb> Found actions in w3c/i18n-actions: #67, #66, #65, #64, #53, #47, #43, #35, #33, #18, #16, #12, #11, #8, #7, #4

#67

<gb> Action 67 add some comments to CSS #8511 (on r12a) due 2024-01-23

#66

<gb> Action 66 fix base direction vs. paragraph direction in string-meta (on aphillips) due 2024-01-18

#65

<gb> Action 65 contact Daniel and check the Ethiopic word boundary situation (on r12a) due 2023-12-26

#64

<gb> Action 64 Make list of HTML issues for February 22 call with WHATWG (on aphillips, xfq)

addison: See agenda item later.

#53

<gb> Action 53 come up with a set of information CSS want the i18n group to provide support for generic font families (on frivoal, fantasai) due 2023-11-01

#47

<gb> Action 47 make the CSSWG aware of Warichu (on frivoal) due 2023-10-04

#43

<gb> Action 43 pull together the list of win/mac/etc apis for setting base direction and/or language (on aphillips) due 2023-09-18

addison: Done in the issue.
… Starting to put a Q&A together.

#33

<gb> Action 33 Close issues marked `close?` or bring to WG for further review (on aphillips)

addison: Down to around 60

#12

<gb> Action 12 Upgrade/edit the explainer to address issues raised by google (on aphillips) due 18 Jul 2023

#8

<gb> Action 8 Follow up on the status of Canvas and formatted text (on aphillips) due 18 Jul 2023

#7

<gb> Action 7 Remind shepherds to tend to their awaiting comment resolutions (Evergreen) (on aphillips, xfq, himorin, r12a, bert-github) due 18 Jul 2023

#4

<gb> Action 4 Work with respec and bikeshed to provide the character markup template as easy-to-use markup (on r12a) due 27 Jul 2023

Info Share

RADAR Review

<r12a> https://typo.social/@ri/111764452166307113

Info Share

r12a: Made tool to search for characters or a regexp.
… This will find chars that browser search won't show.

https://github.com/w3c/i18n-request/projects/1

RADAR Review

addison: No incoming requests and nothing in review.

Pending Issue Review

addison: We have no pending issues.

I18N+CSS

<xfq> https://www.w3.org/2024/01/16-i18n-minutes.html

addison: There was an i18n-CSS call. Anything that came up, anything we need to do?

xfq: Nothing essential. Just some infoshare on HTML ruby document, about <rb> and <rbc>

ACTION: addison: follow up with florian about testing with kindle

<gb> Created action #68

<xfq> w3c/csswg-drafts#8511

<gb> Issue 8511 [css-text-4] text-autospace: what gets copied? (by fantasai) [css-text-4] [Agenda+] [i18n-tracker] [i18n-jlreq] [i18n-clreq] [i18n-eurlreq] [Agenda+ i18n]

xfq: Also discussed a few GitHib issues, on inserted spacing and whether it should be copied by copy&paste

addison: That is the issue r12a has an action for.

WHATWG + I18N Prep

https://github.com/w3c/i18n-activity/issues?q=is%3Aissue+is%3Aopen+label%3AAgenda%2BI18N%2BWHATWG

addison: Has labels on issues for agenda+ for different meetings.

https://github.com/w3c/i18n-activity/issues?q=is%3Aissue+is%3Aopen+label%3As%3Ahtml

addison: First issue is whether to add a named entity to HTML for narrow no-break space. HTML previously said no, but discussion goes on.
… If you have things to add...

xfq: Thanks for compiling that list. I'll see if we need to add more.
… Some issues like ruby could be labeled "needsresolution", although WhatWG is a different organization.

r12a: Wait with <rb> and <rtc>.

r12a: On 22nd, will WhatWG come to our meeting?

<xfq> w3c/vc-di-bbs#114

<gb> Issue 114 "XML Schema formatted date string" not specific enough (by aphillips) [i18n-needs-resolution]

addison: It's their regular meeting.

xfq: Reply I got on XML issue ^^ is that it is in a different spec, Data Integrity.
… If they indeed remove the duplicated text, we can close the issue.

addison: I will reply to the comment.

<xfq> w3c/i18n-glossary#62

xfq: I added a pull request with target=_blank for external links in the glossary.

r12a: addison's list with HTML issues is useful. Can we do the same with CSS issues? Can you select by labels with a wildcard, "css-*"?

https://w3c.github.io/horizontal-issue-tracker/index#

addison: In plh's comment tracker ^^, you can more easily see all CSS issues.
… xfq, would you be interested in finding a way to more easily group and sort all CSS issues?

xfq: I'll think about it.

https://github.com/w3c/i18n-activity/issues?q=is%3Aissue+is%3Aopen+css

<r12a> https://docs.github.com/en/search-github/searching-on-github/searching-issues-and-pull-requests#search-by-label

xfq: Maybe we can ask plh to let his bot add a special "css" label to all issues with css-* labels.

r12a: Or a label that identifies the WG. That could maybe be added automatically by the bot.

addison: I will ask plh.

ACTION: addison: ask PLH to add a WG feature to the gh bot

<gb> Created action #69

Summary of action items

  1. addison: follow up with florian about testing with kindle
  2. addison: ask PLH to add a WG feature to the gh bot
Minutes manually created (not a transcript), formatted by scribe.perl version 221 (Fri Jul 21 14:01:30 2023 UTC).

Diagnostics

Succeeded: s/the action/the issue/

Succeeded: s/rbc/rtc

No scribenick or scribe found. Guessed: addison

Maybe present: r12a, xfq

All speakers: addison, r12a, xfq

Active on IRC: addison, Bert, r12a, xfq