[minutes] Internationalization telecon 2024-06-06

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





text version:

                              – DRAFT –
            Internationalization Working Group Teleconference

06 June 2024

    [2]Agenda. [3]IRC log.

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

Attendees

    Present
           Addison, Atsushi, JcK, Richard

    Regrets
           Fuqiao

    Chair
           Addison Phillips

    Scribe
           addison, atsushi

Contents

     1. [4]Agenda Review
     2. [5]Action Items
     3. [6]Info Share
     4. [7]RADAR Review
     5. [8]Pending Issue Review
     6. [9]Kashmiri/Uighur/Urdu FPWD
     7. [10]String direction APIs
     8. [11]String-Meta Consumer guidance PR
     9. [12]Kashmiri/Uighur/Urdu FPWD
    10. [13]AOB?
    11. [14]Summary of action items
    12. [15]Summary of resolutions

Meeting minutes

   Agenda Review

    addison: got one additional item from r12a
    … anything else?

   Action Items

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

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

    #103

    <gb> [17]Action 103 Migrate RADAR project (on aphillips)

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

    #102

    <gb> [18]Action 102 ping alreq group to review our
    i18n-activity#1620 (on aphillips) due 2024-05-30

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

    #100

    <gb> [19]Action 100 complain to plh about the new IRC tool (on
    aphillips) due 2024-05-30

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

    close #100

    <gb> Closed [20]issue #100

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

    r12a: irc client looks similar to webirc one

    #99

    <gb> [21]Action 99 ping unicode about emphasis skip property
    (see our #530) (on aphillips) due 2024-05-28

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

    #98

    <gb> [22]Action 98 fix code points examples in
    lang-bidi-use-cases (on r12a) due 2024-05-23

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

    #96

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

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

    #93

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

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

    #90

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

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

    #89

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

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

    #87

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

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

    addison: did while ago, and replied on thread and waiting for
    reply

    #79

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

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

    #78

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

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

    #43

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

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

    addison: done for PR, and agenda later

    #33

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

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

    #8

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

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

    #7

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

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

    #4

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

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

    addison: will write to them on this

    ACTION: addison: follow up on [35]action#4 by writing an email

      [35] https://github.com/w3c/action/issues/4

    <gb> Created [36]action #104

      [36] https://github.com/w3c/i18n-actions/issues/104

   Info Share

    JcK: discussion going at IETF, on strings and characters
    … language and direction information
    … discussion for screen reader and a11y point of view
    … explained in explainer, basically direction by user
    … would bring recommendations from IETF and W3C

    addison: email thread flows
    … will probably suggest some discussion for reasonable
    resolution

    r12a: talk at June 25th
    … called bidi text, organized by Unicode

    <r12a> Bidirectional Text (Part 1): The Basics of Bidi

    <r12a> Date & Time Jun 25, 2024 04:00 PM London

    r12a: you need to register from URL

    <r12a> [37]https://blog.unicode.org/2024/05/
    new-event-on-june-25-webinar-on.html

      [37] 
https://blog.unicode.org/2024/05/new-event-on-june-25-webinar-on.html

   RADAR Review

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

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

    addison: two new incoming

    addison: will take device posture

    atsushi: will take controlers documents

    addison: under review, waiting for input
    … web translation api, couple of pending issues

    r12a: nothing for html ruby extension, but need to check around

    addison: web principles and baggages are moved to completed,
    since all issues resolved

   Pending Issue Review

    [39]https://github.com/w3c/i18n-activity/
    issues?q=is%3Aissue+is%3Aopen+label%3Apending

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

    [40]i18n-activity#1856

      [40] https://github.com/w3c/i18n-activity/issues/1856

    <gb> [41]Issue 1856 language tag handling needs more attention
    (by aphillips) [pending] [needs-resolution] [s:translation-api]

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

    addison: language tag issue
    … high level handling is #1856

    <gb> Issue 1856 not found

    +1

    [all agrees]

    [42]i18n-activity#1855

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

    <gb> [43]Issue 1855 `canTranslate` values `no`, `readily` and
    `afterDownload` are not internationalized? (by aphillips)
    [pending] [needs-resolution] [s:translation-api]

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

    r12a: in language tag examples, there are bad examples

    addison: this is naming of values

    r12a: no strong feelings.

    addison: would have some conversations with this group

    r12a: IETF question was for 14th Ul /04

   Kashmiri/Uighur/Urdu FPWD

    Perso-arabic Kashmiri [44]https://w3c.github.io/alreq/arab-ks/
    index.html

      [44] https://w3c.github.io/alreq/arab-ks/index.html

    Uighur [45]https://w3c.github.io/alreq/arab-ug/index.html

      [45] https://w3c.github.io/alreq/arab-ug/index.html

    Urdu [46]https://w3c.github.io/alreq/arab-ur/index.html

      [46] https://w3c.github.io/alreq/arab-ur/index.html

    publish arab-ks, arab-ug, and arab-ur as FPWD?

    <r12a> +1

    +1

    jck: +1

   String direction APIs

    [47]w3c/i18n-drafts#586

      [47] https://github.com/w3c/i18n-drafts/pull/586

    <gb> [48]Pull Request 586 Publish a list of APIs for setting
    language and direction in native code (by aphillips)

      [48] https://github.com/w3c/i18n-drafts/pull/586

   String-Meta Consumer guidance PR

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

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

    r12a: bdi, and isolation, problem you don't actually know
    without metadata
    … you should have direction via bdi tag

    You are reading <span id="title"></span>

    addison: above example, you need to decorate using span for
    parts
    … similar to message format one

    addison: not like bdi, span wont isolate things

    <r12a> getElementById('title') = `You are reading:
    <bdi>{$title}</bdi>`

    r12a: default sinario to have bdi, but even if not you should
    have dir for changing direction

    addison: depends on situation, you should have bdi, direction
    or auto

    r12a: will read carefully

    addison: discussed last week, and to have examples. and added
    some here

   Kashmiri/Uighur/Urdu FPWD

    r12a: plain text example is not identical to html one

    +1 for FPWD

    addison: back to FPWDs, and resolved

    RESOLUTION: publish arab-ks, arab-ug, and arab-ur as FPWD

   AOB?

    ACTION: ri: Review [50]https://
    deploy-preview-87--string-meta.netlify.app/#bp-consumers

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

    <gb> Created [51]action #105

      [51] https://github.com/w3c/i18n-actions/issues/105

Summary of action items

     1. [52]addison: follow up on action#4 by writing an email
     2. [53]ri: Review https://
        deploy-preview-87--string-meta.netlify.app/#bp-consumers

Summary of resolutions

     1. [54]publish arab-ks, arab-ug, and arab-ur as FPWD

Received on Friday, 7 June 2024 02:07:52 UTC