trackbot, prepare teleconference

<scribe> ScribeNick: addison

Agenda

Action Items

https://www.w3.org/International/track/actions/open

action-621?

<trackbot> action-621 -- Addison Phillips to File additional issue on imsc related to font selection and "recommended character sets" section -- due 2017-06-01 -- OPEN

<trackbot> http://www.w3.org/International/track/actions/621

https://github.com/w3c/i18n-activity/issues/420

addison: need to file this to them

richard: still filing a few, need to understand jck's comments and incorp

addison: will file this one unless objections

Info Share

Radar

https://github.com/w3c/i18n-activity/projects/1

<r12a> w3c.github.io/i18n-activity/reviews/#poe

<scribe> ACTION: richard: forward poe/ordl comments on behalf of bert [recorded in http://www.w3.org/2017/06/01-i18n-minutes.html#action01]

<trackbot> Created ACTION-622 - Forward poe/ordl comments on behalf of bert [on Richard Ishida - due 2017-06-08].

unicode discussion on U+FFFD generation

0xC0.80

-> U+FFFD

-> U+FFFD U+FFFD

0xC0.80.80

0xF4.80.F4.80.80.80

richard: could have an effect on encoding

addison: should be a limited effect, best practice? not required?

richard: tests use fffd in decoding for when things go wrong
... would have an effect for unrecognized sequences for conversion to utf8

addison: encoding spec does each bad byte

david: security impact
... utf8 sequences that were abusive

addison: question is whether we have an opinion?

david: personal opinion that you emit single rather than multiple

addison: tend to prefer only one, but there are solid arguments for multiple

jck: also tend to think reject the entire string

addison: a little weird to have this conversation in 2017; if writing a converter need to handle these cases

Review of qa-floating-times

http://w3c.github.io/i18n-drafts/questions/qa-floating-times.en

<r12a> https://github.com/w3c/i18n-drafts/issues/44

<r12a> https://github.com/w3c/i18n-drafts/issues/66

66 is about the footer

44, mati has a good point

review and close Charmod-norm issues

https://github.com/w3c/charmod-norm/issues

https://github.com/w3c/charmod-norm/issues/54

http://w3c.github.io/charmod-norm/

http://w3c.github.io/charmod-norm/#non-normalizing

http://w3c.github.io/charmod-norm/#non-normalizing

Regular expression syntaxes are sometimes useful in defining a format or protocol, since they allow users to specify values that are only partially known or which can vary. The definition or use of regular expression syntaxes or wildcards when considered over the range of Unicode encoding variations, and particularly when considering character or grapheme boundaries brings with it additional considerations. [S][I] Specifications that define a regular expre[CUT]

[S][I] Specifications that define a regular expression syntax must provide at least Basic Unicode Level 1 support per [UTS18] and should provide Extended or Tailored (Levels 2 and 3) support.

http://www.unicode.org/reports/tr18/#Tailored_Support

addison: will close close? and update the regex issue

AOB?

This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Present: Addison David Jan Andrew andrewc JcK
Regrets: Steven Bert
Found ScribeNick: addison
Inferring Scribes: addison
Agenda: https://lists.w3.org/Archives/Member/member-i18n-core/2017May/0032.html
Found Date: 01 Jun 2017
Guessing minutes URL: http://www.w3.org/2017/06/01-i18n-minutes.html
People with action items: richard