[whatwg] Google Feedback on the HTML5 media a11y specifications

[Philip Jägenstedt]

On Tue, 15 Feb 2011 12:57:02 +0100, Glenn Maynard <glenn at zewt.org> wrote:

> Following up on a use case discussed earlier, an alternative approach
> for adding mid-cue comments, such as editor notes, would be to wrap
> them in a class: <c.c>comment</c>.  It's a little awkward, but has the
> advantage of allowing the comments to be displayed within the
> displayed captions just by changing the style attached to the class.

I think it's not a bad idea.

Pro:
  - No new escapes
  - Optionally visible when previewing e.g. a translation

Cons:
  - not hidden by default
  - therefore, requires either assuming CSS support (boo!) or removing all  
comments before publishing

> On Tue, Feb 15, 2011 at 5:09 AM, Philip Jägenstedt <philipj at opera.com>  
> wrote:
>> 1. Authors are encouraged to not manually line-break
>
> I think that, no matter what you do, people will insert line breaks in
> cues.  I'd follow the HTML model here: convert newlines to spaces and
> have a separate, explicit line break like <br> if needed, so people
> don't manually line-break unless they actually mean to.
>
> Related to line breaking, should there be an   escape?  Inserting
> nbsp literally into files is somewhat annoying for authoring, since
> they're indistinguishable from regular spaces.

I would kind of prefer not going down that path, otherwise we should also  
add ­ and escapes for all kinds of things that are hard to type. I  
naively hope that editors that don't suck at Unicode will spring into  
existence.

-- 
Philip Jägenstedt
Core Developer
Opera Software