[minutes] Internationalization telecon 2019-02-07

https://www.w3.org/2019/02/07-i18n-minutes.html






text version follows:


- DRAFT -

            Internationalization Working Group Teleconference

07 Feb 2019

    [2]Agenda

       [2] 
https://lists.w3.org/Archives/Member/member-i18n-core/2019Feb/0000.html

Attendees

    Present
           Bert, JcK, addison, atsushi, r12a, Andrew

    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 and Active Work Review
          5. [8]RTL Japanese and Chinese
          6. [9]<input> types in HTML
          7. [10]Publishing APL doc in Jlreq TF
          8. [11]String-Meta
          9. [12]AOB?
      * [13]Summary of Action Items
      * [14]Summary of Resolutions
      __________________________________________________________

    trackbot, prepare teleconference

    <agendabot> clear agenda

Agenda and Minutes

Action Items

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

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

    action-773?

    <trackbot> action-773 -- Addison Phillips to Close all issues
    and publish charmod-norm as a wg note (with richard's
    assistance) -- due 2019-01-31 -- OPEN

    <trackbot>
    [16]https://www.w3.org/International/track/actions/773

      [16] https://www.w3.org/International/track/actions/773

    close action-773

    <trackbot> Closed action-773.

    action-774?

    <trackbot> action-774 -- Richard Ishida to Publish first public
    working draft of string-meta -- due 2019-02-07 -- OPEN

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

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

Info Share

    jck: ietf i18n directorate now set up

RADAR and Active Work Review

    [18]https://github.com/w3c/i18n-activity/projects/1

      [18] https://github.com/w3c/i18n-activity/projects/1

    [19]http://w3c.github.io/i18n-activity/projects/

      [19] http://w3c.github.io/i18n-activity/projects/

    <r12a> w3c.github.io/typography/gap-analysis/language-matrix

    richard: implemented the change in categorization for
    typographic stuff as discussed last week
    ... did this in the language matrix too

    <r12a>
    [20]http://w3c.github.io/typography/gap-analysis/language-matri
    x

      [20] http://w3c.github.io/typography/gap-analysis/language-matrix

    richard: if you look at the language matrix
    ... set pagination, other paragraph, other inline to "okay" by
    default
    ... reduced need for investigation
    ... started retrofitting to gap analysis docs
    ... for lao and javanese and khmer
    ... gathering gap analysis from discussion list
    ... didn't have anywhere to put info

    <r12a> [21]https://w3c.github.io/sealreq/lao/

      [21] https://w3c.github.io/sealreq/lao/

    richard: created new layout requirements docs

    <r12a> [22]https://w3c.github.io/sealreq/khmer/

      [22] https://w3c.github.io/sealreq/khmer/

    <r12a> [23]https://w3c.github.io/sealreq/javanese/

      [23] https://w3c.github.io/sealreq/javanese/

    richard: pretty much little stubs

    addison: any way to automate?

    (discussion)

    <r12a> [24]https://w3c.github.io/mlreq/

      [24] https://w3c.github.io/mlreq/

RTL Japanese and Chinese

    <r12a> [25]https://github.com/w3c/csswg-drafts/issues/2754

      [25] https://github.com/w3c/csswg-drafts/issues/2754

    richard: for your information...
    ... a little more common in chinese
    ... question is how to do
    ... what about punctuation?
    ... placed in middle of square
    ... comma might face same way?
    ... in japanese, the comma is moved to the left of character
    square in horizontal
    ... would you need to reposition it if RTL?
    ... no one knows, no examples so far

    addison: how?

    richard: actually vertical text with 1 character per column is
    really an urban myth
    ... it's nonsensical
    ... horizontal-tbrl was suggested
    ... but that is inconsistent with writing modes
    ... key issue is that japanese/chinese are strongly LTR
    ... UBA relies on character properties
    ... thinking is to use bidi override with direction=rtl
    ... embedded numbers/text in <bdo>
    ... but very similar to "close wrapping" recommendation we do
    for normal bidi text

<input> types in HTML

    [26]https://lists.w3.org/Archives/Public/www-international/2019
    JanMar/0033.html

      [26] 
https://lists.w3.org/Archives/Public/www-international/2019JanMar/0033.html

    [27]https://lists.w3.org/Archives/Public/public-i18n-core/2019J
    anMar/0007.html

      [27] 
https://lists.w3.org/Archives/Public/public-i18n-core/2019JanMar/0007.html

    <scribe> ACTION: addison: ping florian in place of chaals for
    input type=email

    <trackbot> Created ACTION-775 - Ping florian in place of chaals
    for input type=email [on Addison Phillips - due 2019-02-14].

    richard: info share

Publishing APL doc in Jlreq TF

    <r12a> [28]https://w3c.github.io/jlreq/docs/simple-ruby/

      [28] https://w3c.github.io/jlreq/docs/simple-ruby/

    richard: JL req TF plans to do number of things
    ... 1. go through errata
    ... also pick up docs from advanced publishing lab in japan
    ... this is the first
    ... "rules for simple placement of ruby"
    ... didnd't want to put in jlreq directly
    ... believe we should at least point to it from jlreq
    ... people might disagree, more a personal opinion?
    ... need to figure out what status to use
    ... have a look at it in case of problems

    addison: should this really go into TR space? or just be
    article? concern about normative appearance

    richard: let's have a look

    <scribe> ACTION: addison: remind WG to read simple-ruby draft
    for next week's teleconference

    <trackbot> Created ACTION-776 - Remind wg to read simple-ruby
    draft for next week's teleconference [on Addison Phillips - due
    2019-02-14].

String-Meta

    [29]https://w3c.github.io/string-meta/

      [29] https://w3c.github.io/string-meta/

    [30]https://w3c.github.io/string-meta/#best-practices-for-commu
    nicating-language-and-direction

      [30] 
https://w3c.github.io/string-meta/#best-practices-for-communicating-language-and-direction

    richard: question, one approach is to require say HTML
    ... can add directional information in HTML in your string
    ... and doc says we don't recommend this

    addison: try to say "probably a terrible idea"

    richard: if using metadata, dont you need a closed system in
    same way?
    ... need to be more explicit that this is an idea

AOB?

Summary of Action Items

    [NEW] ACTION: addison: ping florian in place of chaals for
    input type=email
    [NEW] ACTION: addison: remind WG to read simple-ruby draft for
    next week's teleconference

Summary of Resolutions

    [End of minutes]

Received on Thursday, 7 February 2019 15:37:31 UTC