[minutes] Internationalization WG telecon, 2013-01-09


Text version follows:

Internationalization Working Group Teleconference

09 Jan 2013



    See also: [3]IRC log

       [3] http://www.w3.org/2013/01/09-i18n-irc


           Addison, Richard, Mati, Koji, Felix

           Addison Phillips

           Addison Phillips


      * [4]Topics
          1. [5]Agenda and Minutes
          2. [6]Action Items
          3. [7]Info Share
          4. [8]Pending reviews received over break
          5. [9]KLReq
          6. [10]ITS v2 review
          7. [11]Case Sensitivity in CSS
          8. [12]AOB?
      * [13]Summary of Action Items



Agenda and Minutes

Action Items

    close ACTION-164

    <trackbot> Closed ACTION-164 Create blog entry showing our case
    for css caselessness.

    close ACTION-168

    <trackbot> Closed ACTION-168 Remind everyone to read ITS 2.0
    for the 9th.

Info Share

    addison: KLReq document received
    ... temporary link to follow


      [15] http://rishida.net/temp/HangulTextLayout_20130102.pdf

Pending reviews received over break


      [16] http://www.w3.org/TR/2013/WD-css-text-decor-3-20130103/

    CSS3: Text-decoration

    due by the 31st

    <scribe> ACTION: addison: remind everyone to comment on
    css3-text-decoration by next week [recorded in

    <trackbot> Created ACTION-169 - Remind everyone to comment on
    css3-text-decoration by next week [on Addison Phillips - due



      [18] http://rishida.net/temp/HangulTextLayout_20130102.pdf

    addison: above is temporary link

    richard: scanned it
    ... looks pretty good
    ... not as detailed as the Japanese one
    ... good for a first version
    ... we need to send for review and then get feedback
    ... think it might need some extra small details
    ... such as wrapping rules (when, what context)... just example
    ... needs English editing

    addison: also need to publish Korean version

    richard: need formal sign-off on publication through w3c
    ... talked to domain lead
    ... should invited editors to join IG as IE
    ... create IG-task-force
    ... and use public-cjk list as their feedback list
    ... suggest we convert to polyglot

    <scribe> ACTION: addison: coordinate with richard regarding
    KLReq [recorded in

    <trackbot> Created ACTION-170 - Coordinate with richard
    regarding KLReq [on Addison Phillips - due 2013-01-16].

ITS v2 review


      [20] http://tinyurl.com/its20-comments-handling

    <scribe> chair: IMPORTANT to read by next week

    UNKNOWN_SPEAKER: for call of the 16th

    felix: send comments before next week

    addison: will create item in tracker
    ... please follow WG process for creating comments


      [21] http://www.w3.org/International/reviews/review-instructions

Case Sensitivity in CSS


      [22] http://www.w3.org/International/wiki/CaseForCaselessCSS


      [23] http://www.inter-locale.com/test/css-case-sensitive-demo1.html




      [25] http://www.w3.org/blog/CSS/2007/12/12/case_sensitivity/








      [29] http://lists.w3.org/Archives/Public/www-style/2012Dec/0089.html

    case sensitivity: we're okay with that

    ACI for ASCII-restricted namespaces: okay

    for user identiifers that are case *IN*sensitive: only Unicode
    CF is acceptable

    for user identifiers that are case *SENSITIVE*, we're okay

    ACI is a special case of UniCF

    we're not okay with any ACI comparison that can contain
    non-ASCII characters

    scribe: that is using ACI

    if "g" == "G" then "ü" == "Ü"

    we would recommend that CSS use case sensitive comparison

    if there is a feature that is case insensitive, then it should
    be UniCF

    restate: we would recommend that CSS adopt case sensitive
    comparison going forward for all identifiers and language
    elements, except where legacy considerations apply

    ACI "doesn't really exist" (it's a shadow case of UniCF on an
    ASCII namespace)

    A custom data attribute is an attribute in no namespace whose
    name starts with the string "data-", has at least one character
    after the hyphen, is XML-compatible, and contains no uppercase
    ASCII letters. All attribute names on HTML elements in HTML
    documents get ASCII-lowercased automatically, so the
    restriction on ASCII uppercase letters doesn't affect such

    possible exception of list-style-type


    - case sensitive

    - except legacy ascii-only items

    - only if a WG still wants to make a new feature case
    insensitive, then Unicode case folding

    ACTION; addison: communicate case sensitivity to CSS

    i18n recommends case sensitive

    spec writing guidelines


Summary of Action Items

    [NEW] ACTION: addison: coordinate with richard regarding KLReq
    [recorded in
    [NEW] ACTION: addison: remind everyone to comment on
    css3-text-decoration by next week [recorded in

    [End of minutes]

Richard Ishida
Internationalization Activity Lead
W3C (World Wide Web Consortium)


Received on Monday, 14 January 2013 14:07:07 UTC