See also: IRC log
<r12a> zakim is on holiday today
close action-316
<trackbot> Closed action-316.
close action-317
<trackbot> Closed action-317.
close action-318
<trackbot> Closed action-318.
<koji> http://www.unicode.org/review/pri278/
koji: UTR50 public review is
about to happen. See above
... only three weeks
addison: will add to radar
<koji> The blog is here http://unicode-inc.blogspot.jp/2014/07/proposed-update-utr-50-unicode-vertical.html
https://www.w3.org/International/wiki/Review_radar#Scheduled_Last_Call_reviews
http://www.w3.org/International/docs/charmod-norm/
http://lists.w3.org/Archives/Public/public-i18n-cjk/2014JulSep/0002.html
koji: sent this out and haven't
had time to digest responses
... issue is that WG removed inter-ideograph
justification
... prefer automatic based on content language
... and when content language is not available
... want to do something "good for any language"
... trying to figure out how to keep that goal
... particularly between Chinese, Japanese, and Korean
... need Korean input to make proposal
... WG discussed status yesterday
... some thought maybe bring inter-ideograph back
... maybe translate English to Korean and send again
... and see what comes back
richard: let's not mess around with language codes, forcing them to say something that they don't say
koji: agree
... mozilla may have decided to go in this direction
... others don't seem to be paying attention
richard: one case talking about
korean using han only
... and that was treated as "chinese"
addison: so if a language has one
behavior, just fold it into "auto"
... but if two behaviors need keywords
richard: perhaps ping Leandro for some info
<scribe> ACTION: koji: report back on korean justification when response received [recorded in http://www.w3.org/2014/07/10-i18n-minutes.html#action01]
<trackbot> Created ACTION-319 - Report back on korean justification when response received [on Koji Ishii - due 2014-07-17].
koji: one more info
... discussion on slowness of css-text
... proposed to split
... fantasai wants to keep together, proposed to move to CR by
october
... need to be quick
http://www.w3.org/International/track/products/25
# Historically many encodings had their names and labels (and sometimes # references to specifications) defined in the IANA Character Sets registry. # This specification supplants that registry.
JcK: helpful if there will be a
summary ahead of the call
... IETF is the week after next