Re: File headers

On Tue, Mar 12, 2013 at 8:34 AM, David Singer <singer@apple.com> wrote:

>
> On Mar 10, 2013, at 18:34 , Silvia Pfeiffer <silviapfeiffer1@gmail.com>
> wrote:
>
> On Mon, Mar 11, 2013 at 12:01 PM, Glenn Maynard <glenn@zewt.org> wrote:
>
>> On Sun, Mar 10, 2013 at 6:21 PM, Silvia Pfeiffer <
>> silviapfeiffer1@gmail.com> wrote:
>>
>>> If you have to escape an empty line with a "\", then you might as well
>>> not do inline styles, since you have to author them differently to a CSS
>>> file.
>>>
>>
>> The intent is to allow a WebVTT editor, or serialization and parsing
>> library, to represent blank lines, so the header format doesn't have a
>> weird exception of not being able to represent something as basic as a
>> blank line.  I don't expect people hand-authoring WebVTT files to use this.
>>
>
>
> We can't exclude that possibility. I'd expect a lot of cut-and-paste
> authoring, which would totally break for CSS.
>
>
> I think it's a minimal change to escape blank lines and terminators ("."
> on a line by itself) and lines that start with the escape.
>

It's really annoying to have to edit that as you're cutting and pasting. I
think it will be the cause of a lot of issues.


>
> The more I think about CSS, the more I'd prefer to force it to be in an
> external stylesheet.
>
>
> It's easier to document inline and then expect to use @import, than 'the
> other way around' (which means using a data: URI, or somesuch)
>


So, if we use "@import (captions.css);" as Ian proposed in
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18530, then the @import
needs to do all the escaping of lines and terminators? That would be
different to CSS and further confusing IMHO.

I'd prefer to just have a metadata header field:
Style: captions.css

Silvia.