[minutes] Internationalization telecon 2014-02-20


Text version follows:

Internationalization Working Group Teleconference

20 Feb 2014



    See also: [3]IRC log

       [3] http://www.w3.org/2014/02/20-i18n-irc


           Addison, Richard, Mati, JohnK

           Addison Phillips

           Addison Phillips


      * [4]Topics
          1. [5]Agenda
          2. [6]Action Items
          3. [7]Info Share
          4. [8]RADAR
          5. [9]HTML5 caseless matching
          6. [10]HTML5 review
          7. [11]AOB?
      * [12]Summary of Action Items


Action Items


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


    <trackbot> action-149 -- Norbert Lindenberg to Draft a proposal
    for adding time zone IDs to HTML5 -- due 2012-09-26 -- OPEN


      [14] http://www.w3.org/International/track/actions/149

    move to addison

    close ACTION-286

    <trackbot> Closed ACTION-286.

    richard: one outstanding new issue though
    ... got spec changed to match hebrew implementations (thanks
    ... but all of the japanese implementations are (consistently)
    out by one or two charactes
    ... change to match?
    ... rare characters at the end of hiragana, so all items out
    after 48
    ... same with iroha set

    addison: ask people we know and report back

Info Share

    richard: tests

    <r12a> [15]http://www.w3.org/International/tests/

      [15] http://www.w3.org/International/tests/

    richard: changing so we don't rely on w3c framework/server
    ... above link, now done
    ... click on tests. table on right has results
    ... don't go to test framework server any more
    ... link on left shows test in test runner
    ... and click on "score" you can score it
    ... and when done do "show results", copy to email and send to
    ... watch inboxes for announcement about Unicode 7.0 coming

    richard: Aolita Sharma to give keynote at ML workshop in May



      [16] http://www.w3.org/International/wiki/Review_radar



    1. Section 3.6 "Positioning Images", the keywords "left" and
    "right" are defined but not the direction independent "start"
    and "end" keywords.

    2. Section 4. There are a number of border-left-* and
    border-right-* properties. (See above).

    There is no mention of bidi other than a note about breaks in
    fragmented borders (section 7.1), so it's not clear how
    left/right interact with RTL.

    richard: +1

    <scribe> ACTION: addison: create comments on
    borders/backgrounds in tracker and forward to CSS WG [recorded
    in [18]http://www.w3.org/2014/02/20-i18n-minutes.html#action01]

    <trackbot> Created ACTION-288 - Create comments on
    borders/backgrounds in tracker and forward to css wg [on
    Addison Phillips - due 2014-02-27].

    richard: the containing element would determine start/end, that
    is, the outer element, not the styled element

    <matial> agree

HTML5 caseless matching


      [19] https://www.w3.org/International/wiki/CaseForCaselessHTML

    addison: focused on fragments



    richard: bug is about three things
    ... 1. radio buttons (which is a different and probably less
    interesting case: do case sensitive?)
    ... 2. fragment identifiers
    ... 3. should fragments be case sensitive at all
    ... same rule for @id as for radio button names

    <input name=match> and <input name=MATCH>

    addison: split off radio buttons

    richard: can't predict how typed
    ... looser than codepoint by codepoint?
    ... but not compatibility decompositions

    john: agree that compatibility decomposition should be

    <scribe> ACTION: addison: split off radio button comment and
    update bug 16970 [recorded in

    <trackbot> Created ACTION-289 - Split off radio button comment
    and update bug 16970 [on Addison Phillips - due 2014-02-27].


HTML5 review



    addison: suggest that you review all "suggest close" items

    I18N-ISSUE-78: tracker confused and not actually fixed

    <trackbot> Notes added to I18N-ISSUE-78 Spellchecking in
    editors and sc services.

    richard: some still pending until rb is actually in the spec
    (need implementations)

    ISSUE-30: allow 'utf-16' in charset declarations. wontfix. Last
    commenter suggested we reopen.

    <trackbot> Notes added to ISSUE-30 Allow utf-16 meta encoding

    ISSUE-84: BCE month representation. Wontfix. Consider in WG.

    <trackbot> Notes added to ISSUE-84 Representing BCE months.

    addison: only goes back to january 1 AD in gregorian
    ... was pre-gregorian

    addison; be satisfied?

    jck: retitle and document for the future

    ISSUE-87: leap seconds not allowed. Wontfix. Consider in WG.

    <trackbot> Notes added to ISSUE-87 Leap seconds.

    addison: better for people who are customers of this to raise
    it than for us to be their proxhy


    <trackbot> ISSUE-123 -- Insertion of U+202C -- open

    <trackbot> [23]http://www.w3.org/International/track/issues/123

      [23] http://www.w3.org/International/track/issues/123

    <matial> Suggestion for issue-123: any end tag for a run of
    phrasing content must be treated as if as many U+202C had been
    inserted at that point as needed for closing open embeddings
    and overrides.


Summary of Action Items

    [NEW] ACTION: addison: create comments on borders/backgrounds
    in tracker and forward to CSS WG [recorded in
    [NEW] ACTION: addison: split off radio button comment and
    update bug 16970 [recorded in

    [End of minutes]

Received on Friday, 21 February 2014 12:41:49 UTC