Re: Unicode character for CC symbol?

It is available in Font Awesome (http://fontawesome.io/icon/cc/) using the private use space in Unicode…

Thanks,
AWK

Andrew Kirkpatrick
Group Product Manager, Accessibility
Adobe 

akirkpat@adobe.com
http://twitter.com/awkawk







On 9/5/17, 06:07, "Nigel Megitt" <nigel.megitt@bbc.co.uk> wrote:

>This seems on the face of it problematic. The trouble is that there is no
>single representation for the idea of "closed captions" globally. Whereas
>in the US it might be represented by something like "CC", in the UK where
>closed captions are known more usually as subtitles, it is often
>represented by "S". I may be wrong about this but I don't think Unicode
>would normally create a code point for a glyph that has
>territory/culture-specific variant forms.
>
>Having said that, a globally usable label of some sort that means "this is
>the button for switching closed captions on and off" could be useful.
>
>
>On 03/09/2017, 22:33, "Michael A. Peters" <mpeters@domblogger.net> wrote:
>
>>According to 
>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FFile%3AClosed_captioning_symbol.svg&data=02%7C01%7C%7C044b96f883e0476fbf5408d4f446d6c7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636402032489256383&sdata=um37Q5hz%2FuCfvJ67yslDrq5qF%2FPPwrRp77uZTxr7mwQ%3D&reserved=0 that
>>symbol has been released into the public domain.
>>
>>It would make sense then for there to be a unicode character for it, in
>>the technical range (where play and fast forward and pause glyphs exist)
>>but I could not find one.
>>
>>For me where it would be useful is when designing html5 players, the
>>standard audio players in most browsers don't show the CC button even
>>when there are track elements provided and custom JS to display them.
>>
>>If it had a unicode character, I could modify my webfont to include it
>>there and just specify the character glyph (in a span with title
>>attribute of course) like I do with the other player control elements.
>>
>>I can suggest it to the unicode group but I wanted to make sure it
>>doesn't already exist and I'm just not finding it, and also if it
>>doesn't, hear any arguments as to why it might be a bad idea.
>>
>
>

Received on Tuesday, 5 September 2017 14:43:55 UTC