- From: Nigel Megitt <nigel.megitt@bbc.co.uk>
- Date: Wed, 26 Aug 2015 14:47:58 +0000
- To: Michael Dolan <mdolan@newtbt.com>, "'Timed Text Working Group'" <public-tt@w3.org>
- Message-ID: <D2038FB8.26560%nigel.megitt@bbc.co.uk>
The sRGB primaries are different to the BT-2020 primaries. They're still essentially red, green and blue though. Also problematically, it's common to use 10 or 12 bits per channel, which wouldn't work at all well with a #12345678 hex RGBA expression. From: Michael Dolan <mdolan@newtbt.com<mailto:mdolan@newtbt.com>> Date: Wednesday, 26 August 2015 15:43 To: 'Timed Text Working Group' <public-tt@w3.org<mailto:public-tt@w3.org>> Subject: RE: FW: ATSC Liaison to W3C Resent-From: <public-tt@w3.org<mailto:public-tt@w3.org>> Resent-Date: Wednesday, 26 August 2015 15:43 Right. I believe the proposal was to leave the primaries alone. I’m not sure how well that would map to BT-2020 primaries though... In any event, I think the right answer is to ask for more information. Regards, Mike From: Glenn Adams [mailto:glenn@skynav.com] Sent: Wednesday, August 26, 2015 7:18 AM To: Nigel Megitt <nigel.megitt@bbc.co.uk<mailto:nigel.megitt@bbc.co.uk>> Cc: Timed Text Working Group <public-tt@w3.org<mailto:public-tt@w3.org>> Subject: Re: FW: ATSC Liaison to W3C btw, I think the suggestion that the syntax/value space of tts:color would not change to accommodate this will not work; we can't have #RRGGBB mean something that is not RGB, we can't have rgb() and rgba() mean something that is not RGB; at least we can't do so without completely disregarding history and name to meaning correspondence; we would need to introduce a new generic color function, e.g., color() to introduce generic color spaces; it would also be better for compatibility purposes as it would signal use of another space; On Wed, Aug 26, 2015 at 2:42 AM, Nigel Megitt <nigel.megitt@bbc.co.uk<mailto:nigel.megitt@bbc.co.uk>> wrote: With permission from Mark Richer, making this available on public-tt. Nigel From: Mark Richer <mricher@atsc.org<mailto:mricher@atsc.org>> Date: Thursday, 13 August 2015 21:36 To: Nigel Megitt <nigel.megitt@bbc.co.uk<mailto:nigel.megitt@bbc.co.uk>>, "tmichel@w3.org<mailto:tmichel@w3.org>" <tmichel@w3.org<mailto:tmichel@w3.org>> Cc: 'Rich Chernock' <rchernock@trivenidigital.com<mailto:rchernock@trivenidigital.com>>, 'Madeleine Noland' <mnoland@noland-consulting.com<mailto:mnoland@noland-consulting.com>>, "chomer@pbs.org<mailto:chomer@pbs.org>" <chomer@pbs.org<mailto:chomer@pbs.org>> Subject: ATSC Liaison to W3C Dear Nigel, Attached you will find a liaison from ATSC to W3C regarding closed captions and subtitles. Best regards, Mark Mark Richer President Advanced Television Systems Committee, Inc. (202) 459-6690<tel:%28202%29%20459-6690> ---------------------------- http://www.bbc.co.uk This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated. If you have received it in error, please delete it from your system. Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately. Please note that the BBC monitors e-mails sent or received. Further communication will signify your consent to this. ---------------------
Received on Wednesday, 26 August 2015 14:48:35 UTC