– DRAFT –
Internationalization Working Group Teleconference

Agenda Review

addison: got one additional item from r12a
… anything else?

Action Items

https://github.com/w3c/i18n-actions/issues

#103

<gb> Action 103 Migrate RADAR project (on aphillips)

#102

<gb> Action 102 ping alreq group to review our i18n-activity#1620 (on aphillips) due 2024-05-30

#100

<gb> Action 100 complain to plh about the new IRC tool (on aphillips) due 2024-05-30

close #100

<gb> Closed issue #100

r12a: irc client looks similar to webirc one

#99

<gb> Action 99 ping unicode about emphasis skip property (see our #530) (on aphillips) due 2024-05-28

#98

<gb> Action 98 fix code points examples in lang-bidi-use-cases (on r12a) due 2024-05-23

#96

<gb> Action 96 evaluate and where necessary fix i18n-glossary#76 (on r12a) due 2024-05-02

#93

<gb> Action 93 create best practices for consumers in string-meta (on aphillips) due 2024-04-25

#90

<gb> Action 90 steal some of henri's text from scroll-to-text-fragment for string-search (on aphillips) due 2024-04-18

#89

<gb> Action 89 update i18n specs to support dark mode (on xfq) due 2024-04-18

#87

<gb> Action 87 write to IETF ADs about RFC9457 with JcK's assistance (on aphillips) due 2024-04-04

addison: did while ago, and replied on thread and waiting for reply

#79

<gb> Action 79 schedule a follow-up call with WHATNOT in ~April (on aphillips) due 2024-03-07

#78

<gb> Action 78 compare infra to i18n-glossary export list and report back (on aphillips) due 2024-03-07

#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 for PR, and agenda later

#33

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

#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

addison: will write to them on this

ACTION: addison: follow up on action#4 by writing an email

<gb> Created action #104

Info Share

JcK: discussion going at IETF, on strings and characters
… language and direction information
… discussion for screen reader and a11y point of view
… explained in explainer, basically direction by user
… would bring recommendations from IETF and W3C

addison: email thread flows
… will probably suggest some discussion for reasonable resolution

r12a: talk at June 25th
… called bidi text, organized by Unicode

<r12a> Bidirectional Text (Part 1): The Basics of Bidi

<r12a> Date & Time Jun 25, 2024 04:00 PM London

r12a: you need to register from URL

<r12a> https://blog.unicode.org/2024/05/new-event-on-june-25-webinar-on.html

RADAR Review

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

addison: two new incoming

addison: will take device posture

atsushi: will take controlers documents

addison: under review, waiting for input
… web translation api, couple of pending issues

r12a: nothing for html ruby extension, but need to check around

addison: web principles and baggages are moved to completed, since all issues resolved

Pending Issue Review

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

i18n-activity#1856

<gb> Issue 1856 language tag handling needs more attention (by aphillips) [pending] [needs-resolution] [s:translation-api]

addison: language tag issue
… high level handling is #1856

<gb> Issue 1856 not found

+1

[all agrees]

i18n-activity#1855

<gb> Issue 1855 `canTranslate` values `no`, `readily` and `afterDownload` are not internationalized? (by aphillips) [pending] [needs-resolution] [s:translation-api]

r12a: in language tag examples, there are bad examples

addison: this is naming of values

r12a: no strong feelings.

addison: would have some conversations with this group

r12a: IETF question was for 14th Ul /04

Kashmiri/Uighur/Urdu FPWD

Perso-arabic Kashmiri https://w3c.github.io/alreq/arab-ks/index.html

Uighur https://w3c.github.io/alreq/arab-ug/index.html

Urdu https://w3c.github.io/alreq/arab-ur/index.html

publish arab-ks, arab-ug, and arab-ur as FPWD?

<r12a> +1

+1

jck: +1

String direction APIs

w3c/i18n-drafts#586

<gb> Pull Request 586 Publish a list of APIs for setting language and direction in native code (by aphillips)

String-Meta Consumer guidance PR

https://deploy-preview-87--string-meta.netlify.app/#bp-consumers

r12a: bdi, and isolation, problem you don't actually know without metadata
… you should have direction via bdi tag

You are reading <span id="title"></span>

addison: above example, you need to decorate using span for parts
… similar to message format one

addison: not like bdi, span wont isolate things

<r12a> getElementById('title') = `You are reading: <bdi>{$title}</bdi>`

r12a: default sinario to have bdi, but even if not you should have dir for changing direction

addison: depends on situation, you should have bdi, direction or auto

r12a: will read carefully

addison: discussed last week, and to have examples. and added some here

Kashmiri/Uighur/Urdu FPWD

r12a: plain text example is not identical to html one

+1 for FPWD

addison: back to FPWDs, and resolved

RESOLUTION: publish arab-ks, arab-ug, and arab-ur as FPWD

AOB?

ACTION: ri: Review https://deploy-preview-87--string-meta.netlify.app/#bp-consumers

<gb> Created action #105