Re: File headers

BTW: I'm happy to specify multi-line, but would just want to exclude the
use of empty lines in multi-line.

So we could do something like
Style: |
captions1.css
captions2.css
.

or
Style: |
captions1.css
captions2.css
##

(the latter seems like a more readable "end" character)

Silvia.

On Tue, Mar 12, 2013 at 9:16 AM, Silvia Pfeiffer
<silviapfeiffer1@gmail.com>wrote:

> On Tue, Mar 12, 2013 at 9:09 AM, David Singer <singer@apple.com> wrote:
>
>>
>> On Mar 11, 2013, at 15:00 , Silvia Pfeiffer <silviapfeiffer1@gmail.com>
>> wrote:
>>
>> 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.
>>
>>
>> but if you're sure to get an error and nothing works if you forget…
>>
>
> I don't think that's what would happen. Everything would work until the
> first empty line and from there on the parser expects a cue, so it keeps
> dropping stuff until it finds a valid cue.
>
> Things will continue to work, except that some styles will not be applied.
>
>
> this is pretty common, by the way.
>>
>>
>>
>>>
>>> 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.
>>
>>
>> No, I mean if we allow inline, and document that you use @import for
>> reference (to an un-modified style sheet) you get both effects.  Whereas if
>> we allow only reference, the poor sod who wants to go inline has to use
>> data:text/css:whatever
>> which is messy
>>
>
> Yeah, you do it the non-standard way, it gets messy. It's supposed to,
> right?
>
>
>>
>>
>> I'd prefer to just have a metadata header field:
>> Style: captions.css
>>
>>
>> I think we could live with that.  we can always intro multi-line values
>> later, if it gets painful.  it means we would have two different keys
>> (Style and InlineStyle, or the like), but that's livable also.
>>
>
> That raises another question: will browser ignore this field and this is
> only for non-browsers, i.e. if you use it in a Web page you have to include
> the captions.css file there anyway?
>
>
> Silvia.
>