See also: IRC log
http://www.w3.org/International/track/actions/open
close action-403
<trackbot> Closed action-403.
close action-405
<trackbot> Closed action-405.
close action-406
<trackbot> Closed action-406.
close action-407
<trackbot> Closed action-407.
close action-408
<trackbot> Closed action-408.
close action-409
<trackbot> Closed action-409.
<r12a> https://www.w3.org/International/wiki/Bp_spec_bidi
richard: talked about above wiki
page last week
... have a list of do/don't for spec writers
... worked on above
... reviewing webvtt was helpful in updating
... techniques index is where this might go
<r12a> http://www.w3.org/International/techniques/developing-specs-dynamic
addison: bring sections of that for review here?
richard: also good to ensure that every review's items get harvested here
https://www.w3.org/International/wiki/Review_radar
https://www.w3.org/International/wiki/Project_radar
richard: move the spec checklist under 1.2
addison: okay
richard: over time the spec checklist will bring together guidelines from and link out to all of the other documents :-)
https://lists.w3.org/Archives/Member/chairs/2015JanMar/0085.html
https://www.w3.org/wiki/DocumentReview#Horizontal_Groups
addison: above is voluntary, suggest that we are looking for a mandatory process step
no conclusion reached
issue-394?
<trackbot> issue-394 -- decimal-format reference CLDR? -- open
<trackbot> http://www.w3.org/International/track/issues/394
https://lists.w3.org/Archives/Public/public-i18n-core/2015JanMar/0038.html
richard: would like it "noted" that we made this comment. not satisfied but won't stop you
<scribe> ACTION: addison: write back to QT asking for issue-394 to be "noted" [recorded in http://www.w3.org/2015/02/26-i18n-minutes.html#action01]
<trackbot> Created ACTION-410 - Write back to qt asking for issue-394 to be "noted" [on Addison Phillips - due 2015-03-05].
http://www.w3.org/International/track/products/73
issue-418?
<trackbot> issue-418 -- observation: line wrapping, line balancing ⓟ -- open
<trackbot> http://www.w3.org/International/track/issues/418
http://www.w3.org/TR/2014/WD-webvtt1-20141113/
http://www.w3.org/TR/webvtt1/#cues-with-multiple-lines
richard: see in section 6
later?
... don't think you can set css properties for line
wrapping
... didn't see it
... they are pretty specific about which css properties you can
set
... don't think that's one
addison: keep our eyes on this, add line wrapping properties to comment
issue-419?
<trackbot> issue-419 -- term "NOTE" may not be friendly to users in other languages ⓟ -- open
<trackbot> http://www.w3.org/International/track/issues/419
jck: may also be a bidi issue
<arabic> NOTE <latin>
richard: markup would mess up the
file in an plain text editing process
... controls are invisible and may create other issues
... seems that we need a "bidi reference model" ?
... how you expect to display, edit, etc.
issue-420?
<trackbot> issue-420 -- no provision for indicating overall content language(s) ⓟ -- open
<trackbot> http://www.w3.org/International/track/issues/420
addison: also no way to set the whole document to rtl either
issue-421?
<trackbot> issue-421 -- non-ASCII examples? ⓟ -- open
<trackbot> http://www.w3.org/International/track/issues/421
Generally in the document, I don't find a means for indicating the natural language of the content as a whole. There is a cue language span, for spanning runs of text, but no way to indicate the language of the file as a whole (that is, the language outside a spanned section).
<!-- -->
#
issue-422?
<trackbot> issue-422 -- start/end linked to left/right ⓟ -- open
<trackbot> http://www.w3.org/International/track/issues/422
richard: rlm and lrm don't solve
all cases
... don't reference the rest of the unicode controls
issue-423?
<trackbot> issue-423 -- Optional BOM ⓟ -- open
<trackbot> http://www.w3.org/International/track/issues/423
richard: no need to draw attention?
issue-424?
<trackbot> issue-424 -- Why not ABNF/EBNF? ⓟ -- open
<trackbot> http://www.w3.org/International/track/issues/424
richard: railroad diagrams!
... more verbiage could be useful if there were examples
... a picture every so often would make this clear
issue-425?
<trackbot> issue-425 -- Normalization and string identity issues ⓟ -- open
<trackbot> http://www.w3.org/International/track/issues/425
addison: need a health warning about divergent byte sequences
issue-426?
<trackbot> issue-426 -- zero or more characters? ⓟ -- open
<trackbot> http://www.w3.org/International/track/issues/426
issue-427?
<trackbot> issue-427 -- WebVTT percentage ⓟ -- open
<trackbot> http://www.w3.org/International/track/issues/427
A WebVTT percentage consists of the following components: One or more ASCII digits.
issue-428?
<trackbot> issue-428 -- emphasis spans ⓟ -- open
<trackbot> http://www.w3.org/International/track/issues/428
addison: other kinds of emphasis?
richard: whether they should provide those rather than relying on CSS?
<b> bold</b>
richard: we have an article about
that
... this is presentational markup, have a more general
mechanism
... you'd want bouten marks in Japanese on TVs for example
issue-429?
<trackbot> issue-429 -- "valid" language tag ⓟ -- open
<trackbot> http://www.w3.org/International/track/issues/429
issue-430?
<trackbot> issue-430 -- No character escapes ⓟ -- open
<trackbot> http://www.w3.org/International/track/issues/430
issue-431?
<trackbot> issue-431 -- ruby + rt sufficient? ⓟ -- open
<trackbot> http://www.w3.org/International/track/issues/431
richard: html ruby model
... doesn't handle double-sided
... want to start small and grow later might be okay
addison: no group ruby?
richard: by having separate rt spans
issue-432?
<trackbot> issue-432 -- processing model handling of bidi ⓟ -- open
<trackbot> http://www.w3.org/International/track/issues/432
richard: apparently some tests exist
<scribe> ACTION: addison: notify WebVTT that we are actively reviewing [recorded in http://www.w3.org/2015/02/26-i18n-minutes.html#action02]
<trackbot> Created ACTION-411 - Notify webvtt that we are actively reviewing [on Addison Phillips - due 2015-03-05].
http://www.w3.org/International/track/products/74
http://www.w3.org/TR/2015/WD-appmanifest-20150212/
This specification defines a JSON-based manifest that provides developers with a centralized place to put metadata associated with a web application. This includes, but is not limited to, the web application's name, links to icons, as well as the preferred URL to open when a user launches the web application. The manifest also allows developers to declare a default orientation for their web application, as well as providing the ability to set the display[CUT]
<matial_> have to leave