[minutes] Internationalization telecon 2018-02-22

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





text snapshot:



  – DRAFT –
            Internationalization Working Group Teleconference

22 February 2018

    [2]IRC log

       [2] https://www.w3.org/2018/02/22-i18n-irc

Attendees

    Present
           Bert, JcK, Katy, r12a

    Regrets
           Addison, Fuquiao

    Chair
           -

    Scribe
           katy

Contents

      * [3]Meeting Minutes
          1. [4]Action Items
          2. [5]Info Share
          3. [6]IMSC character sets
          4. [7]More infoshare
          5. [8]Closing TTML Issues
          6. [9]Greek emphasis dots & metrical marks

Meeting Minutes

Action Items

    <r12a> [10]http://www.w3.org/International/track/actions/open

      [10] http://www.w3.org/International/track/actions/open

    <r12a> close action-696

    <trackbot> Closed action-696.

    <r12a> close action-697

    <trackbot> Closed action-697.

Info Share

    <r12a> [11]http://w3c.github.io/typography/gap-analysis/
    language-matrix.html

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

    <r12a> [12]https://w3c.github.io/jlreq/gap-analysis/

      [12] https://w3c.github.io/jlreq/gap-analysis/

    r12a: Language matrix, links to docs where people can identify
    gap analysis
    … new one, an example that is developed.
    … incl. tests and figures; generates some info

    r12a: suggested a single group to contacts for Khmer & Lao
    … looking for Thai and Myanmar

IMSC character sets

    <r12a> [13]https://www.w3.org/TR/
    ttml-imsc1.0.1/#recommended-unicode-code-points-per-language

      [13] 
https://www.w3.org/TR/ttml-imsc1.0.1/#recommended-unicode-code-points-per-language

    JcK: Reposted to key thread, moving towards CLDR
    … looking for advice on that.

    <r12a> [14]https://github.com/w3c/imsc/issues/236

      [14] https://github.com/w3c/imsc/issues/236

    r12a: Talk about the wider question…
    … Application uses UTF-8, no need to specify the character set.
    … The fonts or rendering algorithms are not unavailable to
    support specific char-ranges / langs
    … Aims to assist authors b/c existing processes are poor at
    supporting foreign languages
    … One shouldn't take it too far, to rely on these applications
    … content authors may require some advice, to ensure that texts
    support these chars
    … symbols etc, commonly used in video transcriptions, may be
    unavailable in CLDR
    … when dealing with legacy applications, may find have poor
    support for multilingual texts
    … by implication, the application developers may not have
    multilingual support;
    … whereas this limits to specific sets of characters.
    … CLDR may not always be accurate or complete (?)
    … in thread, tried to suggest an alternative wording

    JcK: Have posted the wrong solution to the wrong problem. It's
    an interesting question.
    … if updating legacy application, should update accordingly

    r12a: If this is about legacy applications, then look at what
    charsets are supported
    … expecting that applications will rely on CLDR
    … meaning expecting applications to limit their support for
    chars

    JcK: The issue about chars in legacy applications, or langs not
    appearing in CLDR either, fact that imposing chars in langs
    which have no possible use for them.
    … Fundamentally, wrong solution to wrong problem
    … utility of decorated Latin chars is a little dubious. Taking
    us back to pre-Unicode definition of HTML.
    … suggests opening up a new thread, distance from fonts etc.

    r12a: recommends waiting to see what happens on this thread,
    first.

    r12a:

More infoshare

    <r12a> [15]https://twitter.com/webi18n/status/
    966654589574549504

      [15] https://twitter.com/webi18n/status/966654589574549504

    r12a: Tweet explains the first public working draft of text
    layout for Arabic script.
    … lot of text; not yet many instructions for implementers.
    … publishing it may get some attention.

Closing TTML Issues

    <r12a> [16]https://lists.w3.org/Archives/Public/
    www-international/2018JanMar/0085.html

      [16] 
https://lists.w3.org/Archives/Public/www-international/2018JanMar/0085.html

    <r12a> Proposed: Close all TTML issues listed at above URL

    <r12a> +1

    <JcK> +1

    +1

    <Bert> +1

    <r12a> Resolved

Greek emphasis dots & metrical marks

    e.g. ⏒ 23D2 METRICAL LONG OVER SHORT

    JcK: Use of zero-width joiners; there are similar chars in
    Arabic or Hebrew that are aggravated by RTL

    r12a: Armenian explanation mark + question mark, that are
    displayed above the vowel nearest the end

    <r12a> [17]https://r12a.github.io/scripts/
    armenian/#tonal_punctuation

      [17] https://r12a.github.io/scripts/armenian/#tonal_punctuation

    JcK: can you lose the emphasis marks without loss of meaning

    JcK: If there were a perfect normalisation algorithm, it would
    treat the emphasis marks in different ways.

    JcK: Charmod-Norm, getting a sophisticated use of lang
    typically requires lang specific info.
    … no. of one-to-one examples.

Received on Thursday, 22 February 2018 17:39:39 UTC