- From: Fuqiao Xue <xfq@w3.org>
- Date: Fri, 13 Sep 2024 10:33:02 +0800
- To: www-international@w3.org
https://www.w3.org/2024/09/12-i18n-minutes.html
text version:
– DRAFT –
Internationalization Working Group Teleconference
12 September 2024
[2]Agenda. [3]IRC log.
[2]
https://www.w3.org/events/meetings/bc275b6e-6c38-4ed5-b324-6606a0c6cca7/20240912T150000/
[3] https://www.w3.org/2024/09/12-i18n-irc
Attendees
Present
Addison, Atsushi, Bert, Fuqiao, Richard
Regrets
-
Chair
Addison Phillips
Scribe
Bert
Contents
1. [4]Agenda Review
2. [5]Action Items
3. [6]Info Share
4. [7]RADAR Review
5. [8]Pending Issue Review
6. [9]TPAC Preparation
7. [10]AOB?
8. [11]Summary of action items
Meeting minutes
Agenda Review
Action Items
<addison> [12]https://github.com/w3c/i18n-actions/issues
[12] https://github.com/w3c/i18n-actions/issues
<addison> #118
<gb> [13]Action 118 check on the html/i18n meeting (on
aphillips) due 2024-09-12
[13] https://github.com/w3c/i18n-actions/issues/118
<addison> close #118
<gb> Closed [14]issue #118
[14] https://github.com/w3c/i18n-actions/issues/118
<addison> #115
<gb> [15]Action 115 review i18n-activity#1783 (on r12a) due
2024-08-22
[15] https://github.com/w3c/i18n-actions/issues/115
<addison> #114
<gb> [16]Action 114 read through i18n-activity#1659 and report
on whether we're satisfied (on r12a) due 2024-08-22
[16] https://github.com/w3c/i18n-actions/issues/114
r12a: not done.
<addison> #90
<gb> [17]Action 90 steal some of henri's text from
scroll-to-text-fragment for string-search (on aphillips) due
2024-04-18
[17] https://github.com/w3c/i18n-actions/issues/90
addison: Doing rewrites.
<addison> [18]w3c/string-search#23
[18] https://github.com/w3c/string-search/issues/23
<gb> [19]Pull Request 23 Address I18N-ACTION-90 by adding text
from scroll-to-text-fragment#233 (by aphillips)
[19] https://github.com/w3c/string-search/pull/23
<addison> #89
<gb> [20]Action 89 update i18n specs to support dark mode (on
xfq) due 2024-04-18
[20] https://github.com/w3c/i18n-actions/issues/89
<addison> #33
<gb> [21]Action 33 Close issues marked `close?` or bring to WG
for further review (on aphillips)
[21] https://github.com/w3c/i18n-actions/issues/33
xfq: I pinged the respec folks 2 mweeks ago, but no reply
<addison> #8
<gb> [22]Action 8 Follow up on the status of Canvas and
formatted text (on aphillips) due 18 Jul 2023
[22] https://github.com/w3c/i18n-actions/issues/8
<addison> #7
<gb> [23]Action 7 Remind shepherds to tend to their awaiting
comment resolutions (Evergreen) (on aphillips, xfq, himorin,
r12a, bert-github) due 18 Jul 2023
[23] https://github.com/w3c/i18n-actions/issues/7
<addison> #4
<gb> [24]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
[24] https://github.com/w3c/i18n-actions/issues/4
addison: not done
Info Share
RADAR Review
<addison> [25]https://github.com/orgs/w3c/projects/91/views/1
[25] https://github.com/orgs/w3c/projects/91/views/1
addison: No new incoming requests.
Bert: ACT not done yet.
Pending Issue Review
<addison> [26]https://github.com/w3c/i18n-activity/
issues?q=is%3Aissue+is%3Aopen+label%3Apending
[26]
https://github.com/w3c/i18n-activity/issues?q=is:issue+is:open+label:pending
<addison> [27]i18n-activity#1902
[27] https://github.com/w3c/i18n-activity/issues/1902
<gb> [28]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]
[28] https://github.com/w3c/i18n-activity/issues/1902
<addison> [29]w3c/csswg-drafts#10844
[29] https://github.com/w3c/csswg-drafts/issues/10844
<gb> [30]Issue 10844 [css-overflow] Line-clamp and approaches
to ellipsis insertion (by frivoal) [css-overflow-4]
[i18n-tracker] [i18n-jlreq] [i18n-alreq]
[30] https://github.com/w3c/csswg-drafts/issues/10844
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> [31]https://
private-user-images.githubusercontent.com/113268/
365107075-18fd22fc-cc95-48ad-8399-c9f2538e28fe.png?jwt=eyJhbGci
OiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIj
oicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiO
jE3MjYxNTA4NDYsIm5iZiI6MTcyNjE1MDU0NiwicGF0aCI6Ii8xMTMyNjgvMzY1
MTA3MDc1LTE4ZmQyMmZjLWNjOTUtNDhhZC04Mzk5L
[31]
https://private-user-images.githubusercontent.com/113268/365107075-18fd22fc-cc95-48ad-8399-c9f2538e28fe.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjYxNTA4NDYsIm5iZiI6MTcyNjE1MDU0NiwicGF0aCI6Ii8xMTMyNjgvMzY1MTA3MDc1LTE4ZmQyMmZjLWNjOTUtNDhhZC04Mzk5L
<addison>
WM5ZjI1MzhlMjhmZS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEy
NTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQ
wOTEyJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT
0yMDI0MDkxMlQxNDE1NDZaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hd
HVyZT1lZDZiNDM3Yzk2NTRlZjJiODg3YWExYmNiYmEzNWZhZTFhOWIzNDE4YjE1
Yjc3MTA0Mjg1NjU3Y2FhYjY5MjJjJlgtQW1
<addison>
6LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faW
Q9MCJ9.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 [32]action #119
[32] https://github.com/w3c/i18n-actions/issues/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> [33]https://www.w3.org/2024/09/TPAC/schedule.html
[33] https://www.w3.org/2024/09/TPAC/schedule.html
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.
Summary of action items
1. [34]addison: write back on css 10844 saying maybe RLM/LRM
from direction of elided chars
Received on Friday, 13 September 2024 02:33:03 UTC