– DRAFT –
Internationalization Working Group Teleconference

Agenda Review

Action Items

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

<addison> #112

<gb> Action 112 investigate changes to jlreq due to publication of jpan-lreq (on himorin) due 2024-07-25

<addison> atsushi: there's a question if there's a fundamental, there should be some answer

<addison> ... wonder if i should work on there

<addison> ... it's a philosophy issue

<r12a> w3c/jlreq#438 (comment)

<gb> Issue 438 Japanese Script Resources page (by r12a)

<addison> richard: responded to some questions from kida-san, responded ^

addison: how about jlreq to -lreq document

r12a: asked Kida-san about mapping bwtween jlreq documents and new -lreq documents

<addison> atsushi: there is some question about the scope between the two documents

<addison> ... want to maybe mirror structure of arabic or latin requirements

<addison> richard: they can do what they want; organization of original doc could maybe be improved

<addison> ... not need to adopt the 89 heads in lreq

<addison> addison: perhaps do a cross-over call; suspect just a misunderstanding

<addison> atsushi: seems like there ... there might be some ??? eastern languages support; could be the cause for ???

<addison> richard: made a long comment

<addison> atsushi: don't think comment will solve

<addison> richard: don't really "care"; they can do it their own way, do whatever they want; they _can_ use the structure but not required

<addison> ... treat langauges, not just scripts, and it works fine for all sorts of languages

<addison> ... up to kida-san whatever he wants to do, can link to sections in the document

<addison> ... it's one reason I split out jlreq docs from the other ones so we have

<addison> ... let's see what kida-san says; if further misunderstanding can follow up

<addison> #106

<gb> Action 106 write to ietf group about rfc9457 (on aphillips) due 2024-06-20

<addison> #90

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

addison: not finishwd #108

<gb> CLOSED Action 108 talk to jlreq about *default* behavior of line breaking with small kana (cf. csswg-drafts#10363) (on himorin) due 2024-06-25

<addison> #89

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

<addison> #79

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

addison: 4pm today for WHATWG call

<addison> close #79

<gb> Closed issue #79

<addison> #33

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

<addison> #8

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

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

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

Info Share

<r12a> https://github.com/w3c/i18n-activity/wiki/LReq-documents

r12a: now have lots of documents retires

RADAR Review

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

addison: two incoming requests

bert: looking into
… will take ACT Rules Format 1.1

atsushi: will do for IFT

Pending Issue Review

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

addison: incoming checklist for IFT, will be checked by atsushi
… xfq has pending one also[

This week's publications

<addison> https://lists.w3.org/Archives/Public/public-i18n-core/2024JulSep/0027.html

<r12a> grek-lreq https://w3c.github.io/eurlreq/grek

<r12a> gujr-lreq https://w3c.github.io/iip/gujr/

<r12a> taml-lreq https://w3c.github.io/iip/tamil/

<r12a> java-lreq https://w3c.github.io/sealreq/java/

r12a: published seveal

<r12a> https://w3c.github.io/amlreq/cher/index.html

<r12a> https://w3c.github.io/amlreq/cans/index.html

<r12a> https://w3c.github.io/amlreq/osge/index.html

r12a: mostly the same documents with some different links

<addison> PROPOSED: shall the nine new script-based lreq documents be approved for FPWD

<r12a> +1

<addison> +1

<Bert> +1

<atsushi_> +1

RESOLUTION: publish nine new script-based lreq documents mentioned in the minutes for FPWD

Prepare for WHATNOT call

<addison> whatwg/html#10496

<gb> Issue 10496 Upcoming WHATNOT meeting on 2024-07-25 (by past) [agenda+]

addison: upcoming whatnot call, pushed as above issue

<addison> whatwg/html#5799

<gb> Pull Request 5799 Fix #4562: add support for internationalized email addresses (by aphillips) [addition/proposal] [needs implementer interest] [topic: forms] [i18n-tracker] [agenda+]

addison: cleaned up that PR

addison: another topic on i18n-glossary and topics
… several weesk ago, we discussed on this
… our documents are non normative document, but most of referrering document does not need to do
… just to use definitions
… conflict with INFRA are code points related terminology
… and kinds of UTF-16 kinds of words
… code unit values and schema related
… they are not correctly , but they focues on usage within UTF016

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

RESOLVED

addison: open issue on directions as above issues

addison: another slot is right after this, so potential next slot should be next month

AOB?