Meeting minutes
Agenda Review
Action Items
<addison> gb, list open actions
<gb> Found actions in w3c/i18n-actions: #80, #79, #78, #77, #76, #75, #74, #72, #68, #53, #43, #35, #33, #18, #16, #12, #11, #8, #7, #4
<addison> #80
<gb> Action 80 reply to Lisa about A11Y-I18N CG proposal (on aphillips) due 2024-03-14
<addison> #79
<gb> Action 79 schedule a follow-up call with WHATNOT in ~April (on aphillips) due 2024-03-07
addison: will do #80 today
<addison> #78
<gb> Action 78 compare infra to i18n-glossary export list and report back (on aphillips) due 2024-03-07
addison: #79, I'll goto find the issues for next month's call
<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: #78, will discuss later
<addison> #76
<gb> Action 76 propose best practices for producers and for examples in specs in string-meta (on aphillips) due 2024-03-07
r12a: #77, not done yet
<addison> #75
<gb> Action 75 work on developing new specdev material about IDNs/domain names/etc. (on xfq) due 2024-02-29
<addison> #74
<gb> Action 74 ask korean folks about text-autospace and hangul (on xfq) due 2024-02-27
<addison> close #74
<gb> Closed issue #74
<addison> #72
<gb> Action 72 update specdev to match string-meta with string/block direction as appropriate (on aphillips) due 2024-02-22
<addison> #68
<gb> Action 68 follow up with florian about testing with kindle (on aphillips) due 2024-01-25
<addison> #53
<gb> Action 53 come up with a set of information CSS want the i18n group to provide support for generic font families (on frivoal, fantasai) due 2023-11-01
<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> #35
<gb> Action 35 make the edits of CSS #5478 (on fantasai) due 2023-08-30
<addison> #33
<gb> Action 33 Close issues marked `close?` or bring to WG for further review (on aphillips)
<addison> #18
<gb> Action 18 Have informal explanation sessions about counter style translations with csswg members (on frivoal, fantasai) due 18 Jul 2023
<addison> #16
<gb> Action 16 Keep track of line-breaking in Korean for i18n-discuss#11 (on aphillips) due 1 Jan 2024
<addison> #12
<gb> Action 12 Upgrade/edit the explainer to address issues raised by google (on aphillips) due 18 Jul 2023
<addison> #11
<gb> Action 11 Triage all css properties to determine which are logical, physical, or na by default (on frivoal) 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> #5
<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
r12a: I will try and remember to do #4 next week
Bert: xfq sent me an email about the history of i18n activity
… I'm collecting the dates
addison: I'll be interested to see what you come up with
… many happenings dating to the late nineties in the group
RADAR Review
<addison> https://
addison: we have a new request
… Privacy Principles
… this might be super amusing
… 'be sure you never do anything to allow locale to be stripped off'
Pending Issue Review
<addison> https://
addison: w3c/
<gb> Issue 1835 Explicitly specify binary encoding for string truncation (by w3cbot) [pending] [tracker] [s:webauthn]
addison: related to truncation
… that's still in progress
<addison> w3c/i18n-activity#1834
<gb> Issue 1834 Clarify note on single character of mi as italic (by himorin) [pending] [s:mathml]
addison: you're welcome to look at that
atsushi: it's a minor point within their note
… This transformation is via `text-transform: math-auto` and is to apply the italic table but not applying italic style
… but it's not clear from their spec
addison: do they mean single character?
… they say 'single letter'
… but I can imagine the letter having an accent on it
… and therefore be 2 code points
atsushi: this is the point I want to discuss with the group
addison: what is 'italic table'?
https://
atsushi: it's common in maths and physics
… similar character used in mathematical formula
addison: OK
… and they have a mapping for the Unicode code points
… they need to clarify this
addison: anybody else got a comment?
Discontinuing simple-ruby
addison: since we're gonna do a full review when Bert is done
… we can hold this for now
addison: we have a request from Kida-san
… the JL-TF wants to stop maintaining it
… and want to publish effectively a tombstone version of it
… with some sort of box in it that says we've stopped developing this
… florian sent a reply to that request
… saying you don't wanna kill the document
<addison> https://
addison: there might be valuable content
… it is a note track document
… and the note track does not have a discontinued state like the rec track
… but we have other notes that we published in the past that have some sort of big red box at the top saying
… this isn't being maintained anymore
… Unicode in XML is an example
… the document is a subset of ruby that we said is simple
… it can say 'here is a description of simple ruby, work is underway to provide a more complete model'
… if something else comes out later
… we can come back and change what that note says
… 'this is now a historical document. look over here for more info'
ACTION: addison: write to kida-san about publishing simple-ruby as note with appropriate status text
<gb> Created action #81
JcK: that seems right to me
New lreq doc format
<r12a> https://
r12a: taking things a little further than I had last week
<r12a> https://
r12a: I started putting the links to the orthography notes and other relevant documents into a list format
… and realized that actually we could do something quite useful here
… we have another document called the Language enablement index
… I don't know how many people actually look at that document
… but I certainly keep forgetting to update it
… so now I'm doing something similar in the lreq documents, and it allows more granular information or specific information that you can look up quite easily
<r12a> https://
r12a: I think it's much easier to remember to update these links
… in the fonts section above
… forget about the Chinese and Hangul Layout requirements for the time being, I'll come back to that in a sec
… you have a list very much like we have in the Khmer document
… that would make it much easier to maintain the typography thing without duplicating work
… for clreq/jlreq/alreq, we may or may not add these list of links
… in which case they might still have some links in the typography index
… but what I'm talking about in particular here is for the new lreq documents
… like Khmer
… and Mongolian, Ethiopic, possibly Korean
… if you look at section 6.2 https://
… it says 'See Ishida, Cambodian (Khmer) Orthography Notes/Phrase & section boundaries.'
… I don't think that's the best approach
addison: this looks automatable
r12a: a large part of it, yes
addison: a bunch of the links here are generic links
… and you could have a little piece of JSON to say here's the specific things
r12a: yes
… it's also easy to have a flat document
… from a template
… and then all you have to do is to add the labels into the right places
… that's actually one of the problems with the typography index at the moment is that the date is driven through JS
… as it's getting bigger
… it's becoming more of a problem to maintain the date in a separate file from the index page itself
ACTION: richard: publish khmer lreq with new format
<gb> Created action #82
addison: any comments?
r12a: I propose that I complete the Khmer lreq document
… and then publish that
Old version of LTLI
r12a: will do similar thing to the Tibetan lreq
https://
<addison> xfq: I found an old version of LTLI via a search engine
<addison> ... this page ^^
<addison> ... was searching for 'language-range' on google
<addison> ... seems like an early draft version
<addison> ... since we have one on TR, propose we add a big red box pointing at LTLI
addison: if it weren't a cool URL, we would delete it with extreme prejudice
… but since it exists, we might even consider hollowing it and just have a big red box
… or a permanent redirect to LTLI
… I don't think this document serves any purpose except to confuse people
… this was a draft document
ACTION: xfq: replace the old core/langtags document with a redirect and some appropriate text blurb
<gb> Created action #83
I18N Glossary
addison: we have definitions and some of them have similar
… but the nature of theirs and our glossary don't match
… I owe this group a more detailed analysis
… I think we want to do that sooner rather than later
… so that we have have a follow up discussion with them
… the key disconnect is that they're married to the JS string
… when they refer to code units and such
… we had a discussion with RDF-star about this
… @@ byte-wise truncation of HTTP headers
… when doing truncation the terminology in Infra doesn't quite match ours
… so that's the status
… I have a side thing
… we talked about a couple of PRs last time
… one of them is planes and blocks
… the other is variation selector
<atsushi> +1
addison: should we merge the variation selector PR?
… let's merge it
https://
addison: we have some issues open
<gb> Issue 70 Definition of cursive scripts (by xfq) [enhancement]
[xfq explains the issue]
addison: my comments was the existing text doesn't claim to be exhaustive
… but the problem is you have to always have an alert in your brain so when a new script emerges in the Unicode standard and it happens to be cursive
… you have to go back here and complete the list
… there may be other things already in Unicode that are not in that list
<gb> Issue 51 About Tashkil : long vowel marks are called Madd. (by ntounsi) [enhancement]
addison: shall we leave it alone?
… do we need to say that the list is not exhaustive?
xfq: I'm OK with closing this issue with no changes
addison: OK
addison: #51 is a comment from Najib about long vowel marks
addison: about Tashkil
… does somebody wanna take this on?
… r12a, you provided a long comment about it
r12a: this is not a manual about how to write Arabic or anything like that
… I would have to read the current definition again and think about what Najib is adjusting
addison: is there a better home for some of this information
r12a: you find it everywhere you look
… Wikipedia and my orthography notes
… it's probably in alreq too
… which is another reason you don't necessarily need to put it there
ACTION: richard: follow up on i18n-glossary#51
<gb> Created action #84
AOB?
<r12a> #84 note: w3c/
<gb> Issue 51 About Tashkil : long vowel marks are called Madd. (by ntounsi) [enhancement]
<gb> Action 84 follow up on i18n-glossary#51 (on r12a) due 2024-03-21