[minutes] Internationalization telecon 2023-08-24

https://www.w3.org/2023/08/24-i18n-minutes.html





text version:

                              – DRAFT –
                  Internationalization WG Teleconference

24 August 2023

    [2]Agenda. [3]IRC log.

       [2] 
https://www.w3.org/events/meetings/c5b143d1-0a5b-4adb-8d60-0f5f9bfe5a41/20230824T150000/
       [3] https://www.w3.org/2023/08/24-i18n-irc

Attendees

    Present
           Addison, Atsushi, Fuqiao, JcK

    Regrets
           -

    Chair
           Addison Phillips

    Scribe
           addison, xfq

Contents

     1. [4]Agenda Review
     2. [5]Action Items
     3. [6]Info Share
     4. [7]RADAR Review
     5. [8]WCAG 2.2
     6. [9]I18N+CSS
     7. [10]name-like fields
     8. [11]TPAC
     9. [12]AOB?
    10. [13]Summary of action items

Meeting minutes

   Agenda Review

   Action Items

    <addison> gb, list open actions

    <gb> Found actions in w3c/i18n-actions: #35, #34, #33, #32,
    #18, #16, #15, #13, #12, #11, #10, #9, #8, #7, #6, #5, #4

    <addison> #35?

    <gb> [14]Action 35 make the edits of CSS #5478 (on fantasai)
    due 2023-08-30

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

    <addison> #34?

    <gb> [15]Action 34 write summary email showing path forward for
    WCAG 2.2 (on aphillips) due 2023-08-24

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

    <addison> close #34

    <addison> #33?

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

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

    <gb> Closed [17]action #34

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

    <addison> #32?

    <gb> [18]Action 32 Approve the character markup PR (on
    fantasai) due 2023-08-17

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

    addison: started #34

    <addison> #18?

    <gb> [19]Action 18 Have informal explanation sessions about
    counter style translations with csswg members (on frivoal,
    fantasai)

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

    <addison> #16?

    <gb> [20]Action 16 Keep track of line-breaking in Korean for
    i18n-discuss#11 (on aphillips)

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

    <addison> #15?

    <gb> [21]Action 15 Get character styling into w3c stylesheet
    (on aphillips)

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

    xfq: fantasai will look at the latest revision of the character
    markup PR

    <addison> #13?

    <gb> [22]Action 13 Make sure generics are comfortable to read
    in the content language (on frivoal)

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

    <addison> #12?

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

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

    <addison> #11?

    <gb> [24]Action 11 Triage all css properties to determine which
    are logical, physical, or na by default (on frivoal)

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

    <addison> #10?

    <gb> [25]Action 10 With florian triage richard's article into a
    list of potential generics (on fantasai)

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

    <addison> #9?

    <gb> [26]Action 9 Follow up with ecma-402 on next steps and
    start tc39 discussion (on aphillips)

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

    <addison> #8

    <gb> [27]Action 8 Create pr against canvas formatted text (on
    aphillips)

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

    <addison> #7?

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

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

    <addison> #6

    <gb> [29]Action 6 Check if unicode describes backwards deletion
    clearly and develop doc if not (on aphillips)

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

    <addison> [30]https://w3c.github.io/i18n-drafts/questions/
    qa-backwards-deletion.en.html

      [30] 
https://w3c.github.io/i18n-drafts/questions/qa-backwards-deletion.en.html

    o/

    addison: this is ready for review

    <addison> #5

    <gb> [31]Action 5 Check into how to list questions at the top
    of a digest and/or improve lang enablement communications (on
    r12a)

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

    addison: please send comments

    <addison> #4

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

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

   Info Share

   RADAR Review

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

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

    addison: no new incoming requests
    … no items in review

    xfq: First Public Working Draft published: Catalan Gap Analysis

   WCAG 2.2

    addison: I don't know if any of you guys know what the status
    of the formal objections from Japan
    … or from China

    ACTION: addison to follow up with murata-san about wcag status

    <gb> Created [34]action #36

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

    addison: I'd like to avoid a formal objection if it's not going
    to make sense to have one

    xfq: they're already sending PRs, we'll see how it goes

    addison: I think we need to probably formally review them

   I18N+CSS

    [35]https://www.w3.org/2023/08/23-i18n-minutes.html

      [35] https://www.w3.org/2023/08/23-i18n-minutes.html

    [36]w3c/csswg-drafts#8442

      [36] https://github.com/w3c/csswg-drafts/issues/8442

    <addison> xfq: css working on proposal which will help with
    logical properties

    <addison> xfq: css issue ^^ contains a mapping from kana to
    small kana. they want to upstream it to unicode

    addison: I don't think they have a page that says here's the
    mapping
    … but it might be in normalization
    … because you also got the narrow to wide kana
    … you have a whole bunch of that stuff

    ACTION: xfq to investigate the small kana mapping and what if
    anything to recommend to unicode

    <gb> Created [37]action #37

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

    <addison> xfq: should develop an agenda for tpac for joint
    meeting

    <addison> ... don't have an agenda list specifically for tpac

    ACTION: addison to propose i18n+css agenda for tpac

    <gb> Created [38]action #38

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

    <addison> xfq: discussed character markup for styling. fantasai
    disagreed that there should not be a space between the code
    point and character name

    <addison> ... she prefers a space

    [39]w3c/csswg-drafts#5478

      [39] https://github.com/w3c/csswg-drafts/issues/5478

   name-like fields

    [40]w3c/vc-data-model#1252 (comment)

      [40] 
https://github.com/w3c/vc-data-model/pull/1252#issuecomment-1686366538

    addison: we made a comment sometime ago about they have natural
    language text fields
    … name and description
    … and our comment on them was "you should have language and
    direction"
    … "you should probably allow fore more than one of them"
    … because people might want to localize the credential rather
    than having a separate credential in every language on earth
    … Manu added some thing on how to use these fields
    … but didn't mention localization
    … so I made this comment and he addressed it

    ACTION: addison to develop best practice guidelines for
    name-like fields

    <gb> Created [41]action #39

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

   TPAC

    [42]https://github.com/w3c/i18n-actions/wiki/2023-TPAC-Planning

      [42] https://github.com/w3c/i18n-actions/wiki/2023-TPAC-Planning

    addison: I don't have a lot in our TPAC calendar yet
    … I do need to go back and add a couple of things and I have an
    email to respond to from one of the groups

    [43]w3c/webappswg#91 (comment)

      [43] 
https://github.com/w3c/webappswg/issues/91#issuecomment-1646281939

    ACTION: addison to ping webappswg about a joint time on
    monday/tuesday at tpac

    <gb> Created [44]action #40

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

    [45]https://www.w3.org/groups/wg/webapps/

      [45] https://www.w3.org/groups/wg/webapps/

   AOB?

    [46]w3c/i18n-glossary#52

      [46] https://github.com/w3c/i18n-glossary/pull/52

    [47]w3c/i18n-glossary#35

      [47] https://github.com/w3c/i18n-glossary/pull/35

    addison: you're better off quoting them than forking

    xfq: OK
    … I'll update the PR

Summary of action items

     1. [48]addison to follow up with murata-san about wcag status
     2. [49]xfq to investigate the small kana mapping and what if
        anything to recommend to unicode
     3. [50]addison to propose i18n+css agenda for tpac
     4. [51]addison to develop best practice guidelines for
        name-like fields
     5. [52]addison to ping webappswg about a joint time on
        monday/tuesday at tpac

Received on Friday, 25 August 2023 03:25:47 UTC