Meeting minutes
<addison> s/Atsusu/Atsushi
Agenda Review
Action Items
<addison> https://
<addison> #156
<gb> Action 156 Figure out what is preferred for Fig 15 at https://r12a.github.io/scripts/bopomofo/ontheweb#horhor (on r12a) due 2025-01-28
<addison> #155
<gb> Action 155 review glossary definitions for normativity or candidates for normativity (on aphillips) due 2025-01-23
<addison> #148
<gb> Action 148 propose specdev text related to design-principles#464 discussion (on aphillips) due 2024-12-12
<addison> #143
<gb> Action 143 make comments on the encoding issue attached to i18n-activity#1940 (on aphillips) due 2024-11-28
<addison> #142
<gb> Action 142 check if we can publish the new version of jlreq (on himorin) due 2024-11-21
<addison> #135
<gb> Action 135 follow up on XR issue 1393 about locale in session (on aphillips) due 2024-10-17
<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> #33
<gb> Action 33 Close issues marked `close?` or bring to WG for further review (on aphillips)
<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) due 27 Jul 2023
Info Share
JcK: IETF document that recommends using any Unicode scalar in strings to transmit over the internet, as long as it's valid UTF-8.
r12a: I added a neat feature to the pickers.
r12a: If you have Noto Naskh Arabic on your system, you should see it.
People trying it out.
r12a: I set up some tests. Seeing if Noto was fixed.
RADAR Review
<addison> https://
addison: No new incoming requests.
… I'll have to move the IETF reviews over.
<addison> #1741
<gb> Issue 1741 not found
bert: We finished all MathML Core issues. Can move it to Completed?
<addison> i18n-activity#1741
<gb> Issue 1741 "rtlm" OpenType feature for RTL mirroring (by w3cbot) [tracker] [t:typ_font_management_x] [s:mathml] [wg:math]
addison: Keep the one tracker issue open, but move the review to completed.
r12a: Bert's comments on the WAI ACT issues could have been put in the tracker issues on GitHub.
atsushi: About Kida san and the earlier topic, trying to convince him to become IE.
Pending Issue Review
<addison> i18n-activity#1988
<gb> Issue 1988 [css-fonts-4] Detection-prevention approach to the local font privacy issue (by w3cbot) [pending] [tracker] [s:css-fonts]
addison: Was there any resolution after the CSS ftf last week?
r12a: I think we concluded that it was not either i18n or privacy, and win or lose, but we need to cater to both.
… No good plan for how yet.
… Spec says we have to figure out a way to implement it in browsers. Take care of fingerprinting, but allow users to override.
… There are several proposals.
… Lea had one, and others.
… But problem not solved.
addison: I agree we as a WG don't say only one of the two should win.
r12a: One other thing was discussed: Fantasai brought up an issue where she wants to define a set of lines, like baselines, for text,
… to align things such as dropcaps and more.
… We agreed these would not be standard lines in the sense of how you describe a font or character,
… but something to describe what you want to do with a character in a situation, such as dropcap.
… Next step would be to define what the various functions are and that the lines can vary from font to font.
… Fantasai proposed creating a registry for fonts and scripts to say what the lines are for.
… But it is not so much a function of the script as of the font.
… And will it be a registry of all the fonts in the world?
… Top of char line, top of x-height line, etc. They could apply to some fonts.
addison: Different for arabic font, e.g.
r12a: You could put that info for that font in the registry.
Responses from AG WG on ACT rules review
<addison> https://
<addison> i18n-activity#1912
<gb> Issue 1912 Is the ‘descriptive title’ used for matching? (by bert-github) [needs-resolution] [wg:ag] [s:act-rules-format]
<addison> close i18n-activity#1912
<gb> Cannot close issue #1912 -> ghurlbot does not have the correct permissions to execute `CloseIssue`
<addison> i18n-activity#1911
<gb> Issue 1911 ACT does not require that the language of text is indicated (by bert-github) [needs-resolution] [wg:ag] [s:act-rules-format]
<addison> i18n-activity#1910
<gb> Issue 1910 How are rule identifiers matched to one another? (by bert-github) [needs-resolution] [wg:ag] [s:act-rules-format]
Bert: Not quite satisfied with their answer to what is a unique identifier.
addison: They should say something, maybe point to charmod to help implementations.
<addison> i18n-activity#1909
<gb> Issue 1909 Should ACT require the formats for rules to be localizable? (by bert-github) [needs-resolution] [wg:ag] [s:act-rules-format]
<addison> In addition to supporting people with disabilities, using an accessible format also makes internationalization of ACT Rules easier.
Bert: I'm leaning to accepting just the addition of the words "and localizable".
<addison> https://
addison: What exactly does "internationalization of ACT Rules" mean?
… It would be nice to say that the human-readable bits need to be localizable.
… They are not saying anythign about localization in here.
… So not close the issue, but they should add text that says ACT Rules should be localizable and can appear in multiple languages.
Specdev changes related to TAG design-principles
<addison> w3c/
<gb> Pull Request 149 Address differences between DESIGN-PRINCIPLES and SPECDEV (by aphillips) [Agenda+] [Best Practice] [normative]
<addison> https://
<addison> https://
r12a: I looked at this and don't have comments.
… Possibly have the explanation before the mustard, but not important.
… To explain what is the diff. between a DOMString and a USVString.
… Most other text is expanding on the mustard.
addison: Did the mustard itself seem right?
addison: It is identical to the version in Design Principles.
… Without the Design Principles we would write "use this for this and that for that"
r12a: Maybe move the explanation and examples and bring the USVString and DOMString together.
… Move the gray bar with explanatuiins & examples up by one
AOB?
<r12a> w3c/
<gb> Issue 1909 Should ACT require the formats for rules to be localizable? (by bert-github) [needs-resolution] [wg:ag] [s:act-rules-format]
addison: We'll look at specdev again next week.
<r12a> https://
r12a: ^^ is a tool to copy clean text from minutes to issues.