[minutes] Internationalization telecon 2024-02-22

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





text version:

                              – DRAFT –
            Internationalization Working Group Teleconference

22 February 2024

    [2]Agenda. [3]IRC log.

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

Attendees

    Present
           Addison, Atsushi, Bert, Fuqiao, Richard

    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]RADAR Review
     6. [9]Pending Issue Review
     7. [10]String-Meta and the problem of 'paragraph direction'
     8. [11]Follow up on I18N + CSS Call
     9. [12]IDN in Specdev
    10. [13]Prepare for WHATWG Call
    11. [14]AOB?
    12. [15]Summary of action items

Meeting minutes

    <gb> [16]Action 73 make a list of invisible characters to
    support html 5121 discussion (on r12a) due 2024-02-22

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

   Agenda Review

    <gb> [17]Action 73 make a list of invisible characters to
    support html 5121 discussion (on r12a) due 2024-02-22

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

   Action Items

    <gb> Found actions in w3c/i18n-actions: #74, #73, #72, #68,
    #66, #64, #53, #43, #35, #33, #18, #16, #12, #11, #8, #7, #4

    <addison> #73

    <addison> close #73

    <gb> Closed [18]issue #73

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

    <addison> #72

    <gb> [19]Action 72 update specdev to match string-meta with
    string/block direction as appropriate (on aphillips) due
    2024-02-22

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

    r12a: I wonder whether we should put the information in #73
    somewhere else

    addison: why don't we discuss with the WHATWG
    … depending on what the result is, we can put it somewhere

    <addison> #66

    <gb> [20]Action 66 fix base direction vs. paragraph direction
    in string-meta (on aphillips) due 2024-01-18

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

    <addison> #64

    <gb> [21]Action 64 Make list of HTML issues for February 22
    call with WHATWG (on aphillips, xfq)

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

    <addison> close #64

    <gb> Closed [22]issue #64

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

    <addison> #43

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

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

    <addison> #33

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

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

    <addison> #12

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

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

    <addison> #8

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

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

    <addison> #7

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

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

    <addison> #4

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

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

   Info Share

    Bert: the MessageFormat presentation was about what I expected
    … it was interesting

   RADAR Review

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

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

    Bert: WebNN and MathML not finished

    addison: I have ARIA 1.3

   RADAR Review

    addison: I would appreciate any other pairs of eyes

   Pending Issue Review

    <gb> [30]CLOSED Action 73 make a list of invisible characters
    to support html 5121 discussion (on r12a) due 2024-02-22

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

   String-Meta and the problem of 'paragraph direction'

    addison: last week we discussed the term 'paragraph direction'
    … we discussed replacing that with 'block direction' or 'string
    direction' as a term
    … our glossary definition comes from Unicode
    … so it's a Unicode term
    … should we create new competing but better terminology?

    r12a: I think we could say this is known as paragraph direction

    addison: I can put 'block direction' or 'string direction' in
    our glossary and say 'see paragraph direction'
    … with our explanation of what the term means above that

    r12a: I still think 'paragraph direction' is not clear enough

    addison: I agree
    … I'll working on doing it that way
    … any objections to that?

   Follow up on I18N + CSS Call

    <addison> [31]https://www.w3.org/2024/02/20-i18n-minutes.html

      [31] https://www.w3.org/2024/02/20-i18n-minutes.html

   IDN in Specdev

    <addison> xfq: since we have some specs like rdf that refers to
    punycode

    <addison> ... wonder if it is useful to add best practices
    related to idns

    <addison> ... opinions?

    <addison> ... is it useful and if so what to add and where?

    [32]w3c/bp-i18n-specdev#119

      [32] https://github.com/w3c/bp-i18n-specdev/issues/119

    <gb> [33]Issue 119 Best practice related to IDNs (by xfq)
    [enhancement]

      [33] https://github.com/w3c/bp-i18n-specdev/issues/119

    <addison> [34]https://www.w3.org/TR/
    international-specs/#resid_misc

      [34] https://www.w3.org/TR/international-specs/#resid_misc

    addison: I think we have something in specdev today
    … see ^
    … maybe that needs a little attention

    ACTION: xfq: work on developing new specdev material about
    IDNs/domain names/etc.

    <gb> Created [35]action #75

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

   Prepare for WHATWG Call

    addison: I'll incorporate the discussion of invisible
    characters

    <addison> * Harmonization/cooperation between Infra and
    I18N-Glossary * Input type=email (#4562 + PR #5799) *
    Additional named entities (#5121)

    <gb> Issue 4562 not found

    <gb> Issue 5121 not found

    <gb> Issue 5799 not found

    addison: I propose that we discuss 3 topics
    … see ^

    <addison> [36]https://github.com/w3c/i18n-activity/
    issues?q=is%3Aissue+is%3Aopen+label%3AAgenda%2BI18N%2BWHATWG

      [36] 
https://github.com/w3c/i18n-activity/issues?q=is:issue+is:open+label:Agenda+I18N+WHATWG

    addison: and if we have time, we can go on to time-related
    issues and several input type=date/time issues

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

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

    r12a: I think we need to change the order of these things
    … because the harmonization issue is not too long

    <r12a> [38]w3c/i18n-actions#73

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

    <gb> [39]CLOSED Action 73 make a list of invisible characters
    to support html 5121 discussion (on r12a) due 2024-02-22

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

    r12a: Input type=email is essentially a very long discussion
    … and the additional named entities will probably be quite
    short
    … it took a little while to figure out how to get a list of
    invisible characters
    … I trimmed out some obvious things like PUA characters
    … and some characters you don't really want to create entities
    for them
    … and I created a priority items list
    … these are the things I'd really like to have if nothing else

    Bert: one thing I often use is the variation selector for the
    colour of emojis
    … VS16 (U+FE0F) for emoji with color or VS15 (U+FE0E) for
    monochrome

    addison: what else do we want to say about this list?

    addison: I suspect any of these conversations could be short
    … I'm hopeful John can join us
    … if you can't type some emails this makes this element less
    useful

    <xfq> +1

    addison: the other thing is infra vs glossary
    … I made an assertion in our issue that there are places where
    people want to use terminology and don't want to reference
    Infra
    … like RDF
    … whereas the folks we're talking to say everyone should just
    use Infra
    … we have a lot of terminology that people needed to use that
    doesn't belong to Infra

    r12a: there's also a qualitative difference
    … we sometimes have additional examples or explanations

    addison: we do have definitions in common
    … we should have some process of ensuring that we don't
    conflict each other
    … and we want to avoid situations where we export a term that
    is in Infra

    <gb> [40]CLOSED Action 73 make a list of invisible characters
    to support html 5121 discussion (on r12a) due 2024-02-22

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

   AOB?

Summary of action items

     1. [41]xfq: work on developing new specdev material about
        IDNs/domain names/etc.

Received on Friday, 23 February 2024 03:35:41 UTC