– DRAFT –
Internationalization Working Group Teleconference

Agenda Review

Action Items

<addison> https://github.com/w3c/i18n-actions/issues

<addison> #184

<gb> Action 184 reply to wcag issue with comment about doing a higher level of interaction and pre-review (on aphillips) due 2025-09-04

addison: I did that, I bvelieve.

<addison> #135

<gb> Action 135 follow up on XR issue 1393 about locale in session (on aphillips) due 2024-10-17

<addison> #127

addison: Still pending

<gb> Action 127 make a list of shared topics of interest between TG2 and W3C-I18N (on aphillips) due 2024-09-30

addison: Maybe stale

<addison> #33

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

<addison> #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

addison: Nobody reported any.

<addison> #4

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

addison: Still pending

Info Share

addison: Should maybe push on it

bert: GB bot has a small announcement
… if you mention a github issue in a topic line
… then it will expand that differently so it ends up in the minutes as a link
… rather than a separate line. makes the minutes more readable

Bert: Small enhancement for gb: topic lines can now contain issue references and those will become links.

r12a: Unicode release this week.

Review RADAR Review

<addison> https://github.com/orgs/w3c/projects/91/views/1

Joel: I can take the Geolocation review

<r12a> https://www.w3.org/International/i18n-activity/guidelines/review-instructions.html

addison: I'll take DID Resolution review.
… Screen Orientation is a fairly simple one, an update.

atsushi: I think I did taht in the past, I can do this one again.

Pending Issue Review

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

addison: Top two issues we'll do later. Next one when Fuqiao is back.

ICANN

r12a: I've been nominated to a Universal Acceptance WG.
… It's about international domain names, their use in email addresses and IDs, etc.
… ICANN is trying to work out what places they are used and what changes need to be made to have them supported everywhere.
… They try to get representatives from different stakeholders, big corp, open systems, standards, etc.
… About an hour every week to develop guidelines.

<r12a> https://w3c.github.io/i18n-activity/ua/icann_docs.html

r12a: ICANN tends to be a lot of talking and I'm not as familiar with it as I was. So I need your help. See link ^^

<r12a> w3c/universal-acceptance#2

<gb> Issue 2 not found

r12a: I'm trying to funnel info from WG to W3C and funnel W3C comments & questions to ICANN. That's where I need your help.
… (That issue is not public, looking into access.)
… Next week they will look at Open Source providers.

<r12a> Are there any specific standards ICANN org should contribute toward promoting UA adoption across applications and systems? Are there any emerging topics to consider for standards work for UA which ICANN org should consider? Which organizations should it collaborate with for the work? How should ICANN org prioritize its contribution to standards work related to UA?

r12a: In three weeks they'll talk about standards.
… See my questions ^^
… MAybe we can have a special session to talk about these things.

JcK: How useful is this WG?

r12a: It is time-limited. They seem to be trying.
… Output should be a set of guidelines, for what to do, how to approach people and orgs.

addison: And goal is to remove roadblocks to IDN adoption?

r12a: and also for email.

JcK: Historically, problem is they focused on low-hanging fruit.

addison: Email is a diverse thing, so many places it can go wrong.

JcK: So question is how seriously they will try this time around.

r12a: It seems different this time. They want expert advise. But only had 4 meetings so far.

JcK: I'm not giving up, just a bit sceptical...

r12a: Checking if some of you can see the issue.

Bert: I can see it.

AOB?

r12a: This week it became clear to me that Firefox now wraps Javanese text. Chrome and Safari already did, more or less.
… Note that Javanese doesn't have spaces between words.
… You wrap on syllables.
… Was raised by Norbert.
… Unicode now has algorithms for it.
… I made some tests, not yet for Balinese. And not yet announced.

Joel: Applies to all languages without spaces?

r12a: Some other languages without spaces wrap on word boundaries, need a dictionary.
… There are other southeast asian languages that behave like Javanese.

Richard looking at some language resources.

<r12a> Balinese, Batak, Brahmi, (Eastern) Cham, Dives Akuru, Grantha, Gurung Khema, Javanese, Kawi, Makasar, and Tulu Tigalari.

<r12a> https://www.w3.org/TR/java-gap/#issue40_line_breaking

r12a: Balinese, Batak, Brahmi, Granta, Javanese [see list ^^]