[minutes] Internationalization telecon 2019-07-25

https://www.w3.org/2019/07/25-i18n-minutes.html





text version:


- DRAFT -

            Internationalization Working Group Teleconference

25 Jul 2019

    [2]Agenda

       [2] 
https://lists.w3.org/Archives/Member/member-i18n-core/2019Jul/0008.html

Attendees

    Present
           Bert, David, Fuqiao, Katy, Richard, addison, atsushi,
           r12a, xfq

    Regrets

    Chair
           Addison Phillips

    Scribe
           addison

Contents

      * [3]Topics
          1. [4]Agenda and Minutes
          2. [5]Action Items
          3. [6]Info Share
          4. [7]RADAR and Active Work Review
          5. [8]Continuing Review of HTML/WhatWG issues
          6. [9]AOB?
      * [10]Summary of Action Items
      * [11]Summary of Resolutions
      __________________________________________________________

    trackbot, prepare teleconference

    <agendabot> clear agenda

    <scribe> scribenick: addison

    <atsushi> (possible regrets for next week, just memo..)

Agenda and Minutes

Action Items

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

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

    action-812?

    <trackbot> action-812 -- Richard Ishida to Investigate
    situation for accesskey including wording and tests and report
    back -- due 2019-07-25 -- OPEN

    <trackbot>
    [13]https://www.w3.org/International/track/actions/812

      [13] https://www.w3.org/International/track/actions/812

Info Share

    <xfq> [14]https://www.w3.org/2019/09/TPAC/travel.html

      [14] https://www.w3.org/2019/09/TPAC/travel.html

    action?

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

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

RADAR and Active Work Review

    <scribe> ACTION: richard: publish tips for linking to headings
    and figures for wide review

    <trackbot> Created ACTION-815 - Publish tips for linking to
    headings and figures for wide review [on Richard Ishida - due
    2019-08-01].

    richard: working on article on making LTR text appear/display
    RTL
    ... such as chinese or (ancient) egyptian
    ... still a few little things to do

Continuing Review of HTML/WhatWG issues

    <r12a> [16]https://github.com/w3c/i18n-activity/issues/719

      [16] https://github.com/w3c/i18n-activity/issues/719

    richard: could us a bit of help
    ... about case sensitivity
    ... the whatwg says "... must be case sensitive..."
    ... wrote exploratory test

    <r12a>
    [17]https://w3c.github.io/i18n-tests/html/editing/assigning-key
    board-shortcuts/the-accesskey-attribute/exp_accesskey_000

      [17] 
https://w3c.github.io/i18n-tests/html/editing/assigning-keyboard-shortcuts/the-accesskey-attribute/exp_accesskey_000

    richard: very simple but effective test. type a value and then
    hit with various modifier keys
    ... possible to find keys that are case *IN*sensitive in
    English
    ... haven't done windows
    ... greek, different results in FF and safari
    ... safari case sensitive
    ... ff doesn't recognize uppercase
    ... examples in doc violate it... most shortcut keys you see
    are "uppercase" but you don't press shift to get

    addison: corner cases if insensitive (turkish)

    david: would accents be stripped?

    richard: how would uppercase e-acute work in french?

    addison: what to do? file or bring in more accesskey issues?

    richard: what to recommend?

    addison: insensitive with health warning?

    richard: waiting on addison to do tests
    ... will submit after we have results

    <r12a> [18]https://github.com/w3c/i18n-activity/issues/720

      [18] https://github.com/w3c/i18n-activity/issues/720

    richard: one code point issue
    ... how many code points can you have? our question was: why
    restriction?
    ... restrict value to single keypress instead?
    ... some keyboards have keys that produce multiple code points.
    Burmese, Devanagari
    ... safari, chrome quite happily accept those keys as
    accesskeys

    addison: they're trying to convey the concept rather than a
    tech requirement
    ... submit?

    richard: okay
    ... summarize at end

    <r12a> [19]https://github.com/w3c/i18n-activity/issues/521

      [19] https://github.com/w3c/i18n-activity/issues/521

    <xfq> New abstract:
    [20]https://github.com/w3c/csswg-drafts/issues/3829#issuecommen
    t-513590636

      [20] 
https://github.com/w3c/csswg-drafts/issues/3829#issuecomment-513590636

    <scribe> New abstract reads: CSS Writing Modes Level 3 defines
    CSS support for various writing modes and their combinations,
    including left-to-right and right-to-left text ordering as well
    as horizontal and vertical orientations.

    <atsushi> +1 to close

    RESOLUTION: close 521

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

      [21] https://github.com/w3c/i18n-activity/issues/157

    richard: raise as a question?

    <scribe> ACTION: richard: raise issue 157 with whatwg as a
    question

    <trackbot> Created ACTION-816 - Raise issue 157 with whatwg as
    a question [on Richard Ishida - due 2019-08-01].

AOB?

Summary of Action Items

    [NEW] ACTION: richard: publish tips for linking to headings and
    figures for wide review
    [NEW] ACTION: richard: raise issue 157 with whatwg as a
    question

Summary of Resolutions

     1. [22]close 521

    [End of minutes]

Received on Thursday, 25 July 2019 15:38:15 UTC