W3C

– DRAFT –
Internationalization Working Group Teleconference

14 December 2023

Attendees

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

Meeting minutes

Agenda Review

addison: on webauthentication, and string-meta progress
… anything else?

Action Items

<addison> #61

<gb> Action 61 add css+xml for next call with css (see notes about ttml2) (on aphillips) due 2023-12-14

<addison> close #61

<gb> Closed action #61

addison: able to make that, closing

<addison> #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: still keeping

<addison> #33

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

<addison> #12

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

addison: updated old explainer
… keep going

<addison> #8

<gb> Action 8 Follow up on the status of Canvas and 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: see no activity from others

<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

xfq: Had discussions about i18n in email.

addison: I would like to see somebody from Universal Acceptance reacting as well.

xfq: I mentioned that. We are discussing what to say, what to do.

JcK: You can expect resistance to universal acceptance, like e.g., for emojis in domain names.

addison: But this is about the lhs, not the domain names.

JcK: There is a domain-name aspect as well.

addison: But not for HTML.

xfq: Other issues such as JS support.

JcK: With IDNA2003, the conversionis not unabiguously reversible.
… Solved in IDNA2008, but some parts still stuck on idna2003.

r12a: As of Jan 1, xfq will be the i18n lead.
… I will be around, working 2 days a week, including Thursdays.
… (I saw a film about a guy who got a bus pass and started traveling around England. I just got a bus pass too... :-( )
… But I'll have things to do.

addison: congrats xfq, congrats r12a!

Info Share

RADAR Review

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

addison: No new incoming request yet, but verifiable credentials is coming. They just did a self-review.

String-Meta revision

<addison> w3c/string-meta#81

addison: I'm doing a large reorganization, that why the big diff.
… You can start looking at this. I'd value your review.

xfq: What ois the objective of the refactoring?

addison: Instead of a new string type, we now recommend a @@ approach.
… I'm bringing those things in this doc.
… From an exploration document it is now about what you *should* do.
… I'd like to finish before the end of the year.
… We should do a wide review early next year.
… Did we do a wide review of something before?

r12a: I think we did.

addison: WebIDL is an example of single-language localizable text fields.
… WebIDL is maybe not the languagte for describing these things.

xfq: Maybe JSON.

addison: Yes, maybe JSON.

fun with [w3c/i18n-activity] rp.name, user.name and user.displayName length limit does not state binary encoding

<addison> #1800

<gb> Issue 1800 [not found]

<addison> w3c/webauthn#1994

<gb> Issue 1994 rp.name, user.name and user.displayName length limit does not state binary encoding (by emlun) [type:technical] [i18n-tracker]

addison: This is a new issue against webauthn.
… We commented long ago on truncating strings.
… webauthn doesn't actually say truncate to 64 utf-8 bytes, but to 64 bytes.
… It should say what encoding is used.

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

addison: In the horizontal tracker you can see that this isse has caused webauth to move to the top of the list.
… All of the issues are open.
… Apparently, this would be issues for webauthn3.
… But backwards-compat with webauthn 2...
… I think there isn't anything we can do about it.

<addison> w3c/i18n-activity#1394

<gb> Issue 1394 [Editorial] U+ notation is incorrect (by aphillips) [s:webauthn] [needs-resolution] [t:char_ranges]

addison: The last issue ^^ in their spec they have compatibility characters. I gave them the correct ones, btu they didn't fix it.

r12a: So what status is this spec?

<addison> https://www.w3.org/TR/webauthn-2/

addison: It is a Rec.

r12a: Did you talk to Philippe about that?

addison: I'll check in my archives what we told them.
… But not pleased to see a Rec with 7 open issues from us.

r12a: Seems some thing we can change in the Rec.

addison: Yes, errata.

xfq: It looks like the process works correctly. The issues were after the webauthn 3 first draft.

<addison> w3c/webauthn#1642

<gb> Issue 1642 Unicode "tag" characters are deprecated for language tagging (by aphillips) [type:technical] [i18n-needs-resolution] [@Risk]

w3c/transitions#315

<gb> CLOSED Issue 315 PR Request for Web Authentication:
 An API for accessing Public Key Credentials 
Level 2 (by YubicoDemo) [Entering PR] [Awaiting Publication]

addison: But the issue links to webauthn2.

xfq: Yes, but the issue was created when the spec was already a Rec.
… webauthn 3 is not CR yet.

addison: I can try to find the history.

addison: I will add a comment to issue 1800 and convert it to needs-resolution.

<addison> https://www.w3.org/TR/international-specs/#char_truncation

addison: Our text about truncation ^^ also doesn't mention a specific encoding.
… I will make a pull request for that.

ACTION: addison to reply to webauthn issue tracked by 1800 and add bp to specdev about encoding in trunction

<gb> Created action #62

Needs Attention issues for WG review (continued)

<addison> https://github.com/w3c/i18n-activity/issues?q=is%3Aissue+is%3Aopen+label%3Aneeds-attention

<addison> i18n-activity#258

<gb> Issue 258 Default styling for chinese annotations (by r12a) [close?] [s:css-ruby] [needs-attention] [i:inline-notes] [spec-type-issue] [clreq] [needs-resolution] [t:typ_ruby]

r12a: Didn't we talk about this last week? I think it is fine.

addison: OK, I'll close it. And 259, too.

<addison> i18n-activity#219

<gb> Issue 219 definition of character (by r12a) [close?] [s:svg] [needs-attention] [needs-resolution] [t:char_def]

<addison> w3c/svgwg#263

<gb> CLOSED Issue 263 definition of character (by r12a) [Text chapter] [SVG Core] [i18n-needs-resolution]

<addison> i18n-activity#606

<gb> Issue 606 Character counting in text 'x', 'y', 'dx', 'dy', and 'rotate' attributes (by r12a) [s:svg] [needs-resolution]

addison: I propose closing the issue 219, since we are tracking it in 606.

<addison> i18n-activity#506

<gb> Issue 506 UAs may have somewhat more liberal handling of the dir attribute than the spec does (by r12a) [tracker] [s:html] [needs-attention] [i:bidi-text] [spec-type-issue] [alreq] [hlreq]

<addison> whatwg/html#2769

<gb> Issue 2769 UAs may have somewhat more liberal handling of the dir attribute than the spec does (by bzbarsky) [good first issue] [topic: rendering] [i18n-tracker] [needs tests] [i18n-alreq] [i18n-hlreq]

addison: Hasn't been touched in a while.
… It's a tracker. Do want to make it needs-resolution?

r12a: Probably worth looking at what the current situation is. Some things in here are no longer the case.

xfq: I will look at it.

<addison> i18n-activity#404

<gb> Issue 404 Should generalYear (etc.) be gregorianYear (etc.)? (by aphillips) [close?] [s:owl-time] [needs-attention] [needs-resolution] [t:loc_time]

<addison> sdw#888

<gb> CLOSED Issue 888 should generalYear (etc) be gregorianYear (etc)? (by aphillips) [i18n-needs-resolution] [time]

xfq: I think we looked at this...

addison: They say they are prepared for other calendars, but in practice it is all Gregorian. Do we want to keep it open? Wait for their new review request?
… I can also take away the needs-attention label.

xfq: Should probably close it and wait for future review request.

AOB?

r12a: More infoshare:
… We talked about changing th title of the arabic layour reqs.

<Zakim> r12a, you wanted to discuss another info share - not urgent

r12a: I wasn't able to publish it, because the editors are no longer active.
… I talked to the Webmaster.
… There is a new rule that editors must be in the group.
… Way around is to make them authors, and keep the group members as editors.
… But we should now look at how we cite documents. We usually only cite the editors.
… And in this case it would look as if I'm the only editor.

addison: Can that be done by changing specref?

r12a: I think so.

<xfq> https://www.w3.org/International/alreq/

addison: Does it have to have an editor?

r12a: I think it does.

<xfq> https://www.w3.org/TR/jlreq/

xfq: The jlreq has even more editors who not active anymore.

r12a: I considered putting the names as ‘former editors’.

addison: Can also use the acknowledgements.
… Is this something to raise with Philippe? Is this just a specref issue? Should it pick up the authors?

ACTION: xfq to check on referencing authors in specref

<gb> Created action #63

Summary of action items

  1. addison to reply to webauthn issue tracked by 1800 and add bp to specdev about encoding in trunction
  2. xfq to check on referencing authors in specref
Minutes manually created (not a transcript), formatted by scribe.perl version 221 (Fri Jul 21 14:01:30 2023 UTC).