401
edits
Accessibility/Experiment1 feedback: Difference between revisions
Jump to navigation
Jump to search
Ms2ger feedback from blog post included
(added missing callback feature) |
(Ms2ger feedback from blog post included) |
||
| Line 67: | Line 67: | ||
FS = Felipe Sanches/collaborative subtitling | FS = Felipe Sanches/collaborative subtitling | ||
MG = [[User:Ms2ger]] | |||
* SP: the distinction between captions and subtitles may not be necessary | * SP: the distinction between captions and subtitles may not be necessary | ||
| Line 125: | Line 127: | ||
::: SP reply: I haven't started working on in-band time-aligned text yet, but the plan is to experiment with Ogg and Kate to see how far we can get to expose an identical interface to the browser as through the out-of-band time-aligned text. So, while parsing the binary file, the text should be added to the DOM as is happening with the out-of-band text. | ::: SP reply: I haven't started working on in-band time-aligned text yet, but the plan is to experiment with Ogg and Kate to see how far we can get to expose an identical interface to the browser as through the out-of-band time-aligned text. So, while parsing the binary file, the text should be added to the DOM as is happening with the out-of-band text. | ||
* MG: It looks interesting to me, but from a quick read I'd say that in the current proposal (at least in the demo) there's too much boilerplate code. At least one of the arguments pro HTML5 is that it doesn't require more typing than necessary (see the doctype, meta charset, etc.). | |||
::: So, personally, I'd drop @type and shorten @category. I'd also put @charset in the SRT file itself, or at least in the HTTP headers, where it is less likely to be out of sync with the content. (I guess that's not possible with the format as it stands today, but it needs a better spec anyway. I guess a charset declaration could be added at the same time.) Finally, I'd make @display default to "auto", and make the behavior dependent on the language and the category. (E.g. always display the cue points.) | |||
::: I.e., instead of <itext lang="es" type="text/srt" charset="ISO-8859" display="auto" src="subtitles/elephant.spanish.srt" category="CC"></itext> I'd prefer something closer to <itext lang="es" src="subtitles/elephant.spanish.srt" cat="CC">. I'd drop the end-tag. | |||
:: Also, shouldn't that use "ISO-8859-1" rather than "ISO-8859"? | |||
* more feedback encouraged! | * more feedback encouraged! | ||