Meeting minutes
Agenda Review
Action Items
<addison> #90
<gb> Action 90 steal some of henri's text from scroll-to-text-fragment for string-search (on aphillips) due 2024-04-18
<addison> #33
<gb> Action 33 Close issues marked `close?` or bring to WG for further review (on aphillips)
addison: Probably an agenda item next week.
<addison> #16
<gb> Action 16 Keep track of line-breaking in Korean for i18n-discuss#11 (on aphillips) due 1 Jan 2024
<addison> #8
<gb> Action 8 Follow up on the status of Canvas and formatted text (on aphillips) due 18 Jul 2023
<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, r12a) due 27 Jul 2023
Info Share
RADAR Review
<addison> https://
xfq: I raised an issue on WCAG2 and got a reply.
addison: Atsushi said he had no issues on Incremental Font Transfer, but maybe he had one after all.
… I'll make it a pending issue to discuss next week.
Pending Issue Review
<addison> https://
addison: Moving all my Infra issues to Infra land. Otherwise nothing stands out.
<addison> i18n-activity#1870
<gb> Issue 1870 [css-content] Styling applied to a quoted element should not affect the quotation marks (by w3cbot) [pending] [s:css-content] [needs-resolution] [wg:css]
addison: Not sure about #1870.
<gb> Issue 1870 not found
<addison> w3c/
<gb> Issue 10468 [css-content] Styling applied to a quoted element should not affect the quotation marks (by r12a) [css-content-3] [i18n-needs-resolution]
r12a: Related to the long-running discussion on quotes. But not quite the same.
addison: I think we'll agree. I'll remove "pending".
r12a: It needs some other labels. Adding them now.
Programmatically determine the language of text (WCAG2ICT)
<xfq> w3c/
<gb> Issue 463 Programmatically determine the language of text (by xfq) [i18n-needs-resolution]
xfq: We discussed this before. I'm asking them what they are trying to accomplish.
… Is it heuristic determination of language? What about the exception list?
… It is about whether the assistive tech can determine the language, from markup or any other means.
… If it can, the success criteria succeed.
… They didn't answer why the exception list.
addison: the explanation from Gregg is clearer than the text in the spec.
… But the exception list is still there.
xfq: I can ask them about the list of exceptions.
… Should we ask them to add a note to explain about what "programmatically determined" is? They have a definition, but maybe it is not clear enough.
… Another option is to switch to a different term.
addison: I'd argue with their exception list.
… Assume you have a paragraph marked as French and a proper name inside it. That proper name is still in French.
<xfq> https://
xfq: The text is from WCAG, with "non-web document" replacing "content" there.
addison: APIs can provide language metadata.
xfq: One thing we can do is ask about the list of exceptions.
addison: Maybe we discussed this in the past already. Would need to look at old issues.
<xfq> https://
<xfq> https://
xfq: ^ this is the list of issues on GitHub, but maybe it was before we used GitHub.
addison: Maybe they should add something to the note avout what is going on, in particular the list of exceptions.
<r12a> w3c/
<gb> Issue 1882 Programmatically determine the language of text (by xfq) [needs-resolution] [t:lang_strings] [wg:ag] [s:wcag2ict]
xfq: I'll add a comment.
AOB?
Bert: regrets for next week