[minutes] Internationalization telecon 2021-08-19

https://www.w3.org/2021/08/19-i18n-minutes.html












– DRAFT –
            Internationalization Working Group Teleconference

19 August 2021

    [2]Agenda. [3]IRC log.

       [2] https://lists.w3.org/Archives/Member/member-i18n-core/2021Aug/0009.html
       [3] https://www.w3.org/2021/08/19-i18n-irc

Attendees

    Present
           Addison, Atsushi, Bert, Felix, Fuqiao, JcK, r12a

    Regrets
           -

    Chair
           Addison Phillips

    Scribe
           xfq

Contents

     1. [4]Agenda Review
     2. [5]Action Items
     3. [6]Info Share
     4. [7]RADAR Review
     5. [8]Remove links to Encoding tests in i18n test suite
     6. [9]IPv6 Zone identifiers, i18n, and URIs
     7. [10]"Awaiting Comment Resolution" reviews
     8. [11]AOB?
     9. [12]Summary of action items

Meeting minutes

    <addison> trackbot, prepare teleconference

   Agenda Review

    addison: anything else to add to the agenda?

   Action Items

    <addison> [13]https://www.w3.org/International/track/actions/
    open

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

    <addison> action-1050?

    <trackbot> [14]action-1050: Addison Phillips to Merge
    string-meta changes pending richard's review of the glossary
    changes -- due 2021-07-22 -- OPEN

      [14] https://www.w3.org/International/track/actions/1050

    <addison> close action-1050

    <trackbot> Closed action-1050.

    <addison> action-1055?

    <trackbot> [15]action-1055: Addison Phillips to Publish
    localizable-manifests as fpwd with help from richard -- due
    2021-08-05 -- OPEN

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

    addison: "Publish localizable-manifests as fpwd with help from
    richard" is not quite done but I think we're in good shape,
    mostly thanks to Richard

   Info Share

    <atsushi> [16]https://github.com/CITPCSHARE/UAX50/wiki/
    Request-to-revise-UAX-50-for-the-harmonization-with-Adobe-Japan
    1

      [16] https://github.com/CITPCSHARE/UAX50/wiki/Request-to-revise-UAX-50-for-the-harmonization-with-Adobe-Japan1

    atsushi: discrepancy between UAX 50 and Adobe-Japan1
    … 4 code points
    … any comment is welcome
    … the discussions were in Japanese, but the conclusion in this
    document is in English

    addison: is this somewhat final?

    atsushi:

    Japanese Character Information Technology Promotion Council

    <atsushi> [17]https://moji.or.jp/

      [17] https://moji.or.jp/

    atsushi: CITPC
    … will send it to the UTC

    r12a: it would be good at least to say somewhere in this
    proposal that it is developed by the jlreq TF in W3C

    addison: the power of standards is that you can get support
    from a wider community

    atsushi: let me propose to the TF chair, Kida-san

    atsushi: Tatsuo Kobayashi is managing CITPC

    r12a: not everyone in CITPC is a participant of i18n WG/IG
    … will it be sent to the Unicode Consortium?

    atsushi: yes

    Action: atsushi: follow up on CITPC/JLTF request to UTC about 4
    characters and bring doc for review by WG when ready

    <trackbot> Created ACTION-1060 - Follow up on citpc/jltf
    request to utc about 4 characters and bring doc for review by
    wg when ready [on Atsushi Shimono - due 2021-08-26].

    r12a: I'm now not only on the Unicode Editorial Committee, but
    also on the Script Ad Hoc Group

   RADAR Review

    <addison> [18]https://github.com/w3c/i18n-request/projects/1

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

    xfq: no comment on CSS Masking Module Level 1

   Remove links to Encoding tests in i18n test suite

    <r12a> [19]https://www.w3.org/International/
    i18n-tests/#encoding-spec

      [19] https://www.w3.org/International/i18n-tests/#encoding-spec

    r12a: somebody raised an issue recently
    … the tests in wpt and i18n-tests are not consistent
    … keeping them in sync takes hours and hours

    addison: they're mostly tests for truly dead legacy encodings
    … I have no objections since WHATWG is maintaining the Encoding
    Standard

    Action: richard: remove encoding tests and put a link to wpt
    tests

    <trackbot> Created ACTION-1061 - Remove encoding tests and put
    a link to wpt tests [on Richard Ishida - due 2021-08-26].

   IPv6 Zone identifiers, i18n, and URIs

    JcK: ipv6 tries to eliminate NAT mapping

    JcK: they have been trying to look at what WHATWG is doing
    … URI and IRI as @@ understands them, and URL as WHATWG
    understands them

    addison: if they're going to allow non-ascii address they have
    to address all the considerations in IDNA addresses

    JcK: yes

    addison: what WHATWG is doing is trying to describe what the
    browsers do
    … I suppose browsers support this

    addison: i guess as a WG we just kind of wait for them to
    respond
    … i can't think of any other actions

   "Awaiting Comment Resolution" reviews

    <addison> [20]https://github.com/w3c/i18n-activity/
    issues?q=is%3Aissue+is%3Aopen+label%3As%3Aintersection-observer

      [20] https://github.com/w3c/i18n-activity/issues?q=is:issue+is:open+label:s:intersection-observer

    <addison> keep spec open

    <addison> [21]https://github.com/w3c/i18n-activity/
    issues?q=is%3Aissue++label%3As%3Acss-text-decor

      [21] https://github.com/w3c/i18n-activity/issues?q=is:issue++label:s:css-text-decor

    addison: do we need someone to look at them more closely?

    Action: richard: review open css-text-decor issues for close or
    escalation

    <trackbot> Created ACTION-1062 - Review open css-text-decor
    issues for close or escalation [on Richard Ishida - due
    2021-08-26].

    r12a: i'll do it

    <addison> [22]https://github.com/w3c/i18n-activity/
    issues?q=is%3Aissue++label%3As%3Acss-align

      [22] https://github.com/w3c/i18n-activity/issues?q=is:issue++label:s:css-align

    <addison> [23]https://github.com/w3c/i18n-activity/
    issues?q=is%3Aissue++label%3As%3Avocab-dcat+is%3Aopen

      [23] https://github.com/w3c/i18n-activity/issues?q=is:issue++label:s:vocab-dcat+is:open

    addison: vocab-dcat
    … two open issues

    r12a: back to css-align

    [24]https://github.com/w3c/i18n-activity/issues/473

      [24] https://github.com/w3c/i18n-activity/issues/473

    addison: it's closed

    fsasaki: I can take a look at vocab-dcat

    [25]https://github.com/w3c/i18n-activity/issues/709

      [25] https://github.com/w3c/i18n-activity/issues/709

    addison: we requested some health warning on references to
    ISO-639 vs. BCP47

    Action: addison: respond to vocab-dcat issues pinging for
    updates

    <trackbot> Created ACTION-1063 - Respond to vocab-dcat issues
    pinging for updates [on Addison Phillips - due 2021-08-26].

    Action: felix: propose health warning text on vocab-dcat and
    language

    <trackbot> Created ACTION-1064 - Propose health warning text on
    vocab-dcat and language [on Felix Sasaki - due 2021-08-26].

    addison: they said they would create a draft PR in Oct 2019 but
    there doesn't seem to be one

    <addison> [26]https://github.com/w3c/i18n-activity/
    issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+label%3As%3Alow-vi
    sion-needs

      [26] https://github.com/w3c/i18n-activity/issues?utf8=✓&q=is:issue+is:open+label:s:low-vision-needs

    addison: low-vision-needs
    … reviewed in 2017

    addison: should i ping the WG to see if they intend to progress
    this further?

    Action: addison: ping a11y to see if they intend to progress
    low-vision-needs

    <trackbot> Created ACTION-1065 - Ping a11y to see if they
    intend to progress low-vision-needs [on Addison Phillips - due
    2021-08-26].

    <addison> [27]https://github.com/w3c/i18n-activity/
    issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+label%3As%3Alow-vi
    sion-needs

      [27] https://github.com/w3c/i18n-activity/issues?utf8=✓&q=is:issue+is:open+label:s:low-vision-needs

    JcK: low vision @@ font families

    <addison> [28]https://github.com/w3c/i18n-activity/
    issues?q=is%3Aissue+is%3Aopen+label%3As%3Ajson-ld

      [28] https://github.com/w3c/i18n-activity/issues?q=is:issue+is:open+label:s:json-ld

    addison: JSON-LD
    … we spent a lot of effort
    … they did a bunch of work for us
    … should we close this and call that review completed?

    <fsasaki> +1

    <atsushi> +1

    <addison> [29]https://github.com/w3c/i18n-activity/
    issues?utf8=%E2%9C%93&q=is%3Aissue+label%3As%3Apronunciation-ga
    p-analysis+is%3Aopen

      [29] https://github.com/w3c/i18n-activity/issues?utf8=✓&q=is:issue+label:s:pronunciation-gap-analysis+is:open

    r12a: shall I close them?

    addison: yes, please

    addison: this one's gonna be fun
    … published as a working group note
    … though these four issues have not been addressed

    r12a: is the note the end target?

    addison: it's called Pronunciation Gap Analysis
    … so I guess it's the end status

    r12a: whether we need to port these comments to the WD

    addison: i don't think we have reviewed that doc

    Action: richard: move pronunciation-gap-analysis issues to new
    document

    <trackbot> Created ACTION-1066 - Move
    pronunciation-gap-analysis issues to new document [on Richard
    Ishida - due 2021-08-26].

   AOB?

    <r12a> [30]https://www.w3.org/wiki/TPAC/2021/GroupMeetings

      [30] https://www.w3.org/wiki/TPAC/2021/GroupMeetings

    r12a: set a time for TPAC meeting

    addison: i'll add an agenda item next week to discuss that

    r12a: probably be several meetings

    [adjourned]

Summary of action items

     1. [31]atsushi: follow up on CITPC/JLTF request to UTC about 4
        characters and bring doc for review by WG when ready
     2. [32]richard: remove encoding tests and put a link to wpt
        tests
     3. [33]richard: review open css-text-decor issues for close or
        escalation
     4. [34]addison: respond to vocab-dcat issues pinging for
        updates
     5. [35]felix: propose health warning text on vocab-dcat and
        language
     6. [36]addison: ping a11y to see if they intend to progress
        low-vision-needs
     7. [37]richard: move pronunciation-gap-analysis issues to new
        document

Received on Thursday, 19 August 2021 16:25:55 UTC