- From: David Singer <singer@apple.com>
- Date: Sat, 03 Dec 2011 18:48:49 +0000
- To: Christopher Giffard <christopher.giffard@cgiffard.com>
- Cc: Simon Pieters <simonp@opera.com>, "whatwg@whatwg.org" <whatwg@whatwg.org>, Ian Hickson <ian@hixie.ch>, "public-texttracks@w3.org" <public-texttracks@w3.org>
It is also useful for the case where you are given a VTT file and have to write the HTML. It's nice not to have to work out aka guess the srclang tag value. Dave Singer (iPhone) On Dec 2, 2011, at 21:22, Christopher Giffard <christopher.giffard@cgiffard.com> wrote: > I believe an in-file language tag would be important for situations where the file isn't being rendered/parsed by a browser user agent - it could be used offline in VLC or a similar application. > > Kind Regards, > > Christopher Giffard > > On 03/12/2011, at 12:45 AM, Simon Pieters wrote: > >> On Fri, 02 Dec 2011 14:38:13 +0100, David Singer <singer@apple.com> wrote: >> >>> >>> On Dec 2, 2011, at 11:58 , Simon Pieters wrote: >>> >>>> On Fri, 02 Dec 2011 01:34:15 +0100, Ian Hickson <ian@hixie.ch> wrote: >>>> >>>>> If we are to add language information to the language, there's four ways >>>>> to do it: inline, cue-level, block-level (a section of the file, e.g. >>>>> setting a default at different points in the file), and file-level. >>> >>> 5. externally (e.g. a lang tag on the element that embeds the VTT file). (Though this is not exclusive with the above 4, and there is some argument for intrinsic tagging, as it goes with the file) >> >> This already exists. <track srclang="fr"> >> >> -- >> Simon Pieters >> Opera Software >> >
Received on Saturday, 3 December 2011 18:50:08 UTC