– DRAFT –
Internationalization Working Group Teleconference

Agenda Review

[checking agenda items]

Action Items

<addison> #106

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

addison: got responce from area director, will reply shortly

<addison> #104

<gb> Action 104 follow up on action#4 by writing an email (on aphillips) due 2024-06-13

<addison> #105

<gb> Action 105 Review https://deploy-preview-87--string-meta.netlify.app/#bp-consumers (on r12a) due 2024-06-13

<addison> #103

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

addison: you may noticed, new one is generated
… URL has been changed

addison: old URL redirected or sticked?

addison: seems sticked to old

xfq: old and new are both existing, different URLs

<addison> close #103

<gb> Closed issue #103

<addison> #102

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

<addison> i18n-activity#1620

<gb> Issue 1620 [focusgroup] i18n: should arrow key navigation follow text direction? (by w3cbot) [close?] [tracker] [needs-attention] [s:open-ui] [cg:open-ui]

<addison> close #102

<gb> Closed issue #102

<addison> #101

<gb> Action 101 research what if anything to do with dpub-pagination comments and old DPIG comments (on xfq) due 2024-05-30

xfq: guess, bring this as a topic in community group
… no one is editing nor understand this document within W3C community
… need to figure out that point
… could i18n take

addison: except one point, could be taken

r12a: lreq document targets not only web pages but ones like epub

addison: many of lreqs are script basis

xfq: no orthography notes for European language in latain?

<xfq> https://www.w3.org/TR/dpub-latinreq/

xfq: dpub Latin is in WD above

addison: we could ask them to link to ours lreq

<addison> action; addison: reply to pub folk about updating dpub-latinreq to point to our (new) document

<addison> close #101

<gb> Closed issue #101

ACTION: addison: reply to pub folk about updating dpub-latinreq to point to our (new) document

<gb> Created action #109

ACTION: r12a: create new latin lreq document to host dpig contents

<gb> Created action #110

<addison> #98

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

<addison> close #98

<gb> Closed issue #98

r12a: published

<addison> #96

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

addison: sent PR but not yet merged

<addison> close #96

<gb> Closed issue #96

addison: usually we wrote paragraph in one line, but was hard to comment on github
… style change

r12a: could be turned into ugly at later moment

<xfq> CSS specs use https://sembr.org/

addison: xfq pointed semantic breaks

xfq: personally prefer soft wrap, but could work both

addison: revisit little future

<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

xfq: still blocked by respec

<addison> #79

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

<addison> #78

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

addison: follow up call next week

<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

xfq: we also use github project for article, translation, gap-analysis pipelines
… will migrate all into new one

xfq: have updated links to article pipeline
… will update remaining

r12a: new character interface

RADAR Review

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

addison: no new incoming request

addison: agenda item for html-ruby extension

addison: filed a issue for device-posture

addison: manifest colleagues starts working on that, and call held
… will help on language definition and direction

<addison> i18n-activity#1872

<gb> Issue 1872 Proposal: Per-extension language preferences (by w3cbot) [pending] [tracker] [s:webextensions] [cg:webextensions]

<addison> i18n-activity#1871

<gb> Issue 1871 Align on properly formed language tags (by w3cbot) [pending] [tracker] [s:webextensions] [cg:webextensions]

xfq: they seem to have updates on these, will check

HTML Ruby Extensions review

<addison> i18n-activity#1869

<gb> Issue 1869 Various typos (by r12a) [pending] [non-I18N] [s:html-ruby-extensions] [wg:htmlwg]

r12a: this one already fixed

<addison> i18n-activity#1868

<gb> Issue 1868 Are line breaks in examples ok? (by r12a) [pending] [s:html-ruby-extensions] [wg:htmlwg]

r12a: we have changed examples to include line breaks

addison: there were discussion on CSS feature

xfq: most does not contain, but some, yes.

addison: any objections

<addison> i18n-activity#1867

<gb> Issue 1867 Mention that ruby is not just for educational use (by r12a) [pending] [s:html-ruby-extensions] [wg:htmlwg]

<addison> i18n-activity#1866

<gb> Issue 1866 Need to explicitly mention the default placement of ruby with 2 sets of annotations (by r12a) [pending] [s:html-ruby-extensions] [wg:htmlwg]

r12a: double sided ruby, what happens when CSS is applied

<addison> i18n-activity#1865

<gb> Issue 1865 Describe cases where jukugo ruby is not like group ruby (by r12a) [pending] [s:html-ruby-extensions] [wg:htmlwg]

r12a: jlreq sometimes tell jukugo is difficult
… wanted to leave enough space for examples

[questions on example 8]

<xfq> [Discussions on the line breaking behaviour of jukugo ruby]

r12a: would want to remove examples with changing font size, esp. Figure 3 Ruby sized at 60%

r12a: will write some text into this pending issue on this point

<addison> i18n-activity#1864

<gb> Issue 1864 Bopomofo ruby on the right in horizontal text is the norm, not just frequent (by r12a) [pending] [s:html-ruby-extensions] [wg:htmlwg]

addison: wording change for bopomofo position

<addison> i18n-activity#1863

<gb> Issue 1863 Add rb>rt>rb>rt example code to Example 1 (by r12a) [pending] [s:html-ruby-extensions] [wg:htmlwg]

r12a: it's for markup model, on rt and rb
… rb/rt/rb/rt model is effective
… and all three model should be shown here

Publishing Urdu gap analysis doc

r12a: urdu gap-analysis publishing

<addison> proposed: approve urdu gap analysis as FPWD group note

+1

<addison> +1

<xfq> <xfq> +1

<r12a> +1

RESOLUTION: publish urdu gap-analysis as FPWD

<r12a> https://www.w3.org/International/alreq/gap-analysis/arab-ur-gap

AOB?

[silent]