- From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Date: Tue, 24 Apr 2012 10:38:14 +1000
- To: Glenn Maynard <glenn@zewt.org>
- Cc: David Singer <singer@apple.com>, public-texttracks@w3.org
On Tue, Apr 24, 2012 at 9:00 AM, Glenn Maynard <glenn@zewt.org> wrote:
> On Mon, Apr 23, 2012 at 12:41 PM, David Singer <singer@apple.com> wrote:
> On Sat, Apr 21, 2012 at 1:10 AM, Silvia Pfeiffer <silviapfeiffer1@gmail.com>
> wrote:
>>
>> Something like:
>>
>> 1.
>> Name-vaue pairs of header metadata are given with a name-string
>> separated from the value by a colon.
>> No control characters or separators are allowed in the name value.
>> No white space is allowed between the name and the colon (?).
>>
>> 2.
>> If the value is a single "|" character, the value is multi-line,
>> starting on the next line and ends with a line that only contains a
>> single dot.
>> The newline just before the dot-line is also not part of the value.
>>
>>
>> A quick-and-dirty ABF could be:
>>
>> metadata-header = field-name ":" field-value
>> field-name = token
>> field-value = ("|" *TEXT CRLF "." CRLF) | (*TEXT without CRLF)
>
>
> (I'm not sure; it looks more or less right, but reading ABFs has always
> given me a headache.)
Yeah, there's a bug: I need to add a CRLF behind the "|" character.
Also, it's not meant to be complete, just to be a basis for finding
out what we missed.
> Some other details:
>
> Presumably, whitespace between the colon and a single-line value would be
> stripped, eg.
>
> Key: Value
>
> would result in "Key" = "Value".
Agreed.
> If you have significant leading whitespace
> in the value you want to preserve, or if you need to encode the string "|"
> itself, then switch to the block format:
>
> Key: |
> Value
> .
>
> Key: |
> |
> .
Works for me.
Silvia.
Received on Tuesday, 24 April 2012 00:39:03 UTC