W3C

Internationalization Working Group Teleconference

09 Jan 2013

Agenda

See also: IRC log

Attendees

Present
Addison, Richard, Mati, Koji, Felix
Regrets
Chair
Addison Phillips
Scribe
Addison Phillips

Contents


<r12a> http://lists.w3.org/Archives/Public/www-international/2013JanMar/0018.html

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

<r12a> http://rishida.net/temp/HangulTextLayout_20130102.pdf

Pending reviews received over break

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 http://www.w3.org/2013/01/09-i18n-minutes.html#action01]

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

KLReq

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 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 http://www.w3.org/2013/01/09-i18n-minutes.html#action02]

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

ITS v2 review

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

<r12a> http://www.w3.org/International/reviews/review-instructions

Case Sensitivity in CSS

http://www.w3.org/International/wiki/CaseForCaselessCSS

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

https://lists.w3.org/Archives/Member/member-i18n-core/2013Jan/0003.html

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

http://lists.w3.org/Archives/Public/www-international/2013JanMar/0018.html

http://www.w3.org/International/tests/html-css/generate?test=case-conversion-001

<r12a> http://www.w3.org/International/tests/html-css/generate?test=case-conversion-001

<r12a> 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 (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)

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 documents.

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

AOB?

Summary of Action Items

[NEW] ACTION: addison: coordinate with richard regarding KLReq [recorded in http://www.w3.org/2013/01/09-i18n-minutes.html#action02]
[NEW] ACTION: addison: remind everyone to comment on css3-text-decoration by next week [recorded in http://www.w3.org/2013/01/09-i18n-minutes.html#action01]
 
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.137 (CVS log)
$Date: 2013-01-14 14:03:42 $