Meeting minutes
<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
Agenda Review
Action Items
<addison> #84
<gb> Action 84 follow up on i18n-glossary#51 (on r12a) due 2024-03-21
<addison> w3c/i18n-glossary#51
<gb> Issue 51 About Tashkil : long vowel marks are called Madd. (by ntounsi) [enhancement]
<addison> #83
<gb> Action 83 replace the old core/langtags document with a redirect and some appropriate text blurb (on xfq) due 2024-03-21
<addison> close #83
xfq: Done
<gb> Closed issue #83
<addison> #82
<gb> Action 82 publish khmer lreq with new format (on r12a) due 2024-03-21
r12a: working on it.
<addison> #81
<gb> Action 81 write to kida-san about publishing simple-ruby as note with appropriate status text (on aphillips) due 2024-03-21
<addison> close #81
<gb> Closed issue #81
addison: I wrote to him
<addison> #80
<gb> Action 80 reply to Lisa about A11Y-I18N CG proposal (on aphillips) due 2024-03-14
addison: I answered.
<addison> close #80
<gb> Closed issue #80
<addison> #79
<gb> Action 79 schedule a follow-up call with WHATNOT in ~April (on aphillips) due 2024-03-07
addison: Some messages back and forth, but April meeting was cancelled.
<addison> #78
<gb> Action 78 compare infra to i18n-glossary export list and report back (on aphillips) due 2024-03-07
<addison> #77
<gb> 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
<addison> #76
<gb> Action 76 propose best practices for producers and for examples in specs in string-meta (on aphillips) due 2024-03-07
addison: Half done.
<addison> #75
<gb> Action 75 work on developing new specdev material about IDNs/domain names/etc. (on xfq) due 2024-02-29
xfq: I made a pull request.
<addison> #72
<gb> Action 72 update specdev to match string-meta with string/block direction as appropriate (on aphillips) due 2024-02-22
addison: I made a pull request.
<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: They are now in the explainer.
<addison> #33
<gb> Action 33 Close issues marked `close?` or bring to WG for further review (on aphillips)
addison: I closed another few.
<addison> #12
<gb> Action 12 Upgrade/edit the explainer to address issues raised by google (on aphillips) due 18 Jul 2023
addison: Done.
<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
JcK: There is an IETF meeting. Restructuring some areas.
RADAR Review
<addison> https://
addison: New item, Ethical Web Principles
… I'll add a due date.
… I'll take it.
Bert: Not quite done with MatML Core, found some typos, and some maybe issues. Discuss next week.
xfq: Propose we move Privacy Principles to Completed.
ACTION: addison: send a note to privacy folks saying we did a review with notes about i18n
<gb> Created action #85
Pending Issue Review
<addison> https://
<addison> w3c/i18n-activity#1834
<gb> Issue 1834 Clarify note on single character of mi as italic (by himorin) [pending] [s:mathml] [wg:math]
Specdev Work
<addison> https://
Bert: I will look at w3c/i18n-activity#1834 as part of my review.
<gb> Issue 1834 Clarify note on single character of mi as italic (by himorin) [pending] [s:mathml] [wg:math]
<addison> w3c/bp-i18n-specdev#128
<gb> Pull Request 128 New section about IDNs (by xfq)
<addison> https://
<xfq> https://
xfq: I added a section on domain names and best practices.
… One recommends not to refer to IDNA2003.
… Another recommends not to refer to Punycode.
addison: We should probably invert it. Rather than "don't do this but do this", say "do this rather then this".
JcK: Also if you say don't use idna2003 and punycode, you in fact make a comment about @@.
addison: We have a section about resource identifiers. Is that where you put this?
xfq: Yes, I made a subsection.
… A more specialized section about domain names might be useful.
addison: No, I think this is useful.
<addison> w3c/bp-i18n-specdev#127
addison: A little more work is needed.
<gb> Pull Request 127 Sync with string-meta and fix UTF-16 linking (by aphillips)
<addison> https://
<JcK> The comment about Punycode is that it is really just an encoding, able to encode almost any string of Unicode code points, while IDNA (certainly 2008 but even 2003) imposes additional constraints of the names/strings.
addison: This one is tricky. I makes the changes to "base direction" terminology.
xfq: Some guidelines are repeated.
addison: They are very similar.
<xfq> For any string field containing natural language text, it MUST be possible to determine the language and string direction of that specific string. Such determination SHOULD use metadata at the string or document level and SHOULD NOT depend on heuristics.
r12a: It must appear whereever people jump into the document.
addison: Merge?
xfq: Looks good.
<addison> w3c/
<gb> Pull Request 126 Mention combining characters in the template (by xfq)
addison: Any objection to merging this?
No objections
UTS55, UAX31 and URLPattern -- taken up
<addison> whatwg/urlpattern#43
<gb> Issue 43 Consider fully supporting RTL and Bidi URLs (by mohsen1) [i18n-needs-resolution] [decided]
addison: A while ago, there was an issue about bidi and URL patterns.
… URL patterns are URLs with variables in them that can be replaced.
<addison> https://
addison: I'm not sure what to propose.
… It is similar to Message Format in a way.
… Do we want to ask them to do something? ask them to add notes?
… Maybe ask Mark Davis and Robin Leroy to a call and ask for guidance.
xfq: HAven't read tjhe recent, long comments yet.
Changes in GB 18030-2022
addison: I'll see if I can get MArk and Robin.
<addison> https://
xfq: There is a new, incompatibe version of GB 18030.
… It is in operation since August or so,
… But IANA still refers to the old version.
… Should we do something as a group?
… Some people already contacted WHATWG and IANA.
… WebKit made changes to support the new version.
addison: The name is still GB 18030.
xfq: IANA explicitly refers to the 2000 version.
JcK: Underlying difficulty is that assumption with the registration document many years ago is that codes would not change.
addison: Is this an isolated case?
… Several vendors very much don't want to change a charset defintion without changing its name as well.
addison: What should *we* do? Order popcorn? :-)
<xfq> whatwg/
<gb> Issue 312 Reflect changes in GB 18030-2022 (by achristensen07) [i18n-tracker] [i18n-clreq]
xfq: OK for IANA. What do we do for WHATWG?
… We have already tagged an issue.
JcK: Maybe we can tell the people who are pushing for registration of the new version that they are likely to get a new identifier, maybe a name with a year attached.
<xfq> https://
addison: Would be interesting to know what ICU did. Their encoder is widely dsitributed.
xfq: I found this ^^ about ICU
addison: Looks like they adopted the changes and made those the default for GB 18030.
"global-inclusion" community group
<addison> https://
addison: We discussed last week about a a11y i18n community group.
… The a11y people now scheduled a meeting.
… Who wants to be our liaison to this group?
JcK: Could we write them a note that this very different if you go beyond English?
<addison> https://
addison: This CG is I think in reaction to us telling them that.
xfq: Interesting topic, but I have little time.
addison: I'll join the group at least, to observe. You can all do that.
[focusgroup] i18n: should arrow key navigation follow text direction?
<addison> https://
addison: It's about making the arrow keys move in logical direction. Traditionally, there is a difference in moving vs selecting text.
r12a: Can we find people like the alreq people and get them interested in the discussion?
addison: Ask on the alreq list?
r12a: You wouln't reach all people we'd want to reach.
… Maybe alreq and also Unicode list.
… UnicoRe
addison: Can you find email addresses of people I can write to?
… Or forward my mail?