'Sounds' preference misses play and pause button symbols

[-Meanwhile-]

Seen on hrev52849 x86_gcc2:

The 'Sounds' preference application allows the user to test a sound and provides two buttons for that (placed in the bottom right corner).

Both buttons don't have a symbol indicating 'play' and 'pause' (or 'stop', I don't remember...).

[humdinger]

Works here. Maybe you've set a system font that doesn't include the two UTF symbols \xE2\x96\xB6 and \xE2\x96\xA0?

There's no need to prefix a ticket with "[QA]".

[-Meanwhile-]

Yeah, I use Verdana. But it should work with any font, really.

The '[QA]' was added in case these tickets move to KapiX's Kiwi TCMS in the future (easier to select), but okay I'll leave it out from now on.

[rrobgill]

[wrongness deleted]

Sounds may need to specify noto sans display for the buttons.

[humdinger]

The default font has been changed to Noto Sans Display, as far as I know.

@Meanwhile: maybe use the "Keyword" for QA instead.

[rrobgill]

You're right, I got that entirely backwards.

The change was to Noto Sans Display, with geometric-shapes fully populated. The symbols will work out of the box.

[-Meanwhile-]

But Haiku (like any OS of past and present) allows the user to install his/her own font of choice, so the OS shouldn't have any issue with that.

There are other ways to draw a simple black triangle (play) and a square (stop) or two vertical rectangles (pause) on top of a button.

[pulkomandy]

We are supposed to have a font fallback system to find a suitable font when the selected one is missing characters. But I guess it was not adjusted when we switched to Noto Display.

[diver]

Same in Web+ with History->Back/Forward buttons.

[diver]

Also MediaPlayer Fullscreen shortcut is missing.

[diver]

However, Play and Stop buttons are drawn in Sounds.

[pulkomandy]

Now the font overlay is working better so this issue is solved, I think.

There are still symbols missing from the Noto fonts for various keyboard shortcuts (enter key, backspace key, ... in keymap preferences for example). This may be solved by updating to a newer version of the Noto fonts as they keep improving coverage of unicode symbols.

There isn't much to do if none of the fallback fonts actually provide the symbol.

[diver]

Isn't it a dupe of #14034?