trackbot, prepare teleconference
<agendabot> clear agenda
https://www.w3.org/International/track/actions/open
action-773?
<trackbot> action-773 -- Addison Phillips to Close all issues and publish charmod-norm as a wg note (with richard's assistance) -- due 2019-01-31 -- OPEN
<trackbot> https://www.w3.org/International/track/actions/773
close action-773
<trackbot> Closed action-773.
action-774?
<trackbot> action-774 -- Richard Ishida to Publish first public working draft of string-meta -- due 2019-02-07 -- OPEN
<trackbot> https://www.w3.org/International/track/actions/774
jck: ietf i18n directorate now set up
https://github.com/w3c/i18n-activity/projects/1
http://w3c.github.io/i18n-activity/projects/
<r12a> w3c.github.io/typography/gap-analysis/language-matrix
richard: implemented the change
in categorization for typographic stuff as discussed last
week
... did this in the language matrix too
<r12a> http://w3c.github.io/typography/gap-analysis/language-matrix
richard: if you look at the
language matrix
... set pagination, other paragraph, other inline to "okay" by
default
... reduced need for investigation
... started retrofitting to gap analysis docs
... for lao and javanese and khmer
... gathering gap analysis from discussion list
... didn't have anywhere to put info
<r12a> https://w3c.github.io/sealreq/lao/
richard: created new layout requirements docs
<r12a> https://w3c.github.io/sealreq/khmer/
<r12a> https://w3c.github.io/sealreq/javanese/
richard: pretty much little stubs
addison: any way to automate?
(discussion)
<r12a> https://w3c.github.io/mlreq/
<r12a> https://github.com/w3c/csswg-drafts/issues/2754
richard: for your
information...
... a little more common in chinese
... question is how to do
... what about punctuation?
... placed in middle of square
... comma might face same way?
... in japanese, the comma is moved to the left of character
square in horizontal
... would you need to reposition it if RTL?
... no one knows, no examples so far
addison: how?
richard: actually vertical text
with 1 character per column is really an urban myth
... it's nonsensical
... horizontal-tbrl was suggested
... but that is inconsistent with writing modes
... key issue is that japanese/chinese are strongly LTR
... UBA relies on character properties
... thinking is to use bidi override with direction=rtl
... embedded numbers/text in <bdo>
... but very similar to "close wrapping" recommendation we do
for normal bidi text
https://lists.w3.org/Archives/Public/www-international/2019JanMar/0033.html
https://lists.w3.org/Archives/Public/public-i18n-core/2019JanMar/0007.html
<scribe> ACTION: addison: ping florian in place of chaals for input type=email
<trackbot> Created ACTION-775 - Ping florian in place of chaals for input type=email [on Addison Phillips - due 2019-02-14].
richard: info share
<r12a> https://w3c.github.io/jlreq/docs/simple-ruby/
richard: JL req TF plans to do
number of things
... 1. go through errata
... also pick up docs from advanced publishing lab in
japan
... this is the first
... "rules for simple placement of ruby"
... didnd't want to put in jlreq directly
... believe we should at least point to it from jlreq
... people might disagree, more a personal opinion?
... need to figure out what status to use
... have a look at it in case of problems
addison: should this really go into TR space? or just be article? concern about normative appearance
richard: let's have a look
<scribe> ACTION: addison: remind WG to read simple-ruby draft for next week's teleconference
<trackbot> Created ACTION-776 - Remind wg to read simple-ruby draft for next week's teleconference [on Addison Phillips - due 2019-02-14].
https://w3c.github.io/string-meta/
https://w3c.github.io/string-meta/#best-practices-for-communicating-language-and-direction
richard: question, one approach
is to require say HTML
... can add directional information in HTML in your
string
... and doc says we don't recommend this
addison: try to say "probably a terrible idea"
richard: if using metadata, dont
you need a closed system in same way?
... need to be more explicit that this is an idea
This is scribe.perl Revision: 1.154 of Date: 2018/09/25 16:35:56 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Succeeded: s|<atsushi> sorry, but today my home internet access seems a bit slow, let me join via phone.|| Succeeded: s|<Katy> +present|| Default Present: present, atsushi, addison, r12a, Katy, JcK, Bert Present: Bert JcK addison atsushi r12a Andrew No ScribeNick specified. Guessing ScribeNick: addison Inferring Scribes: addison Agenda: https://lists.w3.org/Archives/Member/member-i18n-core/2019Feb/0000.html Found Date: 07 Feb 2019 People with action items: addison remind wg WARNING: IRC log location not specified! (You can ignore this warning if you do not want the generated minutes to contain a link to the original IRC log.)[End of scribe.perl diagnostic output]