[minutes] Internationalization WG TPAC 2023 F2F Part II: 2023-09-12

https://www.w3.org/2023/09/12-i18n-minutes.html



                              – DRAFT –
           Internationalization (I18N) WG - TPAC 2023 - Tuesday

12 September 2023

    [2]IRC log.

       [2] https://www.w3.org/2023/09/12-i18n-irc

Attendees

    Present
           Addison, Bert, Fatima, Fuqiao, Richard, Thomas

    Regrets
           -

    Chair
           Addison Phillips

    Scribe
           xfq

Contents

     1. [3]Today's Live Schedule
     2. [4]Today
     3. [5]reviews needs-attention issues
     4. [6]Meeting with RDF-*
     5. [7]APA WG meeting
     6. [8]review CSS issues for thursday
     7. [9]WCAG
     8. [10]Summary of action items

Meeting minutes

   Today's Live Schedule

    <addison> [11]https://github.com/w3c/i18n-actions/wiki/
    2023-TPAC-Planning

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

    <addison> **Note well: meeting with RDF is at 10:30, not 9:30**

   Today

   reviews needs-attention issues

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

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

    <addison_> [13]w3c/i18n-activity#1361

      [13] https://github.com/w3c/i18n-activity/issues/1361

    <addison_> [14]w3c/adapt#175

      [14] https://github.com/w3c/adapt/issues/175

    addison_: this spec also links to the HTML autocomplete
    attribute
    … I could try to reopen this issue
    … I'll mark this as repoen

    <addison_> [15]w3c/i18n-activity#1358

      [15] https://github.com/w3c/i18n-activity/issues/1358

    addison_: this issue is open
    … it's about RTL named group support in URLPattern

    [16]w3c/i18n-activity#1368

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

    xfq: we have two tracker issues, 1358 and 1368

    addison_: will close 1358

    <addison_> [17]w3c/i18n-activity#1038

      [17] https://github.com/w3c/i18n-activity/issues/1038

    addison_: there's a request at the bottom of it

    r12a: I'm not sure if it's a tatweel or a hyphen

    xfq: when browsers implement this, should they use tatweel or
    hyphen?

    r12a: no conclusion in the Unicode Consortium yet
    … we had a discussion not long ago, and another discussion
    about N'Ko
    … for N'Ko the conlsusion was to use the N'Ko character
    … this is a soft hyphen
    … I think this should use tatweel
    … this is just an example
    … I'll reply to Florian

    <addison_> [18]w3c/i18n-activity#1037

      [18] https://github.com/w3c/i18n-activity/issues/1037

    <addison_> [19]w3c/csswg-drafts#5972

      [19] https://github.com/w3c/csswg-drafts/issues/5972

    addison_: CSSWG rejected it
    … and the question is whether if r12a is satisfied

    r12a: I don't know whether that's a valid distinction or not

    <r12a> [20]https://html.spec.whatwg.org/multipage/
    text-level-semantics.html#the-wbr-element

      [20] 
https://html.spec.whatwg.org/multipage/text-level-semantics.html#the-wbr-element

    Bert: use word-break for long URLs
    … I don't expect hyphens in that case

    addison_: is that intentional?

    r12a: the HTML example is better for soft hyphens rather than
    wbr
    … the HTML spec says the wbr element represents a line break
    opportunity
    … it doesn't say "a line break opportunity without hyphenation"

    Bert: if you put the style in the wbr element itself, it
    doesn't do anything
    … you have to put it in the element outside

    addison_: should we make it a needs-resolution issue?

    r12a: I think so
    … there's no problem if you're using this approach if you use
    it for URLs
    … if you try to click or copy and paste it it will work

    <addison_> [21]whatwg/html#6326

      [21] https://github.com/whatwg/html/issues/6326

    Bert: and that's why I use wbr

    <addison_> [22]w3c/i18n-activity#980

      [22] https://github.com/w3c/i18n-activity/issues/980

    <addison_> [23]w3c/i18n-activity#894

      [23] https://github.com/w3c/i18n-activity/issues/894

    r12a: I think 894 should be closed

   Meeting with RDF-*

    <addison> see their notes

    <addison> [24]https://www.w3.org/2023/09/
    12-rdf-star-irc#T08-33-10

      [24] https://www.w3.org/2023/09/12-rdf-star-irc#T08-33-10

    ACTION: richard to follow up on the bidi thread of rdf-star

    <gb> Cannot create action. Validation failed. Maybe richard is
    not a valid user for w3c/i18n-actions?

    <addison> gb, richard is r12a

    ACTION: richard to follow up on the bidi thread of rdf-star

    <gb> Created [25]action #44

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

   APA WG meeting

    <addison> Location: Ultera, 1st floor

    <addison> [26]https://www.w3.org/2023/09/12-apa-irc#T09-43-49

      [26] https://www.w3.org/2023/09/12-apa-irc#T09-43-49

   review CSS issues for thursday

    <addison> [27]https://github.com/w3c/i18n-actions/wiki/
    2023-TPAC-Planning#proposed-css-joint-agenda

      [27] 
https://github.com/w3c/i18n-actions/wiki/2023-TPAC-Planning#proposed-css-joint-agenda

    [28]https://github.com/w3c/csswg-drafts/projects/39

      [28] https://github.com/w3c/csswg-drafts/projects/39

    [29]w3c/i18n-actions#11

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

    [30]w3c/i18n-actions#10

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

    <addison> [31]https://github.com/w3c/csswg-drafts/projects/39

      [31] https://github.com/w3c/csswg-drafts/projects/39

    [32]https://github.com/w3c/i18n-activity/projects/3

      [32] https://github.com/w3c/i18n-activity/projects/3

    [33]w3c/alreq#220

      [33] https://github.com/w3c/alreq/issues/220

    <r12a> sideways tests: [34]https://www.w3.org/International/
    i18n-tests/results/int-vertical-text.html#dutch

      [34] 
https://www.w3.org/International/i18n-tests/results/int-vertical-text.html#dutch

    [35]w3c/clreq#243

      [35] https://github.com/w3c/clreq/issues/243

    <r12a> [36]w3c/jlreq#318

      [36] https://github.com/w3c/jlreq/issues/318

    <addison> [37]https://github.com/w3c/i18n-actions/wiki/
    2023-TPAC-Planning#proposed-css-joint-agenda

      [37] 
https://github.com/w3c/i18n-actions/wiki/2023-TPAC-Planning#proposed-css-joint-agenda

    [38]https://www.w3.org/WAI/GL/

      [38] https://www.w3.org/WAI/GL/

   WCAG

    <addison> [39]https://www.w3.org/events/meetings/
    8f9736a7-09f1-4133-b3f0-3800f777a5fb/

      [39] 
https://www.w3.org/events/meetings/8f9736a7-09f1-4133-b3f0-3800f777a5fb/

    <addison> email sent to wcag

    <addison> (discussing what else to accomplish today)

    <addison> (pinging wcag)

    <addison> (chat-chatting with css)

    <addison> (introductions with fatima)

Summary of action items

     1. [40]richard to follow up on the bidi thread of rdf-star

Received on Tuesday, 19 September 2023 07:38:54 UTC