- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 05 Mar 2025 17:17:10 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[meta][css-fonts-4] Index of local font issues: fingerprinting, I18n, privacy`. <details><summary>The full IRC log of that discussion</summary> <fantasai> hober notes that Metafont is an actual thing<br> <fantasai> ChrisL: I created this meta-issue ... to organize the discussion<br> <fantasai> ChrisL: Sometimes we solve certain aspects and close an issue, so this is why closed issues are included<br> <fantasai> ChrisL: Want to show where we are, what we've solved / not solved, etc.<br> <fantasai> ChrisL: Some recent discussions around treating local fonts like webfonts<br> <fantasai> ChrisL: But we need to solve this in some way, and we need to not break the Web, and to not disadvantage users who use languages other than English<br> <fantasai> ChrisL: For example Chinese often relies on local fonts<br> <fantasai> ChrisL: Another use case was a word processor type application, where users expect the browser to access all the local fonts<br> <fantasai> ChrisL: Point of agenda item is to ask, who is interested in this topic? Who plans to work on it? If we come up with solutions, who will prototype them?<br> <fantasai> astearns: Looking for volunteers to look at the possible solutions, try to make progress up to and including prototyping, to see what we can do to make this a better situation across all browsers.<br> <fantasai> noamr: I'm personally interested in it, but don't have the bandwidth atm. I can try to find ppl in Google internally, but that's the most I can commit to.<br> <fantasai> ChrisL: That's still helpful, thanks!<br> <fantasai> astearns: As we work on solutions and get closer to something that seems viable, it may be a little easier to convince others to take the time to prototype things.<br> <emilio> (not with a mic r/n), but I'm interested, and there's people at Moz that also are, but whether but whether we're the right people to prototype depends on what solutions we're talking about :)<br> <fantasai> astearns: I will say that I got 5 private responses to my query that was meant to prompt public reply-all of ppl interested in this issue.<br> <fantasai> astearns: People expressed their opinions on what most likely possibilities were on the issue, but just private replies and not sure what ppl are comfortable with me making public.<br> <fantasai> ChrisL: I sent a private reply. First I had increased time in CSSWG by 10% and plh was ok with it.<br> <fantasai> ChrisL: I also commented on what I thought were the most practical directions, but as the editor I want to be neutral.<br> <fantasai> ChrisL: so that's why private reply<br> <fantasai> astearns: I will commit more time to looking through these issues and replying with problems that I see, or avenues that seem promising.<br> <fantasai> astearns: I may not be quite the level of ChrisL, might be more 5% increase. :)<br> <Zakim> astearns, you wanted to read emilio's comment<br> <fantasai> astearns: [reads emilio's comment]<br> <fantasai> jfkthame: I'm in a fairly similar position to noamr, I'm interested, but I have very little bandwidth atm<br> <fantasai> jfkthame: at the same time, if/when we coalesce around ideas worth prototyping, I'm happy to advocate for them and try to find resources to work on it<br> <kbabbitt> q+<br> <fantasai> kbabbitt: Encourage incubating ideas<br> <astearns> ack kbabbitt<br> <fantasai> kbabbitt: Since I brought up word processing idea, I can discuss with those stakeholders<br> <fantasai> kbabbitt: Will try to produce data necessary<br> <fantasai> astearns: So maybe we take this back to the issues and get some more work done, unless anyone else wants to add to the conversation?<br> <fantasai> astearns: OK, done for now. Expect these issues to return!<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11775#issuecomment-2701583171 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 5 March 2025 17:17:10 UTC