Re: Unicode character for CC symbol?

The obvious difference between all those video symbols and the CC button
is the CC button has language-specific characters in. Coming at this
problem from a different angle, a universal icon that doesn't have letters
in it would be a Good Thing, and would work in the proposed scheme. I have
seen such a thing, but I'm not sure how common it is.

For example this:
https://learnoasis.com/wp-content/uploads/2016/12/youtube_caption_icon.png
which I found from: https://learnoasis.com/improving-your-listening-skills/
but which does seem to be the closed caption icon used by YouTube.

The fact that YouTube has adopted a universal symbol is probably a Good
Thing that others would do well to follow. I've seen alternative versions
along the same lines in other apps too.

It might then make sense to assign a Unicode code point to such an icon as
proposed, and that would solve all these localisation issues too.



On 08/09/2017, 00:34, "Michael A. Peters" <mpeters@domblogger.net> wrote:

>On 09/07/2017 01:53 AM, Nigel Megitt wrote:
>>> Those client side options aren't really available when the CC button is
>> an image, the server must support other locales or the user is stuck
>> with the default.
>>
>> Of course they are available. Generally user interface localisation is
>> achieved by dereferencing values from a pre-defined list (e.g. a
>>numerical
>> value understood to mean the "File" menu) into the specific string or
>> resource to be presented, using some kind of lookup against a table that
>> varies based on localisation. Hence menu items will get a different
>>string
>> of unicode points for that menu for English ("File") compared to, say,
>> French ("Fichier"). It is not usually done at the level of mapping
>> individual code points into glyphs.
>>
>> I don't know how many systems localise user interface icons like this -
>>I
>> imagine that icons are generally designed to be universal. But I would
>>put
>> the selection of alternate versions in this layer rather than having a
>> single Unicode point for which glyph selection would require
>>localisation
>> awareness.
>>
>>
>
>http://tease.social/emojitest.xhtml#subgrp-audio/video_symbols
>
>That's interface elements that have unicode codepoints.
>
>To create an interface, images are not needed *except* to provide the CC
>button.
>
>With the CC button as a glyph, not only is an image not needed for it -
>but the font can design it to match the other glyphs in the font.
>
>If the CC glyph designed in the 80s really isn't universal, then yet,
>add CC glyphs for the other regions.
>
>I asked before but didn't see the response. What do the native browser
>HTML5 video players use for the CC glyph outside the united states?
>
>If CC really isn't universally understood at this point, changing the
>unicode glyph is easier than changing an image in order to localize a
>web or desktop application because glyphs can be used the webmaster or
>software designer has no knowledge of.
>
>And they would match the other interface elements as long as the font
>designer had knowledge of them, but even if the font developer didn't
>have knowledge of them, an appropriate glyph from a font that did have
>knowledge could be used.
>
>You can't really do that with images, the application designer has to
>have knowledge of every possible region specifoc version of the CC symbol.
>
>



-----------------------------
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 Friday, 8 September 2017 09:11:48 UTC