Previously, notifications were handled by their respective qubes, and installing non-latin fonts in those qubes resolved the issue. But now that notifications have become centralized, do we need to install fonts in dom0?
Sadly by design the new notification daemon/agent eats & replaces a large subset of Unicode characters which are known for security issues (I can provide link to source if needed).
If showing notification with those characters is essential, the best bet would be deleting qubes-notification-aget from template(s) which should show such text like r4.2.x
Not essential, but having question mark style symbols instead of the actual Unicode characters looks ugly.
I personally agree. Currently it shows U+FFFD unicode character (�). I would have preferred question mark (?) or even a text suggestion the message contained unicode characters with security issues.
Or even better, I would have preferred this was configurable.
So the bottom line is, either we have to decentralize notifications again or put up with the ugly question-mark placeholders.
There is a 3rd way. Compiling notification proxy with filters removed for specific characters you need ![]()
It is here:
It means no third option ![]()
Such an irony that the notification pop-up ate
emoji.
But seriously talking, if you open an issue about this (to allow a subset of characters based on user config), I might work on it in long run. It could be done at notification proxy level (which is written in Rust)l or at libqubes-pure level (which is written in C language).
I’ve opened the issue: #10495