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


--- Comment #19 from nigelmegitt <nigel.megitt@bbc.co.uk> ---
(In reply to Addison Phillips from comment #17)
> I agree with Martin's comment #15.
> (In reply to Simon Pieters from comment #16)
> > It seems to me there are two bugs here:
> > 
> > 1. It is not specified that an external language definition actually affects
> > the language of the cue text.
> Affects is probably the wrong word. Indicates is probably a better choice. 
> Probably the best you can do here is allow an external language definition
> to indicate the language of text (including the cue text) in the file, in
> the absence of local-to-the-file information.

Actually 'affects' is correct since AIUI the text rendering should take the
language into account: the same set of code points can be differently mapped to
glyphs (including variant glyphs) and laid out depending on which language
applies. Another reason why indicating language correctly is not academic.

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

Received on Friday, 30 October 2015 13:52:29 UTC