trackbot, prepare teleconference
<scribe> scribenick: addison
<agendabot> clear agenda
https://lists.w3.org/Archives/Member/member-i18n-core/2020Mar/0000.html
https://www.w3.org/International/track/actions/open
action-856?
<trackbot> action-856 -- Richard Ishida to Check the time planner in the meeting page to ensure it is correct for 2020 -- due 2020-02-27 -- OPEN
<trackbot> https://www.w3.org/International/track/actions/856
action-859?
<trackbot> action-859 -- Richard Ishida to Double-check that github picked up closing of 5 wcag i18n issues -- due 2020-03-05 -- OPEN
<trackbot> https://www.w3.org/International/track/actions/859
close action-859
<trackbot> Closed action-859.
action-860?
<trackbot> action-860 -- Addison Phillips to Submit issues 640 and 650 to vc-data-model and 599 to media-streams -- due 2020-03-05 -- OPEN
<trackbot> https://www.w3.org/International/track/actions/860
close action-860
<trackbot> Closed action-860.
action-861?
<trackbot> action-861 -- Addison Phillips to Add retrieving the weekly digest of external issues and reviewing it to the agenda -- due 2020-03-05 -- OPEN
<trackbot> https://www.w3.org/International/track/actions/861
close action-861
<trackbot> Closed action-861.
https://github.com/w3c/i18n-request/projects/1
(discussion of personalization semantics)
richard: took some wrestling to
get this here
... put in a new issue template for self-review
... changed a few places
addison: did you change the instructions
<r12a> We recommend creating a report a GitHub repository (like this). Do so in your own repository, so that your group can follow any resulting discussion. The self-review page allows you to copy starter text (see the Useful Links in the right column). Copy the text to a comment field in a GitHub issue in your repo, and then annotate it. Add an i18n-tracker label when you create your issue, to alert the Internationalization WG. If you want us to check it, r
<r12a> aise an i18n-request issue.
<scribe> ACTION: addison: chase down the missing review request
<trackbot> Created ACTION-862 - Chase down the missing review request [on Addison Phillips - due 2020-03-12].
https://lists.w3.org/Archives/Member/member-i18n-core/
https://lists.w3.org/Archives/Public/public-i18n-core/2020JanMar/0069.html
<r12a> https://lists.w3.org/Archives/Public/public-i18n-core/2020JanMar/0069.html
richard: want to dive into
language enablement next week
... should prune tracker issue list
... could I ask xfq and atsushi to look through list
... for old items for close, etc.
<scribe> ACTION: xfq: liaise with atsushi to come up with list of items to review/triage in teleconference
<trackbot> Created ACTION-863 - Liaise with atsushi to come up with list of items to review/triage in teleconference [on Fuqiao Xue - due 2020-03-12].
https://w3c.github.io/string-meta/#
atsushi: made several PR for quick fixes and raised one issue
<xfq_> https://github.com/w3c/string-meta/
richard: please put links in when you make issues
<scribe> ACTION: richard: review PRs on string-meta
<trackbot> Created ACTION-864 - Review prs on string-meta [on Richard Ishida - due 2020-03-12].
richard: give me a week to tidy up before you (addison) do the json-ld cleanup
addison: good to add links to the tests?
richard: maybe
... noticed chrome started to support rli/lri
<r12a> https://w3c.github.io/i18n-tests/results/bidi-algorithm#rli_etc
<r12a> ACTION: Richard to fix page at https://w3c.github.io/i18n-tests/results/bidi-algorithm#rli_etc wrt which Edge is being reported
<trackbot> Created ACTION-865 - Fix page at https://w3c.github.io/i18n-tests/results/bidi-algorithm#rli_etc wrt which edge is being reported [on Richard Ishida - due 2020-03-12].
addison: anyone talk to webkit about this?
richard: don't have one I'm aware of
<scribe> ACTION: addison: after richard fixes test page, open an issue against webkit regarding support for isolating controls
<trackbot> Created ACTION-866 - After richard fixes test page, open an issue against webkit regarding support for isolating controls [on Addison Phillips - due 2020-03-12].
richard: draw your attention to a CSS issue
<r12a> https://github.com/w3c/csswg-drafts/issues/4497
richard: bad actors could
fingerprint a system by checking different font support
... css discussing
... one thing that came out is that safari does not allow you
to use locally stored fonts on pages
... can use webfont
addison: over the wire but not off the disk
richard: kind of scary, intervened to say don't emulate this
addison: hurts minority languages
richard: yes, and
researchers
... lots not covered; and one font fits all not a good
situation to be in
<xfq_> font fingerprinting demo: https://browserleaks.com/fonts
<scribe> ACTION: addison: remind group to read css 4497 for next week
<trackbot> Created ACTION-867 - Remind group to read css 4497 for next week [on Addison Phillips - due 2020-03-12].
<JcK> Remind me next week to whine about the difference between "font",
<r12a> and typestyle and family
<atsushi> ah, no, wrong channel
This is scribe.perl Revision: 1.154 of Date: 2018/09/25 16:35:56 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Succeeded: s/draw you/draw your/ Default Present: atsushi, Bert, addison, Fuqiao, JcK Present: atsushi Bert addison Fuqiao JcK Regrets: Felix Found ScribeNick: addison Inferring Scribes: addison Agenda: https://lists.w3.org/Archives/Member/member-i18n-core/2020Mar/0000.html Found Date: 05 Mar 2020 People with action items: addison atsushi group liaise remind richard with xfq WARNING: IRC log location not specified! (You can ignore this warning if you do not want the generated minutes to contain a link to the original IRC log.)[End of scribe.perl diagnostic output]