See also: IRC log
action-113?
<trackbot> action-113 -- Richard Ishida to Work on tidying up Additional Requirements for Bidi in HTML & CSS over coming couple of months -- due 2015-02-05 -- OPEN
<trackbot> http://www.w3.org/International/track/actions/113
<scribe> ACTION: addison: ping Aharon with email about additional requirements document [recorded in http://www.w3.org/2015/03/26-i18n-minutes.html#action01]
<trackbot> Created ACTION-421 - Ping aharon with email about additional requirements document [on Addison Phillips - due 2015-04-02].
action-412?
<trackbot> action-412 -- Felix Sasaki to Publish multilingual web usage scenarios -- due 2015-03-12 -- OPEN
<trackbot> http://www.w3.org/International/track/actions/412
close action-418
<trackbot> Closed action-418.
close action-420
<trackbot> Closed action-420.
https://www.w3.org/International/wiki/Review_radar
steve: will pick up svg a11y spec?
data on the web bp: make felix shepherd
richard: new tweet about new version of latin layout req
https://www.w3.org/International/wiki/Project_radar
<scribe> ACTION: addison: warn WG members to look at LTLI ED for discussion next week as a new WD [recorded in http://www.w3.org/2015/03/26-i18n-minutes.html#action02]
<trackbot> Created ACTION-422 - Warn wg members to look at ltli ed for discussion next week as a new wd [on Addison Phillips - due 2015-04-02].
richard: cl req: not much
activity this week, except that discussing with PLH what
process is for getting people into TF
... don't need to make them WG members per-se
... process is to make them public invited expert
... put them in the IG
... they get a W3 account and then fill in IE form
... predefined counter styles
... if we have extra time, could brainstorm
mlweb workshop
<r12a-limechat> http://www.multilingualweb.eu/documents/2015-riga-workshop/2015-riga-program
<r12a-limechat> program announced
addison: several people seem to
be coming
... do we need a room?
richard: tpac in china wasn't bad... had seats to sit on
addison: no room, wandering minstrel mode?
richard: think that might be best approach
addison: what about cl req folks?
<scribe> ACTION: richard: ping beihan folks about tpac logistics [recorded in http://www.w3.org/2015/03/26-i18n-minutes.html#action03]
<trackbot> Created ACTION-423 - Ping beihan folks about tpac logistics [on Richard Ishida - due 2015-04-02].
https://www.w3.org/wiki/DocumentReview
BP: if in doubt, before formally
asking a horizontal group to review a document, talk to them
informally (f.ex. via e-mail). (comment): I agree that it may
not be obvious that a document needs horizontal review, but I
tend to take a stronger line: even if you have not identified a
horizontal group dependency, you should always discuss whether
a review is necessary or even request a review (saying if you
think there are no issues of interest to t[CUT]
... avoid cross-posting to multiple lists (and if this must be
done, use Bcc:). Alternate instructions for providing
commentary (if needed). Some groups use bugzilla or github as a
means of communication and for tracking issues. --Addison
Phillips (talk)
richard: should add cross-posting
as needed
... "get a decent mail client"
addison: will edit the
above
... actively want cross-posting
<scribe> ACTION: addison: solicit comments from WG on w3c document review process wiki page [recorded in http://www.w3.org/2015/03/26-i18n-minutes.html#action04]
<trackbot> Created ACTION-424 - Solicit comments from wg on w3c document review process wiki page [on Addison Phillips - due 2015-04-02].
richard: don't use bpXXX number. use the gray character off to the left (the id for the best practice) when referring to bps
<r12a-limechat> use http://w3c.github.io/bp-i18n-specdev/#lang_neg or #lang_neg NOT BP71 to refer to recommendations
<scribe> ACTION: richard: figure out means of making BP number and/or identifier properly emphasized [recorded in http://www.w3.org/2015/03/26-i18n-minutes.html#action05]
<trackbot> Created ACTION-425 - Figure out means of making bp number and/or identifier properly emphasized [on Richard Ishida - due 2015-04-02].
richard: this document
... orginally this document was a home for homeless
information
... but became apparent that people expected this to be
everything they needed
... or at least pointers
... and confusing if they had to go to techniques page
... so spent time rearchitecting it
... all BPs in techniques page are now here too
... and the techniques page would like to "more info"
locations
... changed techniques to allow pointer to more than one
thing
... and wrote a script that takes BP document and generates
techniques
... two versions of techniques (one collapsable, one not)
... one version is generated from github document
... reduces need for duplicating information
<Steve_Atkin> My line dropped calling back
<r12a-limechat> http://w3c.github.io/bp-i18n-specdev/
<r12a-limechat> http://www.w3.org/International/techniques/developing-specs
<r12a-limechat> http://www.w3.org/International/techniques/developing-specs-dynamic
https://lists.w3.org/Archives/Public/www-international/2015JanMar/
https://lists.w3.org/Archives/Public/www-international/2015JanMar/0181.html
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28262
https://lists.w3.org/Archives/Public/www-international/2015JanMar/0167.html
https://lists.w3.org/Archives/Public/www-international/2015JanMar/0168.html
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28266
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28265
<Steve_Atkin> I need to drop I have another call.
W3C HTML5 also has rb, rtc That said, I think it is a non-goal to match the expressiveness of HTML in WebVTT. WebVTT only has elements to cater for specific use cases that apply to it.
koji: don't know where the
boundaries are?
... quite hard to say that
... nobody from japan is helping with this?
addison: don't see anyone per-se
koji: common when only two lines
to have first line ruby on top and second line ruby on bottom,
for example
... not sure if TV wants double-sided
... maybe not so important to have group, etc
richard: no ruby styling provided? maybe new comment?
<scribe> ACTION: richard: ask at domain meeting about whether webvtt will be used for tv and cinema [recorded in http://www.w3.org/2015/03/26-i18n-minutes.html#action06]
<trackbot> Created ACTION-426 - Ask at domain meeting about whether webvtt will be used for tv and cinema [on Richard Ishida - due 2015-04-02].
<scribe> ACTION: addison: tag all threads based on our comments in appmanifest's github so we can track [recorded in http://www.w3.org/2015/03/26-i18n-minutes.html#action07]
<trackbot> Created ACTION-427 - Tag all threads based on our comments in appmanifest's github so we can track [on Addison Phillips - due 2015-04-02].