Internationalization Working Group Teleconference

Meeting minutes

Agenda Review

Action Items

<addison> #137

<gb> Action 137 Create new meeting series in the W3C calendar (on xfq)

<addison> close #137

<gb> Closed issue #137

<addison> #135

addison: added action to xfq, and edited calendar event, so done #137

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

addison: will have chat next week for #135

<addison> #134

<gb> Action 134 file an issue about making input respect locale (on aphillips) due 2024-10-05

<addison> #131

<gb> Action 131 follow up on input-events action (on aphillips)

addison: #131 done

<addison> close #131

<gb> Closed issue #131

<addison> #128

<gb> Action 128 perform review of issues for inclusion in specdev (on xfq) due 2024-09-30

xfq: #128 not yet

<addison> #127

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

<addison> #125

<gb> Action 125 propose creating a UTR for text-emphasis skip if we can get help with maintain (on aphillips) due 2024-09-30

addison: #125 done, but wait for next CSS+i18n call for confirmation

<addison> #114

<gb> Action 114 read through i18n-activity#1659 and report on whether we're satisfied (on r12a) due 2024-08-22

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

addison: done some clean ups on repo, not see any other

Info Share

addison: did have unicode technical workshp, xfq was there
… presentation about string-meta, received good feedbacks
… linking with our groups
… also some conversation on message format there

xfq: good event, met with lots of people
… lightweight event, exchanged email with some for like joining to WG
… will discuss with them

addison: good for recruting for our activities, also I've chatted with several colleagues

xfq: chatted with credential colleagues on slack for review, and requesting review on FPWD
… guided them for review
… they may try to use FPWD one

addison: did some review, also they marked self review with tracker
… add some template to follow these?

ACTION: xfq: add text to the issue templates to clarify what to use when

<gb> Created action #138

xfq: would do

RADAR Review

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

xfq: can take EPUB 3.3

bert: will take media capabilities

atsushi: take picture in picture

addison: will take Vision document
… also already working on FedCM

addison: any waiting comment resolution?

Pending Issue Review

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

addison: some for FedCM spec

<addison> #1927

<gb> Issue 1927 not found

<addison> i18n-activity#1927

<gb> Issue 1927 Add a further explanation of `ltr` and `rtl` (based on ePub). (by w3cbot) [pending] [tracker] [s:rdf-concepts]

addison: this is PR from rdf colleagues, if no other comment, will mark as tracker and close

<addison> i18n-activity#1924

<gb> Issue 1924 ContactAddress 'region' inconsistencies (by w3cbot) [pending] [tracker] [s:contact-picker] [wg:das] [wg:webapps]

addison: some from contact picker

Issue 599

<addison> i18n-activity#599

<gb> Issue 599 highly detailed text in video content (by stpeter) [pending] [tracker] [s:mst-content-hint] [wg:webrtc] [Agenda+]

<addison> w3c/mst-content-hint#35

<gb> Issue 35 highly detailed text in video content (by aphillips) [Ready for PR] [i18n-tracker]

addison: propose to do as needs-resolution

xfq: +1

atsushi: +1

<r12a> +1

addison: will change label

Working with Time and Timezones as DNOTE?

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

<addison> The old doc: https://www.w3.org/TR/timezone

<addison> The new version: https://w3c.github.io/timezone

addison: timezone spec, find new version have large change

xfq: republish with note status?

r12a: draft or not

addison: do we want to publish v2 now, or draft?

r12a: state for no, long time elapsed

addison: republish with warning box in-line?

<Bert> (The Process doc says very little about (Draft) Notes, but it says ‘Both Notes and Draft Notes can be updated by republishing as a Note or Draft Note.’ without ‘respectively’, so I think they can be republised with either status.)

r12a: add action to go through and see any issue
… for addison

ACTION: addison: review old timezone note to ensure all content is present and accounted for

<gb> Created action #139

r12a: we should check before any publication

addison: will check for next week, and evaluate any missing point or correction

Specdev PRs

<addison> w3c/bp-i18n-specdev#145

<gb> Pull Request 145 Allow Ruby use in non-CJKM languages (by jyasskin) [Agenda+] [Best Practice] [normative]

addison: take a look at PRs

addison: #145, proposal to make text less CJKM restrictive on ruby use case

<gb> Issue 145 not found

addison: discussed before,,,

r12a: use in these language are prioritized, but what mean by this change?

xfq: prioritized part is not clear

<addison> Ruby markup in HTML is designed primarily for Chinese, <a data-cite="jlreq#usage_of_ruby">Japanese</a>, Korean, and Mongolian requirements. Note that ruby is also sometimes used to associate annotations with text in other languages. However, specifications should avoid proposing new uses for it.

addison: proposal above

r12a: like last sentence

addison: like pulling out from mustard? or something else?
… for middle part

[ruby for phonetic or not, another mechanism or?]

<r12a> https://r12a.github.io/blog/201708.html#20190304

xfq: what jeffery means was ruby display style is different from markup

<addison> Ruby markup in HTML is designed primarily for Chinese, <a data-cite="jlreq#usage_of_ruby">Japanese</a>, Korean, and Mongolian requirements. While sometimes used in other languages, such annotation generally should use other mechanisms. Specifications should avoid proposing new uses for Ruby.

r12a: was no answer for what happens when it is use with non-CJK

addison: how about proposal above again?

<addison> Annotation in other languages should use other mechanisms.

addison: propose change to this PR?

[all agreed]

ACTION: addison: reply to specdev 145 including proposal discussed in telecon

<gb> Created action #140

r12a: use word 'semantics'

<addison> w3c/bp-i18n-specdev#146

<gb> Pull Request 146 Fix examples (by aphillips)

<addison> https://github.com/w3c/bp-i18n-specdev/pull/146/files

addison: resolves comment from i18n activity in hebrew