Meeting minutes
<addison> trackbot, prepare teleconference
Agenda Review
xfq: epub
r12a: changes to language enablement
david: in alreq there are some images missing
<addison> David: arabic layout doc missing some images
Action Items
<addison> https://
<addison> action-989?
<trackbot> action-989: Addison Phillips to Check tus and if necessary ping unicode folks about d145 normalization case fold ordering questions -- due 2021-01-21 -- OPEN
addison: talked to Craig @@
… talked to Mark again
<addison> close action-989
<trackbot> Closed action-989.
r12a: Looked at string meta use of 'natural language'
… most of them should be replaced by localizable
addison: I'll do that
<addison> action-1025?
<trackbot> action-1025: Richard Ishida to Look at the typography index and determine a way to point to other (outside) documents -- due 2021-05-13 -- OPEN
<addison> close action-1025
<trackbot> Closed action-1025.
Info Share
r12a: published three documents
<r12a> https://
r12a: a wide review request this week
RADAR Review
<addison> https://
addison: review requests
xfq: I can review CSS Multi-column Layout Module Level 1
D145 and Charmod
<addison> https://
addison: Mark Davis ☕️ replied
… unless there' some obscure thing I don't know about
… we can make charmod-norm be consistent with @@
… any objections?
<addison> http://
addison: move step 1 to 3
r12a: and 3 to 1
Action: addison: revise charmod-norm to move optional step from 1 to 3
<trackbot> Created ACTION-1026 - Revise charmod-norm to move optional step from 1 to 3 [on Addison Phillips - due 2021-05-20].
changes to language enablement
<r12a> https://
r12a: my action was to figure a way to link to the typography document
<r12a> https://
r12a: thought about various different ways
… ^ ED
<r12a> https://
r12a: we already have some stuff
… if you look at vertical text ^
… some stuff are not W3C-related
… if you click on the link in Orthography Notes
… there's another page
… you can click through all these things
… if anybody has any objections or finds any problems with the way that I've done this
<r12a> https://
r12a: please let me know
… this is for Gap Analysis docs ^
r12a: I think that's a useful tool for you to use
<r12a> https://
r12a: working on this ^
… we've been accumulating gaps for a while now
… from now on we need to systematizing it through a pipeline
… if you click webkit it will show you things that need to be resolved in webkit
… how to manage @@ across many documents
<r12a> https://
r12a: like "Browsers apply extraneous spaces when letter-spacing" ^
… this text was repeated for Dutch, French, Georgian, German, Greek, and Hungarian gap analysis documents
… because they share the same repo
… but if you go to clreq
<r12a> https://
<r12a> https://
r12a: basically it says "This issue applies to all languages that use letter-spacing."
… so we don't have to keep updating the text in every repo
… we just need to update one repo
… it's quite interesting
… i've been going through the issues
… I'll continue to do that
r12a: you start with the lefthand side of the project
addison: do you have links to spec bugs
… like CSS, for example
r12a: yes
… but we add that manually
xfq: x:css-content in https://
r12a: i wonder if i need a css label
… in addition to css-content, css-text etc.
addison: do we have tracker issues?
r12a: yes
<r12a> https://
addison: just as long as it doesn't fly under our radar
… we can discover it
r12a: the review tracker is about WG issues
… this tracker is about language enablement issues
epub
<xfq> https://
xfq: I have a few issues need confirmation by group, resolved or not
<xfq> https://
xfq: 1st, review issue, WG edited and raised PR
… for length of path names
… no specific behavior
<addison> https://
r12a: could be from legacy system's constraints
addison: three points
… path should be UTF-8, could have bunch of restrictions
… if UTF-8 multibytes encoding, with long character, what will happen for mid-character truncation
r12a: truncation should be another issue?
addison: RS could stop processing at some truncated point?
jck: character allocation could happen in in various places,
… truncated characters could happen in somewhere [....]
… truncation by system could happen, and stored as truncated could happen
[talks and what happened from old histories and systems...]
addison: I don't have issue on limitation, but how to handle truncated ones
r12a: could not find any text about truncated text in spec
… another sentence or note states, on mid-character cut
addison: text should state truncation should not occur on in-mid-of-character
r12a: this is for truncation by application, longer than 255 bytes
<xfq> +1
r12a: and in the middle of character
xfq: seems good
<xfq> https://
<xfq> https://
<xfq> https://
xfq: next one is 'Group non characters in character restrictions', on various unicode code points and their restrictions
… they removed mention about arabic presentation form A, all unicode non-characters, BMP, supplimentaly planes. (see detail in PR)
addison: national flags in emojis?
r12a: really used?
addison: to be used as country indicator?
xfq: didn't mention about that code points
addison: I can take action
xfq: they opened PR on typos, presentation form A, etc.
addison: seems reasonal (on PR)
<xfq> https://
xfq: last issue, on char-mod related, which was discussed two weeks before, case folding and nomalization
<xfq> https://
<xfq> https://
xfq: they changed with referring unicode TR#15, charmod-norm
… in the last paragraph of a link, right before note
addison: +1
david: +1
addison: not wanted to be referenced charmod-norm, since it's not in rec-track
[something on editing progress on charmod-norm]
addison: works, except for edge cases
… they normalize and case fold
xfq: any idea for proposal
addison: propose to use our update under consideration
… after this meeting, document should be out
r12a: need to write charmod-norm with updated text first, before sending a comment to them
addison: will do editing
xfq: should publish charmod-norm to /TR/
addison: probably next week or so
AOB?
addison: refund 30sec to all!