[Bug 28255] [webvtt] no provision for indicating overall content language(s) [I18N-ISSUE-420]


--- Comment #12 from Silvia Pfeiffer <silviapfeiffer1@gmail.com> ---
(In reply to nigelmegitt from comment #11)
> It may be true that language can be specified externally, but that's not
> especially helpful for asset management. 

Particularly in asset management, you have a database which contains this
information and is much more easily searchable than the content files
themselves. I don't buy this argument.

> I would argue also that the spec is incomplete in that it includes the
> WebVTT Language Objects to indicate when the language is different from the
> surrounding text language but no mechanism to indicate what the outer level
> language is. The obvious fix for this would be to add a language header with
> file scope, e.g. a reserved keyword for a metadata header, like "lang" so
> you might have a file that begins:
> lang: en-GB
> [rest of file]

There didn't seem to be enough of a use case from practitioners to make it
worth the effort at this point in time. It seems to be an academic request
without a real need.

You are receiving this mail because:
You are on the CC list for the bug.

Received on Thursday, 1 October 2015 23:54:32 UTC