Meeting minutes
Agenda Review
Action Items
<addison> https://
<addison> #159
<gb> Action 159 write up proposal for specdev char-string section, adding material that deals with the encoding interface et al (on aphillips) due 2025-02-27
addison: Started, not tready
<addison> #158
<gb> Action 158 research activity 1971 (html 10896) about ruby bidi isolation with jltf (on himorin) due 2025-02-27
atsushi: not discussed yet. But ruby should be isolated.
<addison> #157
<gb> Action 157 write glossary proposal identifying options and next steps for those options (on aphillips) due 2025-02-20
addison: Not finished
<addison> #142
<gb> Action 142 check if we can publish the new version of jlreq (on himorin) due 2024-11-21
atsushi: Still discussing with r12a
… about changes section.
… Development of the Rec
… most of the history disappeared
… I worry about if we break the names of the orgs that contributed.
… most of the active contributors in the editors list, but not sure I have their @@
… Merge them into... may have missing items
… I would keep the affiliations, but not correct them.
r12a: I'm looking for the pull request...
<r12a> w3c/
<gb> Pull Request 453 Turning editors into contributor section (by himorin)
r12a: I think you are over-complicating what I was thinking about.
… Currently jlreq lists names and affiliations (or IE).
… In the new proposal the same list, but split in two.
… I proposed you put the affiliation s at the time in brackets after the name.
atsushi: Let me revert to the original list then
r12a shows his screen.
r12a: I propose you put parentheses after the names with the affiliations when they worked on the doc.
<addison> #135
<gb> Action 135 follow up on XR issue 1393 about locale in session (on aphillips) due 2024-10-17
addison: not yet
<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: pending
<addison> #89
<gb> Action 89 update i18n specs to support dark mode (on xfq) due 2024-04-18
<addison> #33
<gb> Action 33 Close issues marked `close?` or bring to WG for further review (on aphillips)
addison: Did some clean up
<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
Radar Review
Pending Issue Review
<addison> https://
<addison> i18n-activity#1990
<gb> Issue 1990 Add localization support for GPUCompilationMessage.message and GPUError.message (by w3cbot) [pending] [tracker] [s:webgpu] [Agenda+]
addison: They put in a note. I'm going back in to see if any of our strategies applies.
<atsushi> +1
addison: Do we need to chnage the label from tracker to needs-resolutiion?
xfq: Yes, I think so
r12a: When we remove pending labels, we should add t: label
… and maybe language-specific labels as well.
addison: Agreed
r12a: Look through specdev and find the related section, The ID of that section gives you the label
[string-search] Sequences with variation selectors
<xfq> w3c/
<gb> Pull Request 24 Sequences with variation selectors (by xfq)
<xfq> https://
xfq: We discussed this once before and I made some chnages. Added a table with examples. Changed the section name to mention variation selectors.
… Not only applies to ideographs.
addison: Might want to include a search term in example 5 that includes a variation selector
xfq: Add a new row?
addison: Yes
r12a: If you have more than one row, the contents need to tbe aligned at the top
… To make it clearer
… Our default table style probably doesn't do that.
addison: Can also break up separate cells
… match/doesn't match checkbox-y thing
xfq: I'll try to tweak it
r12a: In that case merge the 3 cells on the left
addison: Otherwise looks good
… DO we want to say thing about other language variation selectors?
r12a: May want to say that other languages have variation selectors.
… Example is perhaps not explicit enough.
xfq: I'll add that.
r12a: Some change to specdev is needed for scripts that keep conjuncts together.
… Not sure it is significant for this document.
<addison> https://
addison: There is a note in section 4 in specdev
… green box
r12a: I have an example for Balinese
addison: I'll look it up.
<r12a> https://
addison: Would you like to work on this section?
<r12a> https://
addison: Or in a month?
<r12a> https://
ACTION: addison: review graphemes in specdev and add balinese example and otherwise fix the text
<gb> Created action #160
<r12a> https://
r12a: If you clikc on the green term, you'll get a breakdown of the combining character sequences. If you click on the green button at the bottom of the list you'll get the grapheme clusters.
addison: What is the issue with "user-perceived character" in Unicode?
r12a: They are not necesarily perceived as a character by the user.
… "Typographic unit" may be better.
AOB?
<xfq> w3c/
<gb> Issue 88 Use title case? (by xfq)
xfq: I propsoe we use title case for @@, too.
… I have a pull request for that
… I don't thing we have guidelines for that in W3C.
<addison> https://
r12a: The docs that use titlecase use it only on H1, don't they?
addison: In the doc ^^, the auto-generated titles use titlecase.
… I'm used to seeing titlecase all the time. When I edit, I usually use it.
r12a: I tend to use downcase section headings.
You can see whether addison or r12a edited by looking at the uppercase. :-)
xfq: This issue is specifically about the document title, not the section titles.
addison: Not sure it matters.
r12a: Happy to use titlecase on the document title.
No objections to titlecase for the document title. xfq will merge the PR