[minutes] Internationalization telecon 2024-05-09

https://www.w3.org/2024/05/09-i18n-minutes.html





text version:

                              – DRAFT –
            Internationalization Working Group Teleconference

09 May 2024

    [2]Agenda. [3]IRC log.

       [2] 
https://www.w3.org/events/meetings/6d544156-352c-46f2-b6ec-383b4e2462fb/20240509T150000/
       [3] https://www.w3.org/2024/05/09-i18n-irc

Attendees

    Present
           Addison, Atsushi, Fuqiao, JcK, Richard

    Regrets
           Bert

    Chair
           Addison Phillips

    Scribe
           atsushi

Contents

     1. [4]Agenda Review
     2. [5]Action Items
     3. [6]Info Share
     4. [7]RADAR Review
     5. [8]Adlam and N'Ko LReq documents
     6. [9]HTML input type=email
     7. [10]Review `needs-resolution` and `needs-attention` issues
     8. [11]AOB?
     9. [12]String-meta bps for consumers
    10. [13]Summary of action items
    11. [14]Summary of resolutions

Meeting minutes

   Agenda Review

   Action Items

    <addison> #93

    <gb> [15]Action 93 create best practices for consumers in
    string-meta (on aphillips) due 2024-04-25

      [15] https://github.com/w3c/i18n-actions/issues/93

    addison: in agenda item

    <addison> #90

    <gb> [16]Action 90 steal some of henri's text from
    scroll-to-text-fragment for string-search (on aphillips) due
    2024-04-18

      [16] https://github.com/w3c/i18n-actions/issues/90

    <addison> #87

    <gb> [17]Action 87 write to IETF ADs about RFC9457 with JcK's
    assistance (on aphillips) due 2024-04-04

      [17] https://github.com/w3c/i18n-actions/issues/87

    addison: #90, haven't published yet

    <addison> #79

    <gb> [18]Action 79 schedule a follow-up call with WHATNOT in
    ~April (on aphillips) due 2024-03-07

      [18] https://github.com/w3c/i18n-actions/issues/79

    addison: #87, haven't submitted yet

    <addison> #78

    <gb> [19]Action 78 compare infra to i18n-glossary export list
    and report back (on aphillips) due 2024-03-07

      [19] https://github.com/w3c/i18n-actions/issues/78

    addison: #79, will get date for meeting

    addison: #78, will back as agenda

    <addison> #43

    <gb> [20]Action 43 pull together the list of win/mac/etc apis
    for setting base direction and/or language (on aphillips) due
    2023-09-18

      [20] https://github.com/w3c/i18n-actions/issues/43

    <addison> #33

    <gb> [21]Action 33 Close issues marked `close?` or bring to WG
    for further review (on aphillips)

      [21] https://github.com/w3c/i18n-actions/issues/33

    addison: #49, drafted and article done

    <gb> [22]CLOSED Action 49 contact unicode about emphasis mark
    skipping (on aphillips) due 2023-10-05

      [22] https://github.com/w3c/i18n-actions/issues/49

    <addison> #12

    <gb> [23]Action 12 Upgrade/edit the explainer to address issues
    raised by google (on aphillips) due 18 Jul 2023

      [23] https://github.com/w3c/i18n-actions/issues/12

    addison: #33, needs attention on close?, and will touch later
    today

    addison: #12, explainer done, and would want to close
    … need agenda item to review updates?

    ACTION: addison: add explainer to next week's agenda

    xfq: works for me

    <gb> Created [24]action #97

      [24] https://github.com/w3c/i18n-actions/issues/97

    <addison> #8

    <gb> [25]Action 8 Follow up on the status of Canvas and
    formatted text (on aphillips) due 18 Jul 2023

      [25] https://github.com/w3c/i18n-actions/issues/8

    <addison> #7

    <gb> [26]Action 7 Remind shepherds to tend to their awaiting
    comment resolutions (Evergreen) (on aphillips, xfq, himorin,
    r12a, bert-github) due 18 Jul 2023

      [26] https://github.com/w3c/i18n-actions/issues/7

    addison: seen no action for #7
    … character markup on bikeshed/respec?

    r12a: haven't heard anything yet

    <addison> #96

    <gb> [27]Action 96 evaluate and where necessary fix
    i18n-glossary#76 (on r12a) due 2024-05-02

      [27] https://github.com/w3c/i18n-actions/issues/96

    <addison> #94

    <gb> [28]Action 94 send jck the text from proposed idn section
    to jck for suggestions (on xfq) due 2024-05-02

      [28] https://github.com/w3c/i18n-actions/issues/94

    xfq: #94, done via email

    <addison> close #94

    <gb> Closed [29]issue #94

      [29] https://github.com/w3c/i18n-actions/issues/94

    <addison> #89

    <gb> [30]Action 89 update i18n specs to support dark mode (on
    xfq) due 2024-04-18

      [30] https://github.com/w3c/i18n-actions/issues/89

    xfq: #89, blocked by CSS spec issue, mediaquery doesn't sync
    html meta color scheme
    … need to fix spec and browser first

    <addison> #4

    addison: keep item for now

    <gb> [31]Action 4 Work with respec and bikeshed to provide the
    character markup template as easy-to-use markup (on r12a) due
    27 Jul 2023

      [31] https://github.com/w3c/i18n-actions/issues/4

   Info Share

    <xfq> [32]https://www.w3.org/2002/09/wbs/1/TPAC2024/

      [32] https://www.w3.org/2002/09/wbs/1/TPAC2024/

    xfq: one thing on TPAC survey
    … addison mentioned before, and WBS is due by May 20

    addison: already filed

   RADAR Review

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

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

    addison: Web translation API explainer from WICG

    xfq: will ask PLH for request/coordination

    addison: this is early review opportunity

    xfq: looks like spec really relevant to us

    addison: by 6 June?

    addison: would invite everyone to review web translation api

   Adlam and N'Ko LReq documents

    r12a: wanted to check whether FPDNote of Adlam, N'Ko is update

    r12a: Adlam links to type samples in repositories, of W3C and
    myself

    <addison> MOTION: publish Adlam Layout Requirements as FPWD

    <r12a> +1

    <xfq> +1

    <addison> +1

    +1

    RESOLUTION: publish Adlam Layout Requirements as FPWD

   HTML input type=email

    addison: many flow on thread of this, JcK and I triggered email
    offline
    … problem is PR made by me fixed, but at old machine
    … took time but update this PR
    … bunch of discussions what restriction we need to place on
    implementation

   Review `needs-resolution` and `needs-attention` issues

    <addison> [34]https://github.com/w3c/i18n-activity/
    issues?q=is%3Aissue+is%3Aopen+label%3Aneeds-attention

      [34] 
https://github.com/w3c/i18n-activity/issues?q=is:issue+is:open+label:needs-attention

    addison: need-resolution and needs-attention are left for this
    week
    … 14 needs-attention are left

    <addison> #1783

    <gb> Issue 1783 not found

    <addison> [35]i18n-activity#1783

      [35] https://github.com/w3c/i18n-activity/issues/1783

    <gb> [36]Issue 1783 CSS `text-spacing` property and its
    longhands (by w3cbot) [close?] [tracker] [s:css-text]
    [needs-attention] [tag-tracker] [other:tag]

      [36] https://github.com/w3c/i18n-activity/issues/1783

    r12a: getting to it, constantly back to many CSS issues. it
    will take a while

    <addison> [37]i18n-activity#1763

      [37] https://github.com/w3c/i18n-activity/issues/1763

    <gb> [38]Issue 1763 Make computation of directionality account
    for Shadow DOM. (by w3cbot) [close?] [tracker] [s:html]
    [needs-attention] [i:bidirectional_text] [alreq] [hlreq]
    [t:bidi_markup] [whatwg]

      [38] https://github.com/w3c/i18n-activity/issues/1763

    <addison> [39]whatwg/html#9796

      [39] https://github.com/whatwg/html/issues/9796

    <gb> [40]MERGED Pull Request 9796 Make computation of
    directionality account for Shadow DOM. (by dbaron)
    [addition/proposal] [topic: shadow] [i18n-tracker] [i18n-alreq]
    [i18n-hlreq]

      [40] https://github.com/whatwg/html/pull/9796

    addison: not sure what to say, but anyone to review?

    <addison> [41]i18n-activity#1758

      [41] https://github.com/w3c/i18n-activity/issues/1758

    <gb> [42]Issue 1758 Reference for punycode-encoding of IDN (by
    w3cbot) [tracker] [needs-attention] [s:rdf-concepts]
    [wg:rdf-star]

      [42] https://github.com/w3c/i18n-activity/issues/1758

    addison: no comment to review, will close #1763

    <gb> Issue 9896 not found

    <addison> [43]i18n-activity#1620

      [43] https://github.com/w3c/i18n-activity/issues/1620

    <gb> [44]Issue 1620 [focusgroup] i18n: should arrow key
    navigation follow text direction? (by w3cbot) [close?]
    [tracker] [needs-attention] [s:open-ui] [cg:open-ui]

      [44] https://github.com/w3c/i18n-activity/issues/1620

    <addison> [45]https://lists.w3.org/Archives/Public/
    public-i18n-core/2024JanMar/0099.html

      [45] 
https://lists.w3.org/Archives/Public/public-i18n-core/2024JanMar/0099.html

    addison: #1620, some discussion recently, email above

    <gb> Issue 1620 not found

    xfq: for #1763, any action to do? JcK comment submitted for
    punycode

    <gb> Issue 1763 not found

    xfq: I believe current comment could be enough, this is not
    only issue for them

    xfq: will check spec and context, and will comment for this
    … to prevent A-labels, need to specifically mention about it

   AOB?

   String-meta bps for consumers

    <addison> [46]w3c/string-meta#87

      [46] https://github.com/w3c/string-meta/pull/87

    <gb> [47]Pull Request 87 Create best practices for consumers
    (by aphillips)

      [47] https://github.com/w3c/string-meta/pull/87

    <addison> [48]https://
    deploy-preview-87--string-meta.netlify.app/#bp-consumers

      [48] 
https://deploy-preview-87--string-meta.netlify.app/#bp-consumers

    addison: added mustards on this point

    r12a: why do we need to normalize language tags?

    addison: among other things, Unicode orders extensions, and
    some obsolete tags replaced

    xfq: if most people does not normalize, probabry we can remove
    this guidance

    [BCP47 registry and its forms]

Summary of action items

     1. [49]addison: add explainer to next week's agenda

Summary of resolutions

     1. [50]publish Adlam Layout Requirements as FPWD

Received on Friday, 10 May 2024 00:50:05 UTC