W3C home > Mailing lists > Public > www-international@w3.org > October to December 2015

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

From: <bugzilla@jessica.w3.org>
Date: Fri, 30 Oct 2015 16:22:12 +0000
To: www-international@w3.org
Message-ID: <bug-28255-4285-o31Ihz7GGT@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28255

--- Comment #20 from Addison Phillips <addison@lab126.com> ---
(In reply to nigelmegitt from comment #19)
> (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.

No, 'affects that language' suggests that it changes what the language of the
text actually is. The use case you cite is precisely why I filed this issue in
the first place. What you (and I) mean is 'affects the processing of the cue'.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Friday, 30 October 2015 16:22:14 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:41:09 UTC