[minutes] Internationalization telecon 2017-06-01

https://www.w3.org/2017/06/01-i18n-minutes.html




text version follows:


Internationalization Working Group Teleconference

01 Jun 2017

    [2]Agenda

       [2] 
https://lists.w3.org/Archives/Member/member-i18n-core/2017May/0032.html

    See also: [3]IRC log

       [3] http://www.w3.org/2017/06/01-i18n-irc

Attendees

    Present
           Addison, David, Jan, Andrew, andrewc, JcK

    Regrets
           Steven, Bert

    Chair
           Addison Phillips

    Scribe
           addison

Contents

      * [4]Topics
          1. [5]Agenda
          2. [6]Action Items
          3. [7]Info Share
          4. [8]Radar
          5. [9]unicode discussion on U+FFFD generation
          6. [10]Review of qa-floating-times
          7. [11]review and close Charmod-norm issues
          8. [12]AOB?
      * [13]Summary of Action Items
      * [14]Summary of Resolutions
      __________________________________________________________

    trackbot, prepare teleconference

    <scribe> ScribeNick: addison

Agenda

Action Items

    [15]https://www.w3.org/International/track/actions/open

      [15] 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>
    [16]http://www.w3.org/International/track/actions/621

      [16] http://www.w3.org/International/track/actions/621

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

      [17] 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

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

      [18] 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
    [19]http://www.w3.org/2017/06/01-i18n-minutes.html#action01]

      [19] 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

    [20]http://w3c.github.io/i18n-drafts/questions/qa-floating-time
    s.en

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

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

      [21] https://github.com/w3c/i18n-drafts/issues/44

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

      [22] 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

    [23]https://github.com/w3c/charmod-norm/issues

      [23] https://github.com/w3c/charmod-norm/issues

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

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

    [25]http://w3c.github.io/charmod-norm/

      [25] http://w3c.github.io/charmod-norm/

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

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

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

      [27] 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.

    [28]http://www.unicode.org/reports/tr18/#Tailored_Support

      [28] http://www.unicode.org/reports/tr18/#Tailored_Support

    addison: will close close? and update the regex issue

AOB?

Summary of Action Items

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

      [29] http://www.w3.org/2017/06/01-i18n-minutes.html#action01

Summary of Resolutions

    [End of minutes]

Received on Thursday, 8 June 2017 18:15:12 UTC