Agenda
See also: IRC log
<r12a>
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.
addison: KLReq document
received
... temporary link to follow
<r12a>
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 2013-01-16].
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 incorporated
... 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].
<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
<r12a>
<r12a>
<r12a>
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 (universally)
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).
possible exception of list-style-type
resolved:
- 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