[minutes] Internationalization telecon 2020-08-27

https://www.w3.org/2020/08/27-i18n-minutes.html








text extract follows:




  - DRAFT -

            Internationalization Working Group Teleconference

27 Aug 2020

    [2]Agenda

       [2] https://lists.w3.org/Archives/Member/member-i18n-core/2020Aug/0030.html

Attendees

    Present
           Atsushi, Bert, Felix, Fuqiao, JcK, Richard, addison

    Regrets

    Chair
           Addison Phillips

    Scribe
           addison

Contents

      * [3]Topics
          1. [4]Agenda and Minutes
          2. [5]Action Items
          3. [6]Info Share
          4. [7]RADAR Review
          5. [8]"cognitive disabilities" comments
          6. [9]String-search / HTML find-in-page
          7. [10]AOB?
      * [11]Summary of Action Items
      * [12]Summary of Resolutions
      __________________________________________________________

    trackbot, prepare teleconference

    <agendabot> clear agenda

    <scribe> scribenick: addison

    <JcK> I'm on another call that is running over; will join as
    soon as possible but may be a bit late.

Agenda and Minutes

Action Items

    [13]https://www.w3.org/International/track/actions/open

      [13] https://www.w3.org/International/track/actions/open

    action-939?

    <trackbot> action-939 -- Richard Ishida to See if we have a
    definition of ltr/rtl/auto somewhere centralized that specs can
    refer to -- due 2020-08-13 -- OPEN

    <trackbot>
    [14]https://www.w3.org/International/track/actions/939

      [14] https://www.w3.org/International/track/actions/939

    <r12a> LTR stands for "left-to-right" and refers to the inline
    base direction of left-to-right [UAX9]. This is the base text
    direction used by languages whose starting character
    progression begins on the left side of the page in horizontal
    text. It's used for scripts such as Latin, Cyrillic,
    Devanagari, and many others.

    <r12a> RTL stands for "right-to-left" and refers to the inline
    base direction of right-to-left [UAX9]. This is the base text
    direction used by languages whose starting character
    progression begins on the right side of the page in horizontal
    text. It's used for a variety of scripts which include Arabic,
    Hebrew, N'Ko, Adlam, Thaana, and Syriac among others.

    <r12a> [15]https://w3c.github.io/string-meta/#terminology

      [15] https://w3c.github.io/string-meta/#terminology

    <xfq> [16]https://github.com/w3c/manifest/pull/926

      [16] https://github.com/w3c/manifest/pull/926

    <JcK> Sorry to be late on this, but RTL has caused confusion
    because there are few, if any contemporary writing systems that
    are strictly RTL (unlike those that are strictly LTR)

    <scribe> ACTION: richard: create definition of
    'ltr'/'rtl'/'auto' that can be referenced by other
    specifications in string-meta

    <trackbot> Created ACTION-946 - Create definition of
    'ltr'/'rtl'/'auto' that can be referenced by other
    specifications in string-meta [on Richard Ishida - due
    2020-09-03].

    close action-939

    <trackbot> Closed action-939.

    action-942?

    <trackbot> action-942 -- Addison Phillips to Apply edits
    discussed in telecon and merge the normalization and
    localization specdev changes -- due 2020-08-20 -- OPEN

    <trackbot>
    [17]https://www.w3.org/International/track/actions/942

      [17] https://www.w3.org/International/track/actions/942

    close action-942

    <trackbot> Closed action-942.

Info Share

    fuqiao: noticed a new CG

    <xfq> [18]https://www.w3.org/community/font-text/

      [18] https://www.w3.org/community/font-text/

    fuqiao: the "Font and Text" CG
    ... a lot to do with our work
    ... should probably track

    richard: in a similar vein

    <r12a> [19]https://github.com/whatwg/html/pull/5868

      [19] https://github.com/whatwg/html/pull/5868

    richard: a PR against HTML to remove the section
    ... in rendering at the end
    ... that says how you render quotes for non-English languages
    ... saying the CSS spec has a new value auto
    ... that browsers should produce appropriate quotes for the
    language
    ... so that they could remove
    ... raised a comment (about 12 min ago)

    <r12a> [20]https://github.com/whatwg/html/issues/3636

      [20] https://github.com/whatwg/html/issues/3636

    richard: our older issue may be redundant becuase nothing to
    point to in HTML
    ... need to take to CSS to specify "lang of quotes is
    surrounding, not embedded text"
    ... resort to raising bugs against impls? look at the thread
    please

    raised tracking issue

    <r12a> [21]https://twitter.com/r12a

      [21] https://twitter.com/r12a

    richard: further info share
    ... released 13 new pickers
    ... a lot of them are for historical scripts, e.g. Phoenician
    ... but a number for living scripts

RADAR Review

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

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

    <xfq> [23]https://github.com/w3c/i18n-activity/labels/s%3Awebxr

      [23] https://github.com/w3c/i18n-activity/labels/s:webxr

    [24]https://github.com/w3c/i18n-activity/issues/953

      [24] https://github.com/w3c/i18n-activity/issues/953

    <xfq> htc-vive

    <xfq> oculus-go

    <xfq> samsung-gearvr

    "generic-trigger-squeeze-touchpad-thumbstick"

    [25]https://www.w3.org/TR/charmod-norm/#choosingMatchingAlgorit
    hm

      [25] https://www.w3.org/TR/charmod-norm/#choosingMatchingAlgorithm

    <xfq> updating RECs will be easier with Process 2020

    <r12a> JcK: we should be more proactive about recommending when
    it's better to use ASCII (ie. for internal-only identifiers)
    and warn people that if they ddon't they need to consider a
    bunch of other stuff

    <scribe> ACTION: addison: propose content guidance text in
    charmod-norm

    <trackbot> Created ACTION-947 - Propose content guidance text
    in charmod-norm [on Addison Phillips - due 2020-09-03].

    <xfq>
    [26]https://github.com/w3c/i18n-request/issues/127#issuecomment
    -671429502

      [26] https://github.com/w3c/i18n-request/issues/127#issuecomment-671429502

    [27]https://github.com/w3c/i18n-activity/issues/949

      [27] https://github.com/w3c/i18n-activity/issues/949

    <scribe> ACTION: addison: submit issue 953 to web-xr with
    appropriate rewording based on telecon

    <trackbot> Created ACTION-948 - Submit issue 953 to web-xr with
    appropriate rewording based on telecon [on Addison Phillips -
    due 2020-09-03].

"cognitive disabilities" comments

    <fsasaki>
    [28]https://github.com/w3c/i18n-activity/labels/s%3Acoga-usable

      [28] https://github.com/w3c/i18n-activity/labels/s:coga-usable

    felix: review deadline next week
    ... can submit comments in next week

    <fsasaki> [29]https://github.com/w3c/i18n-activity/issues/965

      [29] https://github.com/w3c/i18n-activity/issues/965

    expert -> expertise

    <fsasaki> [30]https://github.com/w3c/i18n-activity/issues/957

      [30] https://github.com/w3c/i18n-activity/issues/957

    <xfq> +1

    For Zip / Postal codes, including state or address information
    close to the number so that speech voices can expand known
    abbreviations (such as state names) and listeners can perceive
    the context.

    This is a particular problem for phone numbers or zip codes.

    When writing long numbers, considering what separators will be
    familiar to your readers and how it will be read aloud. In
    general, English speaking countries will use commas between
    thousands and a period as the decimal separator whereas German
    and other European countries do the opposite.

    <fsasaki> [31]https://github.com/w3c/i18n-activity/issues/956

      [31] https://github.com/w3c/i18n-activity/issues/956

    <scribe> ACTION: felix: propose text for spec dev around
    examples such as personal names

    <trackbot> Created ACTION-949 - Propose text for spec dev
    around examples such as personal names [on Felix Sasaki - due
    2020-09-03].

    <fsasaki> [32]https://github.com/w3c/i18n-activity/issues/950

      [32] https://github.com/w3c/i18n-activity/issues/950

    perhaps "person with poor language skills, such as an
    immigrant"

    non-native speakers? avoid "poor"?

    "non-native speakers with limited language skills"

    <scribe> ACTION: felix: submit comments on cognitive
    disabilities doc

    <trackbot> Created ACTION-950 - Submit comments on cognitive
    disabilities doc [on Felix Sasaki - due 2020-09-03].

String-search / HTML find-in-page

    <xfq> [33]https://github.com/whatwg/html/pull/5770

      [33] https://github.com/whatwg/html/pull/5770

    <xfq> [34]https://w3c.github.io/string-search/

      [34] https://w3c.github.io/string-search/

    [35]https://w3c.github.io/string-search/

      [35] https://w3c.github.io/string-search/

    <r12a>
    s|file:///c:/users/addison/Documents/GitHub/string-search/index
    .html||

AOB?

Summary of Action Items

    [NEW] ACTION: addison: propose content guidance text in
    charmod-norm
    [NEW] ACTION: addison: submit issue 953 to web-xr with
    appropriate rewording based on telecon
    [NEW] ACTION: felix: propose text for spec dev around examples
    such as personal names
    [NEW] ACTION: felix: submit comments on cognitive disabilities
    doc
    [NEW] ACTION: richard: create definition of 'ltr'/'rtl'/'auto'
    that can be referenced by other specifications in string-meta

Summary of Resolutions

    [End of minutes]

Received on Thursday, 27 August 2020 16:05:38 UTC