W3C

– DRAFT –
Internationalization Working Group Teleconference

15 December 2022

Attendees

Present
Addison, Atsushi, Bert, David, Felix, Fuqiao, JcK, Richard
Regrets
-
Chair
Addison Phillips
Scribe
atsushi

Meeting minutes

<addison> trackbot, prepare teleconference

Agenda Review

addison: anything else for today?

[silent]

Action Items

<addison> https://www.w3.org/International/track/actions/open

addison: 1164, as agenda item

addison: 1183, no reply yet

addison: 1200, will fix date

addison: 1216, will close on merged

addison: 1221, will be on board Tue

addison: also for 1222

addison: 1224, chatted little bit, will continue new year

r12a: 1226, Thai one last week, Tamil posted

addison: 1228, agenda item

Info Share

addison: this is the last call for 2022
… few weeks without meeting

addison: message format WG in Unicode, lacking chair, and I will do

r12a: interesting to moving into mastdon, will continue annoucements on twitter although

<r12a> https://w3c.social/@webi18n

<r12a> (https://typo.social/@ri)

RADAR Review

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

addison: no new

addison: multi screen window, will finish in Jan

JLTF proposed charter

<addison> https://lists.w3.org/Archives/Member/member-i18n-core/2022Dec/0006.html

atsushi: two major changes to add new deliverables

<addison> https://htmlpreview.github.io/?https://raw.githubusercontent.com/himorin/jlreq/charter-2023/charter/index.html

r12a: seems good
… task force charters are for their participants, and no formal but good to bring into WG. no need to get permission from IG

atsushi: will merge the PR, and github page will be updated

Specdev PRs

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

<addison> https://deploy-preview-86--bp-i18n-specdev.netlify.app/

<addison> https://deploy-preview-86--bp-i18n-specdev.netlify.app/#char_ref

addsion: first one, PR 86, in responce to last week agenda item
… the biggest question is whether to add one item from list

r12a: to fill with 0 for U+XXXX

addison: filling seems to be common these days

xfq: not including style ones?
… adding styles into /TR/ one?

addison: included into the PR, believe

r12a: I think to use small caps rather than upper case

<xfq> https://www.w3.org/International/i18n-activity/guidelines/editing#inline

r12a: the reason, is to apply always different styles

[styling discussions, non-us-ascii]

addison: will remove a sentence and merge this

<addison> change 'interefere' to 'interfere'

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

<addison> https://deploy-preview-82--bp-i18n-specdev.netlify.app/#char_string

addison: PR 82, looking again, first part is defining string

<addison> https://deploy-preview-82--bp-i18n-specdev.netlify.app/#personal_name_examples

addison: second part is incoorporating CLDR
… having phone call with them

addison: take up CLDR stuff?

r12a: or submit all item in table into CLDR, and change text?

addison: how about string section?

[silent]

addison: merge this

String-Search PRs

<addison> https://github.com/w3c/string-search/pull/14

<addison> https://deploy-preview-14--string-search-w3c.netlify.app/

addison: output from indic script
… included examples

r12a: we've reached at the point of research, and happy to publish this

addison: never published yet?

r12a: not see in /TR/ list

addison: will merge and prepare for publish

[no other comment]

WOT Discussions

<addison> https://github.com/w3c/wot-discovery/issues/316

addison: had some discussions with WoT colleagues
… issue 316 is for sorting algorithm

<addison> https://github.com/w3c/wot-thing-description/issues/1750

addison: long thread that no direction specified
… did a little research incl. CLDR, and see ICU implementation for hard coded one
… question is whether to import this into our one or not

r12a: two item, you don't need to know the direction after the last character, on Arabic application like title it goes left hand side for like dots

<addison> https://w3c.github.io/i18n-discuss/explainers/bidi-html-demo.html?text=title:%20%5Cu0627%5Cu0644%5Cu0628%5Cu062d%5Cu0631%5Cu064a%5Cu0646%20(123456)%20%5Cu0645%5Cu0635%5Cu0631%20%5Cu0627%5Cu0644%5Cu0643%5Cu0648%5Cu064a%5Cu062a...

<addison> https://w3c.github.io/i18n-discuss/explainers/bidi-html-demo.html?text=title:%20%5Cu0627%5Cu0644%5Cu0628%5Cu062d%5Cu0631%5Cu064a%5Cu0646%20(123456)%20%5Cu0645%5Cu0635%5Cu0631%20%5Cu0627%5Cu0644%5Cu0643%5Cu0648%5Cu064a%5Cu062a...

r12a: for control display, elipses could follow long English text

addison: examples above

<addison> https://w3c.github.io/i18n-discuss/explainers/bidi-html-demo.html?text=title:\u0627\u0644\u0628\u062d\u0631\u064a\u0646:%20HTML%20and%20CSS...

<addison> https://w3c.github.io/i18n-discuss/explainers/bidi-html-demo.html?text=\u0627\u0644\u0628\u062d\u0631\u064a\u0646: HTML and CSS...

[appearance of ellipses]

r12a: consult with cSS and also ask some RTL people also

addison: couple of things, discussion on language and tag, do some more research on this display area

<r12a> HTML and CSS مصر الكويتمصر الكويتمصر الكويتمصر الكويت..

r12a: paste above into your textbox
… shrink window and you will have first few words, question is where to put ellipses

<addison> https://w3c.github.io/i18n-discuss/explainers/bidi-html-demo.html?text=\u0627\u0644\u0628\u062d\u0631\u064a\u0646%20\u0645\u0635\u0631%20\u0627\u0644\u0643\u0648\u064a\u062a!

[discussion on whether elipses are control or in text]

<addison> close action-1164

<trackbot> Closed action-1164.

<addison> close action-1228

<trackbot> Closed action-1228.

<addison> close action-1226

<trackbot> Closed action-1226.

Minutes manually created (not a transcript), formatted by scribe.perl version 196 (Thu Oct 27 17:06:44 2022 UTC).

Diagnostics

Succeeded: s/elippses/elipses/

Succeeded: s/shlink/shrink/

No scribenick or scribe found. Guessed: atsushi

Maybe present: addsion, r12a, xfq

All speakers: addison, addsion, atsushi, r12a, xfq

Active on IRC: addison, atsushi, fsasaki, JcK, r12a, xfq