– DRAFT –
Internationalization Working Group Teleconference

Agenda Review

Action Items

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

<addison> #110

<gb> Action 110 create new latin lreq document to host dpig contents (on r12a) due 2024-06-27

<addison> close #110

<gb> Closed issue #110

<addison> #108

<gb> 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: #110 done, close

<xfq> https://github.com/w3c/jlreq/discussions/436

<gb> Discussion 436 JLReq TF meeting notes 2024-6-25 (by kidayasuo)

<addison> atsushi: some discussion, kida-san had some comments last week

<addison> close #108

<gb> Closed issue #108

atsushi: #108 discussed and commented, close

<addison> #106

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

<addison> #93

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

<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> #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 in ~April (on aphillips) due 2024-03-07

xfq: #89, yes blocked

<addison> #78

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

<addison> #33

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

addison: covers gap, since it's comparison and diff, still not sending to INFRA

addison: #33, evergreen one

<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

[silent]

RADAR Review

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

addison: new incoming

bert: take vibration API

addison: anything else?

Pending Issue Review

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

<addison> i18n-activity#1879

<gb> Issue 1879 should default reset/submit button text and default summary text use node's language rather than being locale-specific? (by w3cbot) [pending] [tracker] [s:html]

addison: one interesting pending issue, above
… on HTML
… language of the document or locale

<addison> whatwg/html#10437

<gb> Issue 10437 should default reset/submit button text and default summary text use node's language rather than being locale-specific? (by dbaron) [topic: forms] [i18n-tracker]

addison: long standing one, on document language and browser

xfq: clreq discussed recently similar on date picker
… use language of user agent instead of the page
… This makes the internationalization state of this component independent of the internationalization state of the rest of the page.
… it's kind of similar item

addison: lots of controls are behaving as a part of content
… and sometimes it looks something strange
… whether to allow controls to have document language or set to locale of browser, is good question

xfq: author should be able to express override

addison: will chime in this

Publish FPWD of various layout requirements

<r12a> https://www.w3.org/International/typography/gap-analysis/language-matrix.html

r12a: what I am doing, starting from language matrix, supposed to list from gap-analysis document
… gap-analysis document changes over, and applied to matrix
… in addison, also 4/5 left to do
… for Latin, each of Latin languages are in separate gap-analysis document
… like 20 document for Latin
… not good for maintaining
… tried to improve Latin document
… contain all languages into one Latin gap-analysis document
… items are labelled
… gap-analysis and lreq documents are built from scripts for now
… much easier for maintenance

addison: can separate languages if we need?
… just thinking around

JcK: if it is one language to one script, its ok, but for language to multiple scripts, we need some

r12a: see some examples, French, Dutch, has different columns
… we can see issues per set of language or script
… data is in github issue, with label, and can be selected per target

[detail with arabic]

r12a: for publication, not publish urdu one, putting into nastaliq group
… Latin lreq and gap-analysis are for publication approval

r12a: so, Latin lreq, Latin gap-analysis, hebrew gap-analysis
… beng lreq
… hebrew lreq

<addison> proposed: publish as FPWD hebrew, latin, bengali, devanagari lreq and latin gap

r12a: devanagari lreq

<addison> +1

<Bert> +1

+1

<xfq> +1

<r12a> +1

<JcK> +0.5

RESOLUTION: publish Latn, Hebr, Beng, Deva LREQ and Latn gap analysis as FPWD

r12a: nastalq?

addison: arabic as parent and others as children are some complex

addison: how do you do if these are not separated

r12a: multiple lines in arabic part, columns will have different like for nastaliq

<Bert> (All the links in the matrix in the Arab section currently link to cher-gap.)

Normativity of i18n-glossary (redux)

addison: one issue filed to i18n-glossary for normative citing
… use glossary entry as term definition in normative part
… glossary already have a note on this, don't cite in normative, but copy text
… or refer Unicode or else
… i18n-glossary have composed list from various places
… reconsider these requests, and make some sort of rec-track or not, with evergreen CRS or something

addison: sometimes just tell them to copy

addison: want to say, document is not in rec-track, and cannot define normative term. if you want to define normativelly, do it yourself

[chat about normative/rec-track]

xfq: referncing non-normative text in normative part is not prohibited?

String-Meta: BPs for Consumers

addison: as you remember, we had guidance on consumers section

<addison> https://pr-preview.s3.amazonaws.com/aphillips/string-meta/pull/87.html#bp-consumers

addison: added edits, and result as above URL

addison: main change is in examples

Draft PRs

<addison> w3c/i18n-drafts#591

<gb> Pull Request 591 QA Native Direction (edits) (by aphillips)

addison: couple of articles in progress

<addison> https://deploy-preview-591--i18n-drafts.netlify.app/questions/qa-direction-native.html

addison: is this PR ready to merge?
… any objection?

xfq: feedback section?

addison: change link to the same as leave a comment

<addison> https://github.com/aphillips/i18n-drafts/blob/gh-pages/articles/language-negotiation/language-negotiation.md

addison: language negotiation part still in markdown
… please comment or give suggestion on this draft

xfq: having two article on this target is not good

addison: different target, doing the same

r12a: if you wanted to xxx, go yyy?

AOB?

[none]