[minutes] Internationalization telecon 2024-04-11

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





text version:

                              – DRAFT –
            Internationalization Working Group Teleconference

11 April 2024

    [2]Agenda. [3]IRC log.

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

Attendees

    Present
           Addison, Bert, Fuqiao, JcK, Richard

    Regrets
           -

    Chair
           Addison Phillips

    Scribe
           Bert

Contents

     1. [4]Agenda Review
     2. [5]Action Items
     3. [6]Info Share
     4. [7]RADAR Review
     5. [8]Pending Issue Review
     6. [9]Add dark mode support for specdev
     7. [10]named entity issue
     8. [11]needs-attention issue review
     9. [12]AOB?
    10. [13]Summary of action items

Meeting minutes

   Agenda Review

   Action Items

    <addison> #88

    <gb> [14]Action 88 approach Unicode about operating a URL for
    locale-ids (on aphillips) due 2024-04-11

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

    addison: I did #88. Looped Felix in.
    … So far neither accepted nor rejected. May be headed to a
    URN-type solution.

    <addison> close #88

    <gb> Closed [15]issue #88

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

    <addison> #87

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

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

    <addison> #82

    <gb> [17]Action 82 publish khmer lreq as FPWD with new format
    (on r12a) due 2024-03-21

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

    addison: Thanks JcK for the email addresses. But I haven't sent
    yet.

    <addison> close #82

    <gb> Closed [18]issue #82

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

    <addison> #79

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

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

    <addison> #78

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

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

    <addison> #77

    <gb> [21]Action 77 create an issue against html requesting the
    list of named entities based on work in action 73 (on r12a) due
    2024-03-07

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

    r12a: I created a pending issue to discuss.
    … We talked about it and said we should all read it.

    <addison> #76

    <gb> [22]Action 76 propose best practices for producers and for
    examples in specs in string-meta (on aphillips) due 2024-03-07

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

    <addison> #75

    <gb> [23]Action 75 work on developing new specdev material
    about IDNs/domain names/etc. (on xfq) due 2024-02-29

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

    xfq: I have an action to update the PR, but not done (due to AC
    meeting).

    <addison> #43

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

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

    <addison> #3

    <gb> [25]CLOSED Action 3 Give ghurlbot access to write to the
    repo (on r12a) due 18 Jul 2023

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

    <addison> #33

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

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

    addison: On the agenda for later.

    <addison> #12

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

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

    addison: Will be in a coming meeting.

    <addison> #8

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

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

    <addison> #7

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

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

    <addison> #4

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

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

    r12a: Not heard anything back yet.

   Info Share

    xfq: At the AC meeting there was a session about internet, DNS,
    the web and the moon & mars. New lunar time zone.
    … may be related to our time zone work in the future.

    JcK: Did they talk about new DNS infracstructire for DNS
    servers to talk back and forth?

   RADAR Review

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

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

    Bert: Nothing done yet on poniter events.

    addison: I propose to move View Transitions to completed.
    … I looked at my awaiting comment resolutuon specs. All issues
    addressed. Propose to move to completed.

   Pending Issue Review

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

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

    <addison> [33]i18n-activity#1846

      [33] https://github.com/w3c/i18n-activity/issues/1846

    <gb> [34]Issue 1846 Improve handling of malformed unicode bidi
    control characters (by w3cbot) [pending] [tracker] [s:html]
    [spec-type-issue] [alreq] [hlreq]

      [34] https://github.com/w3c/i18n-activity/issues/1846

    addison: Unbalanced bidi controls can break the isolation in
    browsers, probably due to the way it is implemented. Make it a
    "needs-resolutuion"?

    <xfq> +1

    <Bert> +1

   Add dark mode support for specdev

    <xfq> [35]w3c/bp-i18n-specdev#130

      [35] https://github.com/w3c/bp-i18n-specdev/pull/130

    <gb> [36]Pull Request 130 Add dark mode support (by xfq)

      [36] https://github.com/w3c/bp-i18n-specdev/pull/130

    <xfq> [37]https://
    deploy-preview-130--bp-i18n-specdev.netlify.app/

      [37] https://deploy-preview-130--bp-i18n-specdev.netlify.app/

    xfq: I made a pull request to add dark mode. If your OS uses
    dark mode, you can see it here ^^
    … If you think this is good, I can add it to other specs, too.

    addison: Some boxes are illegible.

    xfq: Hmm, not for me...

    r12a, Bert and xfq don't see the same colors as Addison. Why?

    People sharing screens to show what they see.

    JcK: Also problems with contrast and colors for color-blind.

    xfq: Will do some a11y tests.

    ACTION: xfq: update i18n specs to support dark mode

    <gb> Created [38]action #89

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

    The Javascript button that switches dark mode does something
    else than the OS dark mode. That is probably what causes the
    differences.

    r12a: With the JS dark mode, the check boxes actually look more
    readable.

    xfq: A little too prominent.

    r12a: Might be OK. When you click to see those boxes, that is
    what you want to see,

   named entity issue

    <addison> [39]i18n-activity#1841

      [39] https://github.com/w3c/i18n-activity/issues/1841

    <gb> [40]Issue 1841 Request for additional named entities for
    invisible/ambiguous characters (by r12a) [pending] [s:html]
    [t:char_ref]

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

    r12a: Not sure if it useful to have enitity names for all,
    e.g., the musical symbols.

    addison: The Egyption symbols seem very specialized.

    addison: We can just say we have a question about the musical
    symbols, as we are not musicologists ourselves.

    addison: Might be another teleconf discussion with them.

    r12a: Anybody have ideas about the Hangul Jamo symbols? They
    don't seem to work in browswers.
    … the hangul filler character.

    xfq: Maybe ask the Korean experts.

    addison: What does "don't work" mean? You mean when you put the
    Unicode chars?

    r12a: At least one is in the compatibility area.

    addison: Only two variation selectors?

    r12a: Only two for emojis. There are others.

    addison: Is there a priority order? Things to trade?

    r12a: Yes, the ones in italics.

    r12a: Korean is a bit unusual. In most language you go for NFC,
    but in Korean decomposed gives certain possibilities.
    … Writing educational stuff, then bits of syllables are useful.
    … But couldn't find a lot of information about them.

    addison: So what do we need to do to submit this?

    r12a: An issue in the HTML list, I suppose.

    addison: And are we happy with this list?
    … Maybe add some text about what we discussed.

    addison: The &zwsp; is mentioned at the bottom, what is that?
    … the U+200B

    r12a: Refresh, GitHub swallowed the "&ZeroWidthSpace;"

    addison: Maybe put it in the list, indent it.

    Bert: Which ones are for the Egyptian that you mentioned?

    r12a: They're not in the list yet. Egyptian is 2-dimensional,
    need to put side-by-side, on top, etc,

   needs-attention issue review

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

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

    <addison> [42]i18n-activity#1783

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

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

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

    xfq: So we're reviewing the request to the TAG?

    addison: We're viewing the TAG's decision about 'text-spacing'.

    r12a: Complicated, need to do a lot of back reading...
    … I have many issues on my reading list. Would like to keep
    this issue so I can get to it eventually. Not next week,
    though.

    <addison> [44]w3c/i18n-activity#1769

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

    <gb> [45]Issue 1769 Please reconsider the use of collator-based
    search (by w3cbot) [tracker] [needs-attention] [t:char_sort]
    [s:scroll-to-text-fragment] [cg:wicg]

      [45] https://github.com/w3c/i18n-activity/issues/1769

    <addison> [46]WICG/scroll-to-text-fragment#233

      [46] https://github.com/WICG/scroll-to-text-fragment/issues/233

    <gb> [47]Issue 233 Please reconsider the use of collator-based
    search (by hsivonen) [i18n-tracker] [spec issue]

      [47] https://github.com/WICG/scroll-to-text-fragment/issues/233

    xfq: Seems to need a "needs-resolution" label.

    addison: Added.

    xfq: It's related to our string search, but not the same
    mechanism.

    ACTION: addison: steal some of henri's text from
    scroll-to-text-fragment for string-search

    addison: We can steal from hsivonen's work for this issue for
    our own string search.

    <gb> Created [48]action #90

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

   AOB?

    addison: I did a revision for string-meta. Not merged the PR
    yet. Come back to it next week. Please, look at at.

Summary of action items

     1. [49]xfq: update i18n specs to support dark mode
     2. [50]addison: steal some of henri's text from
        scroll-to-text-fragment for string-search

Received on Friday, 12 April 2024 02:58:52 UTC