See also: IRC log
https://www.w3.org/International/track/actions/open
action-580?
<trackbot> action-580 -- Richard Ishida to Set up two repos for felix's documents from its for final publication as note -- due 2017-01-26 -- OPEN
<trackbot> http://www.w3.org/International/track/actions/580
close action-580
<trackbot> Closed action-580.
https://github.com/w3c/i18n-activity/projects/1
<r12a> https://lists.w3.org/Archives/Member/w3c-ac-members/2017JanMar/0012.html
richard: jumped into ttml2,
jumped straight into ruby section
... so if you look elsewhere........
... many issues in ruby
<r12a> [[
<r12a> The horizontal review should focus only on the new features
<r12a> introduced in TTML2.
<r12a> Please refer to the section for changes between Timed Text Markup Language (TTML) Version 1 (TTML1) and Version 2 (TTML2).
<r12a> https://www.w3.org/TR/2016/WD-ttml2-20161117/#changes-from-ttml1-vocabulary
<r12a> ]]
addison: please volunteer on the member list for sections as you review them
https://lists.w3.org/Archives/Member/member-i18n-core/2017Jan/0017.html
https://github.com/w3c/csswg-drafts/issues/938
koji: proposal from florian to
change line-height:normal
... would lose ability to set line height based on font
metrics
... may affect some languages/fonts that have very tall
scripts
... proposal is to make line-height:normal to be
line-height:1
... there are some scripts that stack vertically or are very
tall
(citings of Tibetan, Myanmar, Arabic)
scribe: when set to a number, it
depends on font
... normal uses font metrics not the font
... so line to line spacing can be different
... florians proposal is to avoid font metrics based line
height because Latin font users have bad experience
... do non-latin script rely more on normal/font metrics than
others??
normal is default
lines never overlap as a result, but leading inconsistent
if glyphs too tall, lines overlap, when you use numbers
<r12a> نشاط التدويل، W3C نشاط التدويل، W3C نشاط التدويل، W3C نشاط التدويل، W3C نشاط التدويل، W3C نشاط التدويل، W3C རྒྱལ་སྤྱིར་བསྒྱུར་བའི་ལས་དོན། W3C རྒྱལ་སྤྱིར་བསྒྱུར་བའི་ལས་དོན། W3C རྒྱལ་སྤྱིར་བསྒྱུར་བའི་ལས་དོན། W3C རྒྱལ་སྤྱིར་བསྒྱུར་བའི་ལས་དོན། W3C
richard: trying quickly, Tibetan and Arabic break if line-height:1
mixed script produces better results when it can adjust
richard: there are text examples
at following link
... might be useful
<r12a> http://r12a.github.io/scripts/phrases
koji: can prepare response using
these samples
... will bring back if not easy to conclude
richard: sent some emails about
this
... more I thought that this is useful
... suggesting that we hit www-international issue when an
issue is created
... or if we raised on someone's repo and it gets the i18n
label
... and winter when they close
... but no information flowing
... that is useful in keeping traffic down
... but also means that they get notifications that they might
not care about
... have to subscribe to the issue itself
... also folks reply by email rather than github, creating
threading problems
... so propose to send digest saying effectively: here are the
new issues, the closed issues, and the ones with traffic
... thinking daily digest
... two or more digest is possible
<scribe> ACTION: richard: send note to www-international announcing switching to github digests and set up the digests [recorded in http://www.w3.org/2017/01/26-i18n-minutes.html#action01]
<trackbot> Created ACTION-584 - Send note to www-international announcing switching to github digests and set up the digests [on Richard Ishida - due 2017-02-02].
<r12a> http://w3c.github.io/typography/
<r12a> https://w3c.github.io/i18n-drafts/articles/typography/justification.en
richard: suggesting we take the differently formatted material on justification and put in another place
<najib> +1
addison: +1
no objections noted
<david> +1
<scribe> ACTION: richard: move the justification materials to separate article and point to it from typography document [recorded in http://www.w3.org/2017/01/26-i18n-minutes.html#action02]
<trackbot> Created ACTION-585 - Move the justification materials to separate article and point to it from typography document [on Richard Ishida - due 2017-02-02].
<r12a> http://w3c.github.io/i18n-drafts/articles/vertical-text.en
richard: updated a bit
... new section on "default character orientation"
... some small changes and a few more comments to deal with
https://github.com/whatwg/infra/issues/1
<scribe> ACTION: addison: summarize whatwg string definition and recommend changes if needed [recorded in http://www.w3.org/2017/01/26-i18n-minutes.html#action03]
<trackbot> Created ACTION-586 - Summarize whatwg string definition and recommend changes if needed [on Addison Phillips - due 2017-02-02].
<r12a> [[
<r12a> Code Point. (1) Any value in the Unicode codespace; that is, the range of integers from 0 to 10FFFF16. (See definition D10 in Section 3.4, Characters and Encoding.) Not all code points are assigned to encoded characters. See code point type. (2) A value, or position, for a character, in any coded character set.
<r12a> ]]