Meeting minutes
<trackbot> Please see <http://
REMINDER that the dial in has changed
<JcK> And the W3C site is not letting me log in this morning to get the new link
<r12a> i think i'm clicking on the new link, but end up on a call with just me on it
Agenda Review
Action Items
<addison> https://
addison: send an email for outlining stalled state
addison: 1257, haven't time to check on styling, so not done yet
addison: 1265, do we agree to close this last week?
<addison> w3c/i18n-discuss#11?
<ghurlbot> Issue 11 Languages / writing systems with 2 line breaking conventions in common use? (frivoal)
xfq: korean line breaking issue
r12a: no idea
addison: thread is two line breaking for korean language
… let's look offline?
xfq: 1266, done
addison: will update i18n-css call
Info Share
<r12a> https://
r12a: may mention before, working on onboarding path
… looking at this page
… check when you have time, to check lines works well or not
ACTION: addison: ask group to review languagedev_participation by next week
<ghurlbot> Sorry, I don't know what repository to use.
<trackbot> Created ACTION-1271 - Ask group to review languagedev_participation by next week [on Addison Phillips - due 2023-05-18].
RADAR Review
addison: ask group to review, and back next week
xfq: for newbie, what is language enablement, could be difficult
r12a: a line there
addison: please write a comment on that
<addison> https://
addison: no new incoming
addison: 14 pending issues for manifest, mostly small
How do we feel about installable locales?
<addison> tc39/
addison: happened to see ecma 402 issue, they have an action above
… purpose to prevent fingerprinting for minolity to be trackable by browser configuration
… not aware of any browser currently supporting installable locales
… but heard that chrome is possible to download locale data when needed, rather than installed package
… installable locale could be usable for now, but need to consider about prohibiting this or not
… whether we should jump into this. this is like a font thing we discussed before
addison: all of people in taeget language/locale are affected
r12a: what does installable locale mean?
addison: not installed in browser, but could be used from icu locales
… installing icu data or new locale data, could make people to use new locale
… but would not happen in most cases
xfq: fix seems proposed as editorial
addison: it's by javascript internationalization people
r12a: what javascript have to do?
addison: prevent javascript to install/use more new locales
[conversation on what feature is]
addison: do we have consensus that we should push this up, or not?
[agreed]
addison: will push this point as WG resolution
RESOLUTION: push back on current language in ecma402 PR 780
Pending Issue Review
<addison> https://
addison: mostly for manifest
… we reviewed mini-app manifest while a go, but did not for manifest
<addison> w3c/
addison: 1700, manifest has title icon shortname etc., in one language
… they do provide manifest file, but not localizable
… manifest is better to stored with icons in different locales (like sizes)
<addison> w3c/
addison: agreeed for 1700
addison: 1701, shortcuts appears with title etc. but without lang/dir
<addison> w3c/
r12a: let's go through if you have any questionable points
addison: 1702, auto is not the same as no explicit directionality, any better text for replacement?
<xfq__> Previous discussions: w3c/
<addison> w3c/
addison: 1703
<addison> w3c/
bert: I think localizable is more than having lang, but fine to file
addison: 1704, editorial on cite
r12a: we have talked about this with the same editor on different spec
<xfq__> w3c/
xfq: it was in the manifest spec, as above issue
<addison> w3c/
addison: 1705, on description of language tag
r12a: list some good way?
addison: in second paragraph, there are some
r12a: voice ones? for a11y
<addison> w3c/
addison: 1706, description of language tag is broken
<addison> w3c/
addison: 1707, psudo code of processing lang is included, with ecma402 function
<addison> w3c/
xfq: mention about cldr or bcp?
addison: 1708, localizability stuff
<addison> w3c/
addison: 1709, they prohibit change of name or icon by localization by security reason, should be ok but asking for application
<addison> w3c/
addison: 1710, shortcut is interesting, tell context menu to jump into somewhere in the app
… kind of short cutting in the app
… appears to UI of the host system
<addison> w3c/
addison: 1711, again, application name and shortname
<addison> w3c/
addison: 1712, manifest file is in json, by definition it's unicode but not commonly
r12a: for next time, use emoji of issue to indicate whether one is fine to put or not
addison: let's try it
<addison> w3c/
addison: 1713, quoted from internationalization consideration section, read and discuss here
r12a: what to do here?
addison: discuss here, not jump into there
addison: if localization strategy is implemented into manifest, could push this out?
xfq: might be different manifest?
addison: one manifest per language? how to deal with sub-tags?
… multi-language file could be quite large file
<xfq__> <link rel="manifest" href="en.json">
<xfq__> <link rel="manifest" href="fr.json">
<xfq__> <link rel="manifest" href="zh-Hans.json">
xfq: currently there could have multiple manifest link as above
<xfq__> app?lang=fr
addison: how to tell on which language, and how to prevent finerprinting?
xfq: javascript can manipurate accept-lang
addison: on that time, contents of manifest could be displaied already
… provably need to be happened at server side
<addison> https://
[discussion on how it works]
r12a: what to propose?
addison: here is localizable manifest, or we can have call with them,,,
[on strategy]
<xfq__> is it https://
addison: any other thoughts on this manifest spec?
AOB?
[no item]
<addison> close action-1266
<trackbot> Closed action-1266.