Meeting minutes
Agenda Review
Action Items
<addison> #97
<gb> Action 97 add explainer to next week's agenda (on aphillips) due 2024-05-16
<addison> close #97
<gb> Closed issue #97
<addison> #96
<gb> Action 96 evaluate and where necessary fix i18n-glossary#76 (on r12a) due 2024-05-02
<addison> #93
<gb> Action 93 create best practices for consumers in string-meta (on aphillips) due 2024-04-25
<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> #89
<gb> Action 89 update i18n specs to support dark mode (on xfq) due 2024-04-18
<addison> #87
<gb> Action 87 write to IETF ADs about RFC9457 with JcK's assistance (on aphillips) due 2024-04-04
<addison> #79
<gb> Action 79 schedule a follow-up call with WHATNOT in ~April (on aphillips) due 2024-03-07
<addison> #78
<gb> Action 78 compare infra to i18n-glossary export list and report back (on aphillips) due 2024-03-07
<addison> #43
<gb> Action 43 pull together the list of win/mac/etc apis for setting base direction and/or language (on aphillips) due 2023-09-18
<addison> #33
<gb> Action 33 Close issues marked `close?` or bring to WG for further review (on aphillips)
<addison> #12
<gb> Action 12 Upgrade/edit the explainer to address issues raised by google (on aphillips) due 18 Jul 2023
<addison> close #12
<gb> Closed issue #12
<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 r12a) due 27 Jul 2023
Info Share
addison: Ben Allen from Igalia
… new member
… if you need anything, don't suffer and be silence
Ben: what got me interested in i18n in the first place is I was annoyed in my 1st semester intro to programming class
… when people couldn't do introductory assignments involving use of their own name
… because the number of chars in their name would get counted wrong
… I've been on TC39-TG2 for 1.5 years now
… I just need to get to know the W3C side
r12a: I've been in the W3C for 21 years
Bert: I've been in the W3C for a very long time
… I've been doing CSS, HTML, XML, some privacy stuff
… a lot of different things
atsushi: I'm from Japan
… working in several WGs
… and the Japanese task force
xfq: I'm Fuqiao Xue
RADAR Review
<addison> https://
xfq: W3C Staff, Internationalization Lead since January this year
… joined the W3C in 2017
… based in Beijing, China
addison: Addison Phillips
… chair and IE of the group
Pending Issue Review
<addison> https://
Ruby-t2s-req as a DNOTE?
addison: there was an email from fantasai
… about converting one of Murata-san's document into a draft note
<addison> https://
<addison> https://
addison: there were a couple of emails on our member list about it
atsushi: I have no additional info other than Murata-san shared in the email
… he's working on this and will finish it
xfq: @@1
… we can wait Murata-san to work on it
Is the string-meta explainer finished?
addison: anything else on that?
<addison> https://
addison: see ^
addison: is this document done or does it need more work?
addison: ongoing work to convert the API reference section to an article
r12a: there's a piece of text with a brown background
… is it supposed to be like that?
addison: because it's not really JSON
… because we have "..."
r12a: it looks like the document is broken
xfq: maybe you can use three three backticks in a row, without 'json' after it
… for the fenced code blocks
addison: yeah, that would get rid of the brown
<addison> https://
addison: there was a thread somewhere about the Arabic text
… sent by Najib
xfq: it's about another page, but the text is probably the same
addison: if you go down underneath References, you'll see very small little numbers and text
… those are footnotes in Markdown
… I could convert these to just plain links
r12a: it would be a lot easier
… because you've got the same kind of numbering going on in References
… that doesn't look terribly prominent
xfq: the API reference section will be removed once we have the article, right?
addison: yeahk, we'll probably have a link to the article
… rather than maintaining it in 2 places
xfq: the Chinese and Japanese examples also link to the "Bidirectional Text Demo" page
addison: yes, it should select the correct font there
xfq: maybe we should rename the "Bidirectional Text Demo" page to something more general
… because it also demonstrates non-bidi text
addison: maybe we call it "string-meta demo"
雪, 刃, 直, 令, 垔 (Japanese)
雪, 刃, 直, 令, 垔 (Simplfied Chinese)
r12a: the first line is Japanese
… Kaku Gothic
… the second is PingFang
addison: that's your system
… the Markdown has <span lang=ja/zh-Hans>
… your browser should demonstrate the difference between the chars visually based on the language selection
… my browser does a decent job
https://
https://
[Discuss SC/TC/Japanese font selection]
ACTION: richard: fix code points examples in lang-bidi-use-cases
<gb> Created action #98
xfq: https://
… but it should use zh-Hant instead
<Najib> HI
<Najib> If necessary, action on me to provide a new text for the Arabic example.
<Najib> It appears also elsewhere.
<addison> yes, please: did you already do that in the issue with richard?
<Najib> ?
ACTION: najib: provide new arabic example text for explainer
<gb> Cannot create action. Validation failed. Maybe najib is not a valid user for w3c/i18n-actions?
<Najib> May be
ACTION: ntounsi: provide new arabic example text for explainer
<gb> Cannot create action. Validation failed. Maybe ntounsi is not a valid user for w3c/i18n-actions?
<Najib> I already had actions
<Najib> Please go ahead.
AOB?
<gb> Pull Request 550 Update the titles of the techniques page (by xfq)
xfq: see the PR ^
addison: it looks weird to me to have an article with non-title case title
https://
addison: I don't care that much, but I think it looks weird
r12a: well, only if you're volunteering to change all of the article titles
addison: I'm not volunteering to do any work on this ;-)