Meeting minutes
Agenda Review
Action Items
<addison> https://
<addison> #118
<gb> Action 118 check on the html/i18n meeting (on aphillips) due 2024-09-12
<addison> close #118
<gb> Closed issue #118
<addison> #115
<gb> Action 115 review i18n-activity#1783 (on r12a) due 2024-08-22
<addison> #114
<gb> Action 114 read through i18n-activity#1659 and report on whether we're satisfied (on r12a) due 2024-08-22
r12a: not done.
<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: Doing rewrites.
<addison> w3c/string-search#23
<gb> Pull Request 23 Address I18N-ACTION-90 by adding text from scroll-to-text-fragment#233 (by aphillips)
<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)
xfq: I pinged the respec folks 2 mweeks ago, but no reply
<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
addison: not done
Info Share
RADAR Review
<addison> https://
addison: No new incoming requests.
Bert: ACT not done yet.
Pending Issue Review
<addison> https://
<addison> i18n-activity#1902
<gb> Issue 1902 [css-overflow] Line-clamp and approaches to ellipsis insertion (by w3cbot) [pending] [tracker] [spec-type-issue] [jlreq] [alreq] [s:css-overflow] [wg:css]
<addison> w3c/
<gb> Issue 10844 [css-overflow] Line-clamp and approaches to ellipsis insertion (by frivoal) [css-overflow-4] [i18n-tracker] [i18n-jlreq] [i18n-alreq]
addison: About ellipsis insertion in bidi scope.
… My tendency is to expect the ellipsis on the outside, not necessarily the end of the text.
xfq: Will need to read this. There is also a Japanese example with a small comma.
… Maybe related to line breaking.
addison: Line breaking rules not necessarily related to where the ellipsis goes.
xfq: Yes, the ellipsis could go in the middle of an English word, which would be ambiguous.
<addison> WM5ZjI1MzhlMjhmZS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwOTEyJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDkxMlQxNDE1NDZaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1lZDZiNDM3Yzk2NTRlZjJiODg3YWExYmNiYmEzNWZhZTFhOWIzNDE4YjE1Yjc3MTA0Mjg1NjU3Y2FhYjY5MjJjJlgtQW1
<addison> 6LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.zuj9fxMzH9ikYHKZVEiAW0l575OMqu7JiDt4MiECBM4
<addison> مصر: Call me...
r12a: My pref is the ‘call me bob’ one with the ellipses at the end of the English text (the image before the horizontal line)
Bert: I think I'd prefer the ellipsis on the outside.
<addison> مصر: Call me...
r12a: Maybe if it is replacing latin letters with ‘...’, it could insert an lrm
addison: If you just let the bidi algo figure it out, then when you expand the box, the letters appear where you expect.
… The ellipsis may still be ‘wrong’ some of the time.
r12a: When an ellipsis is introduced in a piece of text, the browser is almost always going to have to chnage the text. The ellipsis is not in the source text.
…
… So you could also add a LRM or something.
addison: Florian's comment says the direction depends on the surrounding block.
… Maybe the trick is to put a direction mark on the next elided character, and then let bidi do its thing.
r12a: Yes, and in Arabic text probably a RLM.
addison: If the next character were arabic, you might not know what mark to use.
r12a: I think just look at the first character that is taken out.
… and put the direction mark after the ellipsis.
addison: I guess that could work...
addison: Any corner cases for ALM to be used?
addison: Who want to reply to the issue?
ACTION: addison: write back on css 10844 saying maybe RLM/LRM from direction of elided chars
<gb> Created action #119
TPAC Preparation
addison: I think our meetings are scheduled. We have quite an array of them.
… I'm starting on th eagenda, That will be a topic next week.
… We meet Monday and Friday as a WG.
… We'll probably do telcon-like things in the morning, for timezone reasons.
… Friday only meeting in the morning.
… WCAG on THursday.
… CSS late on Tuesday.
<xfq> https://
addison: Anybody has any topics we should work on.
xfq: We should have an agenda in the calendar.
addison: Yes, will do that.
… What do we put on Monday and Friday?
xfq: We can schedule some of our own issues.
xfq: string search...
addison: timezones...
… and language negotiation.
… So that is your home work: come up with topics.
xfq: We can still ask people on Monday and Tuesday who haven't voted on the charter yet.
… Although, if the charter expires, we can still continue, just not publish.
AOB?
xfq: We also need to look into potential topics for the joint meetings.
addison: Yes, we need to be prepared.
… Next Tuesday there is a CSS-I18N call, where this will be the main topic.
… Not sure what the topics for the WCAG joint meeting will be.
xfq: One thing to discuss is the ‘programmatically determined’ issue we talked about before.
xfq: regrets for next Tuesday.