W3C

– DRAFT –
Internationalization WG Teleconference

24 August 2023

Attendees

Present
Addison, Atsushi, Fuqiao, JcK
Regrets
-
Chair
Addison Phillips
Scribe
addison, xfq

Meeting minutes

Agenda Review

Action Items

<addison> gb, list open actions

<gb> Found actions in w3c/i18n-actions: #35, #34, #33, #32, #18, #16, #15, #13, #12, #11, #10, #9, #8, #7, #6, #5, #4

<addison> #35?

<gb> Action 35 make the edits of CSS #5478 (on fantasai) due 2023-08-30

<addison> #34?

<gb> Action 34 write summary email showing path forward for WCAG 2.2 (on aphillips) due 2023-08-24

<addison> close #34

<addison> #33?

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

<gb> Closed action #34

<addison> #32?

<gb> Action 32 Approve the character markup PR (on fantasai) due 2023-08-17

addison: started #34

<addison> #18?

<gb> Action 18 Have informal explanation sessions about counter style translations with csswg members (on frivoal, fantasai)

<addison> #16?

<gb> Action 16 Keep track of line-breaking in Korean for i18n-discuss#11 (on aphillips)

<addison> #15?

<gb> Action 15 Get character styling into w3c stylesheet (on aphillips)

xfq: fantasai will look at the latest revision of the character markup PR

<addison> #13?

<gb> Action 13 Make sure generics are comfortable to read in the content language (on frivoal)

<addison> #12?

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

<addison> #11?

<gb> Action 11 Triage all css properties to determine which are logical, physical, or na by default (on frivoal)

<addison> #10?

<gb> Action 10 With florian triage richard's article into a list of potential generics (on fantasai)

<addison> #9?

<gb> Action 9 Follow up with ecma-402 on next steps and start tc39 discussion (on aphillips)

<addison> #8

<gb> Action 8 Create pr against canvas formatted text (on aphillips)

<addison> #7?

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

<addison> #6

<gb> Action 6 Check if unicode describes backwards deletion clearly and develop doc if not (on aphillips)

<addison> https://w3c.github.io/i18n-drafts/questions/qa-backwards-deletion.en.html

o/

addison: this is ready for review

<addison> #5

<gb> Action 5 Check into how to list questions at the top of a digest and/or improve lang enablement communications (on r12a)

addison: please send comments

<addison> #4

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

Info Share

RADAR Review

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

addison: no new incoming requests
… no items in review

xfq: First Public Working Draft published: Catalan Gap Analysis

WCAG 2.2

addison: I don't know if any of you guys know what the status of the formal objections from Japan
… or from China

ACTION: addison to follow up with murata-san about wcag status

<gb> Created action #36

addison: I'd like to avoid a formal objection if it's not going to make sense to have one

xfq: they're already sending PRs, we'll see how it goes

addison: I think we need to probably formally review them

I18N+CSS

https://www.w3.org/2023/08/23-i18n-minutes.html

w3c/csswg-drafts#8442

<addison> xfq: css working on proposal which will help with logical properties

<addison> xfq: css issue ^^ contains a mapping from kana to small kana. they want to upstream it to unicode

addison: I don't think they have a page that says here's the mapping
… but it might be in normalization
… because you also got the narrow to wide kana
… you have a whole bunch of that stuff

ACTION: xfq to investigate the small kana mapping and what if anything to recommend to unicode

<gb> Created action #37

<addison> xfq: should develop an agenda for tpac for joint meeting

<addison> ... don't have an agenda list specifically for tpac

ACTION: addison to propose i18n+css agenda for tpac

<gb> Created action #38

<addison> xfq: discussed character markup for styling. fantasai disagreed that there should not be a space between the code point and character name

<addison> ... she prefers a space

w3c/csswg-drafts#5478

name-like fields

w3c/vc-data-model#1252 (comment)

addison: we made a comment sometime ago about they have natural language text fields
… name and description
… and our comment on them was "you should have language and direction"
… "you should probably allow fore more than one of them"
… because people might want to localize the credential rather than having a separate credential in every language on earth
… Manu added some thing on how to use these fields
… but didn't mention localization
… so I made this comment and he addressed it

ACTION: addison to develop best practice guidelines for name-like fields

<gb> Created action #39

TPAC

https://github.com/w3c/i18n-actions/wiki/2023-TPAC-Planning

addison: I don't have a lot in our TPAC calendar yet
… I do need to go back and add a couple of things and I have an email to respond to from one of the groups

w3c/webappswg#91 (comment)

ACTION: addison to ping webappswg about a joint time on monday/tuesday at tpac

<gb> Created action #40

https://www.w3.org/groups/wg/webapps/

AOB?

w3c/i18n-glossary#52

w3c/i18n-glossary#35

addison: you're better off quoting them than forking

xfq: OK
… I'll update the PR

Summary of action items

  1. addison to follow up with murata-san about wcag status
  2. xfq to investigate the small kana mapping and what if anything to recommend to unicode
  3. addison to propose i18n+css agenda for tpac
  4. addison to develop best practice guidelines for name-like fields
  5. addison to ping webappswg about a joint time on monday/tuesday at tpac
Minutes manually created (not a transcript), formatted by scribe.perl version 221 (Fri Jul 21 14:01:30 2023 UTC).

Diagnostics

Maybe present: xfq

All speakers: addison, xfq

Active on IRC: addison, JcK, xfq