- From: Fuqiao Xue <xfq@w3.org>
- Date: Fri, 26 Apr 2024 10:12:44 +0800
- To: www-international@w3.org
https://www.w3.org/2024/04/25-i18n-minutes.html
text version:
– DRAFT –
Internationalization Working Group Teleconference
25 April 2024
[2]Agenda. [3]IRC log.
[2]
https://www.w3.org/events/meetings/6d544156-352c-46f2-b6ec-383b4e2462fb/20240425T150000/
[3] https://www.w3.org/2024/04/25-i18n-irc
Attendees
Present
Addison, Atsushi, Bert, Fuqiao, JcK, Richard
Regrets
-
Chair
Addison Phillips
Scribe
xfq
Contents
1. [4]Agenda Review
2. [5]Action Items
3. [6]Info Share
4. [7]RADAR Review
5. [8]Pending Issue Review
6. [9]New section about IDNs
7. [10]CFC: Publish HTML Ruby Markup Extensions FPWD
8. [11]First draft of Language Negotiation
9. [12]Glossary Topics
10. [13]AOB?
11. [14]Summary of action items
12. [15]Summary of resolutions
Meeting minutes
Agenda Review
Action Items
<addison> #93
<gb> [16]Action 93 create best practices for consumers in
string-meta (on aphillips) due 2024-04-25
[16] https://github.com/w3c/i18n-actions/issues/93
<addison> #92
<gb> [17]Action 92 fix the rfc3066bis page (on xfq) due
2024-04-25
[17] https://github.com/w3c/i18n-actions/issues/92
<addison> close #92
<gb> Closed [18]issue #92
[18] https://github.com/w3c/i18n-actions/issues/92
<addison> #91
<gb> [19]Action 91 respond to i18n-activity#1846 (malformed
bidi in HTML) (on aphillips) due 2024-04-25
[19] https://github.com/w3c/i18n-actions/issues/91
<addison> close #91
<gb> Closed [20]issue #91
[20] https://github.com/w3c/i18n-actions/issues/91
<addison> #90
<gb> [21]Action 90 steal some of henri's text from
scroll-to-text-fragment for string-search (on aphillips) due
2024-04-18
[21] https://github.com/w3c/i18n-actions/issues/90
<addison> #89
<gb> [22]Action 89 update i18n specs to support dark mode (on
xfq) due 2024-04-18
[22] https://github.com/w3c/i18n-actions/issues/89
<addison> fuqiao: few issues in tr-design and respec. in
progrss
<addison> #87
<gb> [23]Action 87 write to IETF ADs about RFC9457 with JcK's
assistance (on aphillips) due 2024-04-04
[23] https://github.com/w3c/i18n-actions/issues/87
<addison> #79
<gb> [24]Action 79 schedule a follow-up call with WHATNOT in
~April (on aphillips) due 2024-03-07
[24] https://github.com/w3c/i18n-actions/issues/79
<addison> #78
<gb> [25]Action 78 compare infra to i18n-glossary export list
and report back (on aphillips) due 2024-03-07
[25] https://github.com/w3c/i18n-actions/issues/78
<addison> #77
<gb> [26]Action 77 create an issue against html requesting the
list of named entities based on work in action 73 (on r12a) due
2024-03-07
[26] https://github.com/w3c/i18n-actions/issues/77
<addison> close #77
<gb> Closed [27]issue #77
[27] https://github.com/w3c/i18n-actions/issues/77
<addison> #75
<gb> [28]Action 75 work on developing new specdev material
about IDNs/domain names/etc. (on xfq) due 2024-02-29
[28] https://github.com/w3c/i18n-actions/issues/75
<addison> close #75
<gb> Closed [29]issue #75
[29] https://github.com/w3c/i18n-actions/issues/75
<addison> #43
<gb> [30]Action 43 pull together the list of win/mac/etc apis
for setting base direction and/or language (on aphillips) due
2023-09-18
[30] https://github.com/w3c/i18n-actions/issues/43
<addison> #33
<gb> [31]Action 33 Close issues marked `close?` or bring to WG
for further review (on aphillips)
[31] https://github.com/w3c/i18n-actions/issues/33
<addison> #12
<gb> [32]Action 12 Upgrade/edit the explainer to address issues
raised by google (on aphillips) due 18 Jul 2023
[32] https://github.com/w3c/i18n-actions/issues/12
<addison> #8
<gb> [33]Action 8 Follow up on the status of Canvas and
formatted text (on aphillips) due 18 Jul 2023
[33] https://github.com/w3c/i18n-actions/issues/8
<addison> #7
<gb> [34]Action 7 Remind shepherds to tend to their awaiting
comment resolutions (Evergreen) (on aphillips, xfq, himorin,
r12a, bert-github) due 18 Jul 2023
[34] https://github.com/w3c/i18n-actions/issues/7
<addison> #4
<gb> [35]Action 4 Work with respec and bikeshed to provide the
character markup template as easy-to-use markup (on r12a) due
27 Jul 2023
[35] https://github.com/w3c/i18n-actions/issues/4
Info Share
JcK: IETF comment
… the AD @@1
… I did asked a question about @@ BCP 14
RADAR Review
<addison> [36]https://github.com/w3c/i18n-request/projects/1
[36] https://github.com/w3c/i18n-request/projects/1
addison: Bert, how is Pointer Events Level 3 coming?
Bert: not done yet
Pending Issue Review
<addison> [37]https://github.com/w3c/i18n-activity/
issues?q=is%3Aissue+is%3Aopen+label%3Apending
[37]
https://github.com/w3c/i18n-activity/issues?q=is:issue+is:open+label:pending
<addison> [38]i18n-activity#1841
[38] https://github.com/w3c/i18n-activity/issues/1841
<gb> [39]Issue 1841 Request for additional named entities for
invisible/ambiguous characters (by r12a) [pending] [s:html]
[t:char_ref]
[39] https://github.com/w3c/i18n-activity/issues/1841
New section about IDNs
<addison> [40]w3c/bp-i18n-specdev#128
[40] https://github.com/w3c/bp-i18n-specdev/pull/128
<gb> [41]Pull Request 128 New section about IDNs (by xfq)
[41] https://github.com/w3c/bp-i18n-specdev/pull/128
[42]https://
deploy-preview-128--bp-i18n-specdev.netlify.app/#resid_misc
[42]
https://deploy-preview-128--bp-i18n-specdev.netlify.app/#resid_misc
[43]https://
deploy-preview-128--bp-i18n-specdev.netlify.app/#idn
[43] https://deploy-preview-128--bp-i18n-specdev.netlify.app/#idn
<addison> xfq: changed first one to point to idna2008
<addison> ... annevk made some comments, pointing to URL spec
and maybe unicode's TR
[44]https://url.spec.whatwg.org/#concept-domain-to-ascii
[44] https://url.spec.whatwg.org/#concept-domain-to-ascii
<addison> ... in the URL spec there is this link ^^
<addison> ... that refers to UTS46 with some flags set
<addison> jck: let me try to summarize
JcK: using IDNA by way of UTS 46 started out by contradicting
IDNA 2008 and it's gotten worse
<addison> ... using idna by way of uts46 (which somewhat
conflicts)
JcK: this request makes no sense
… yes, there are caveats
… but basically we're in a situation where we have different
standards
… I don't know what to suggest doing
… I can sit down and review but I don't have the time now
… from a WHATWG standpoint, it definitely makes perfect sense
… but that's not consistent
addison: making a couple observations
… first is just a stylistic thing
… you have 2119 keywords
… should and should not should be capiitalized
… I think we don't actually have to weigh into some of these
religious arguments
… because I think it would be non-controversial to say replace
any references to 2003 with 2008
… I think it's good guidance
… the second one is to not refer to Punycode because it's
incomplete
… the URL spec is maybe good for what browsers do
… but is incomplete because it does not cover all of URI
… and the UTS 46 thing is just somebody needs to @@
JcK: saying this less rather than more is probably a reasonable
short-term strategy
addison: I was gonna suggest maybe we could just describe what
the situation is
… xfq started this because we encountered people referring to
Punycode
ACTION: xfq: send jck the text from proposed idn section to jck
for suggestions
<gb> Created [45]action #94
[45] https://github.com/w3c/i18n-actions/issues/94
CFC: Publish HTML Ruby Markup Extensions FPWD
<addison> [46]https://lists.w3.org/Archives/Public/
public-i18n-core/2024AprJun/0022.html
[46]
https://lists.w3.org/Archives/Public/public-i18n-core/2024AprJun/0022.html
<addison> [47]https://w3c.github.io/html-ruby/
[47] https://w3c.github.io/html-ruby/
<addison> [48]https://www.w3.org/2022/02/ruby-agreement
[48] https://www.w3.org/2022/02/ruby-agreement
r12a: it's the stuff Florian has been working on
<addison> [49]w3c/htmlwg#26
[49] https://github.com/w3c/htmlwg/issues/26
<gb> [50]Issue 26 CFC: Publish HTML Ruby Markup Extensions FPWD
(by LJWatson)
[50] https://github.com/w3c/htmlwg/issues/26
r12a: the i18n WG should review
addison: which one of these is the document?
r12a: I haven't checked it yet
atsushi: this is for the W3C HTML WG
… independent from WHATWG
… this matches the CSS Ruby spec
r12a: we tried to get it directly into the HTML Standard
… the conclusion was that we would publish this document
… and we would put everything into the HTML Standard
… it's a FPWD of a document that's been around for like 10
years or something
atsushi: per WHATWG and W3C MoU, the HTML WG has been working
on this in the past 2 years
addison: but we should endorse this, right?
<Bert> +1
atsushi: I think so
<addison> +1
<r12a> +1
<atsushi> +1
<xfq> +1
<JcK> +1
RESOLUTION: I18N WG endorses FPWD publication of HTML Ruby
Markup Extensions
ACTION: addison: write endorsement of html ruby markup
extensions
<gb> Created [51]action #95
[51] https://github.com/w3c/i18n-actions/issues/95
First draft of Language Negotiation
<addison> [52]https://github.com/aphillips/i18n-drafts/blob/
gh-pages/tutorials/language-negotiation/language-negotiation.md
[52]
https://github.com/aphillips/i18n-drafts/blob/gh-pages/tutorials/language-negotiation/language-negotiation.md
<addison> [53]https://lists.w3.org/Archives/Public/
public-i18n-core/2024AprJun/0017.html
[53]
https://lists.w3.org/Archives/Public/public-i18n-core/2024AprJun/0017.html
addison: I have created a first draft of a document about
language negotiation
… I welcome comments
Bert: it mentions IP address as a way of finding the user's
location
… I think there might be a note saying that is very unreliable
addison: yes
r12a: how are you gonna publish this? as an article?
addison: currently parked under tutorials, but it doesn't have
to stay there
r12a: no it shouldn't
… we use the term 'tutorial' term different
… we have lots of articles that teaches stuff
… but they're articles, not tutorials
… we have tutorials that contains a series of links
… for a larger view of a topic
… go and read this and this and this
… so this would be an article
addison: I created a markdown page
… I think it's easier to review
r12a: is there a reason you didn't use GitHub Discussions?
<addison> ```suggestion
addison: because I want to be a little bit formal
addison: it's an early working draft
… quicker than making the HTML and being super formal
r12a: when you do the pre-HTML version, then use Discussions
for that
<addison> [54]w3c/i18n-drafts#581
[54] https://github.com/w3c/i18n-drafts/pull/581
<gb> [55]Pull Request 581 Initial work on language-negotiation
materials (by aphillips)
[55] https://github.com/w3c/i18n-drafts/pull/581
addison: there is a PR against the w3c repo
… see ^
… you can comment on the markdown
… I'll move this from tutorials to articles
… comments are welcome
Glossary Topics
<addison> [56]i18n-glossary#76
[56] https://github.com/w3c/i18n-glossary/issues/76
<gb> [57]Issue 76 Errors in definition of orthographic syllable
(by NorbertLindenberg) [bug]
[57] https://github.com/w3c/i18n-glossary/issues/76
addison: Norbert filed an issue
… about "orthographic syllable" vs "typographic character unit"
r12a: the second point about "one or more grapheme clusters"
should definitely be fixed
[58]https://unicode.org/glossary/#orthographic_syllable
[58] https://unicode.org/glossary/#orthographic_syllable
r12a: for his first paragraph
… those 2 specific examples are exceptions to the rule
… but the rule covers a vast amount of stuff
addison: do you want an action to work on fixing this?
r12a: yes, but it will take me a little while
ACTION: richard: evaluate and where necessary fix
[59]i18n-glossary#76
[59] https://github.com/w3c/i18n-glossary/issues/76
<gb> Created [60]action #96
[60] https://github.com/w3c/i18n-actions/issues/96
<r12a> #76 note [61]w3c/i18n-glossary#76
[61] https://github.com/w3c/i18n-glossary/issues/76
<gb> [62]Issue 76 Errors in definition of orthographic syllable
(by NorbertLindenberg) [bug]
[62] https://github.com/w3c/i18n-glossary/issues/76
<gb> [63]CLOSED Action 76 propose best practices for producers
and for examples in specs in string-meta (on aphillips) due
2024-03-07
[63] https://github.com/w3c/i18n-actions/issues/76
AOB?
<r12a> #96 note [64]w3c/i18n-glossary#76
[64] https://github.com/w3c/i18n-glossary/issues/76
<gb> [65]Action 96 evaluate and where necessary fix
i18n-glossary#76 (on r12a) due 2024-05-02
[65] https://github.com/w3c/i18n-actions/issues/96
<r12a> note #76 [66]w3c/i18n-glossary#76
[66] https://github.com/w3c/i18n-glossary/issues/76
<gb> Added [67]comment
[67]
https://github.com/w3c/i18n-actions/issues/76#issuecomment-2077433577
<r12a> note #96 [68]w3c/i18n-glossary#76
[68] https://github.com/w3c/i18n-glossary/issues/76
<gb> Added [69]comment
[69]
https://github.com/w3c/i18n-actions/issues/96#issuecomment-2077435542
Summary of action items
1. [70]xfq: send jck the text from proposed idn section to jck
for suggestions
2. [71]addison: write endorsement of html ruby markup
extensions
3. [72]richard: evaluate and where necessary fix
i18n-glossary#76
Summary of resolutions
1. [73]I18N WG endorses FPWD publication of HTML Ruby Markup
Extensions
Minutes manually created (not a transcript), formatted by
[74]scribe.perl version 221 (Fri Jul 21 14:01:30 2023 UTC).
[74] https://w3c.github.io/scribe2/scribedoc.html
Received on Friday, 26 April 2024 02:12:45 UTC