Meeting minutes
<gb> Action 73 make a list of invisible characters to support html 5121 discussion (on r12a) due 2024-02-22
Agenda Review
<gb> Action 73 make a list of invisible characters to support html 5121 discussion (on r12a) due 2024-02-22
Action Items
<gb> Found actions in w3c/i18n-actions: #74, #73, #72, #68, #66, #64, #53, #43, #35, #33, #18, #16, #12, #11, #8, #7, #4
<addison> #73
<addison> close #73
<gb> Closed issue #73
<addison> #72
<gb> Action 72 update specdev to match string-meta with string/block direction as appropriate (on aphillips) due 2024-02-22
r12a: I wonder whether we should put the information in #73 somewhere else
addison: why don't we discuss with the WHATWG
… depending on what the result is, we can put it somewhere
<addison> #66
<gb> Action 66 fix base direction vs. paragraph direction in string-meta (on aphillips) due 2024-01-18
<addison> #64
<gb> Action 64 Make list of HTML issues for February 22 call with WHATWG (on aphillips, xfq)
<addison> close #64
<gb> Closed issue #64
<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> #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
Bert: the MessageFormat presentation was about what I expected
… it was interesting
RADAR Review
<addison> https://
Bert: WebNN and MathML not finished
addison: I have ARIA 1.3
RADAR Review
addison: I would appreciate any other pairs of eyes
Pending Issue Review
String-Meta and the problem of 'paragraph direction'
addison: last week we discussed the term 'paragraph direction'
… we discussed replacing that with 'block direction' or 'string direction' as a term
… our glossary definition comes from Unicode
… so it's a Unicode term
… should we create new competing but better terminology?
r12a: I think we could say this is known as paragraph direction
addison: I can put 'block direction' or 'string direction' in our glossary and say 'see paragraph direction'
… with our explanation of what the term means above that
r12a: I still think 'paragraph direction' is not clear enough
addison: I agree
… I'll working on doing it that way
… any objections to that?
Follow up on I18N + CSS Call
IDN in Specdev
<addison> xfq: since we have some specs like rdf that refers to punycode
<addison> ... wonder if it is useful to add best practices related to idns
<addison> ... opinions?
<addison> ... is it useful and if so what to add and where?
<gb> Issue 119 Best practice related to IDNs (by xfq) [enhancement]
<addison> https://
addison: I think we have something in specdev today
… see ^
… maybe that needs a little attention
ACTION: xfq: work on developing new specdev material about IDNs/domain names/etc.
<gb> Created action #75
Prepare for WHATWG Call
addison: I'll incorporate the discussion of invisible characters
<addison> * Harmonization/cooperation between Infra and I18N-Glossary * Input type=email (#4562 + PR #5799) * Additional named entities (#5121)
<gb> Issue 4562 not found
<gb> Issue 5121 not found
<gb> Issue 5799 not found
addison: I propose that we discuss 3 topics
… see ^
<addison> https://
addison: and if we have time, we can go on to time-related issues and several input type=date/time issues
<addison> https://
r12a: I think we need to change the order of these things
… because the harmonization issue is not too long
<r12a> w3c/
r12a: Input type=email is essentially a very long discussion
… and the additional named entities will probably be quite short
… it took a little while to figure out how to get a list of invisible characters
… I trimmed out some obvious things like PUA characters
… and some characters you don't really want to create entities for them
… and I created a priority items list
… these are the things I'd really like to have if nothing else
Bert: one thing I often use is the variation selector for the colour of emojis
… VS16 (U+FE0F) for emoji with color or VS15 (U+FE0E) for monochrome
addison: what else do we want to say about this list?
addison: I suspect any of these conversations could be short
… I'm hopeful John can join us
… if you can't type some emails this makes this element less useful
<xfq> +1
addison: the other thing is infra vs glossary
… I made an assertion in our issue that there are places where people want to use terminology and don't want to reference Infra
… like RDF
… whereas the folks we're talking to say everyone should just use Infra
… we have a lot of terminology that people needed to use that doesn't belong to Infra
r12a: there's also a qualitative difference
… we sometimes have additional examples or explanations
addison: we do have definitions in common
… we should have some process of ensuring that we don't conflict each other
… and we want to avoid situations where we export a term that is in Infra