W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > October 2011

[Bug 14552] <track> support // and /* */ comments everywhere except in the signature line

From: <bugzilla@jessica.w3.org>
Date: Wed, 26 Oct 2011 09:30:07 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1RIzoF-0000jF-MX@jessica.w3.org>

--- Comment #9 from Philip Jägenstedt <philipj@opera.com> 2011-10-26 09:30:07 UTC ---
(In reply to comment #8)
> Please let's not use // for comments - that would make all URLs really
> unreadable.

As mentioned, // occurs in 2229/65643 files. There are 3056 individual lines
that match, and 2939 (96%) of those look like URLs (grep -i http://).

I don't think this is a big deal of caption or subtitle tracks, but for
metadata tracks I have to agree that this has the potential to make a mess of

> Also, I've seen "#" used in live captioning similar to ">>" as speech markers,
> though I can't find an example now.
> I could live with /* */ for intra-cue comments. IIUC, right now anything inside
> < and > that is not a defined tag is ignored, so that would also work, though
> it's not as future-proof as a separate markup.

/* */ (and //) isn't really intended to be intra-cue or inter-cue, it's
pre-processor-like and works as if it wasn't there at all. For example, this
would work:

00:01.000 --> /*00:02.000

00:02.000 --> */00:03.000

It creates a cue from 1 to 3 seconds with the cue text Bar. (The ability to due
this is in itself not important, I'm just stressing that comments work exactly
the same wherever you use them.)

> More important than intra-cue comments, though, is a way to comment out
> complete cues. Since that creates a section, it would be best if that could be
> done the same way as the sections that we need for headers for metadata, inline
> cue settings, and inline CSS. I can live with the suggestion to use the "-->"
> marker as a landmark to separate such sections.

Or is this some other suggestion that the COMMENT --> blocks? If not, do you
really want to comment out each cue individually?

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 26 October 2011 09:30:13 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:02:06 UTC