Some unicode dingbats not working in TBB
Simple dingbats like the pencil doesn't work on TBB in Tails: https://www.fileformat.info/info/unicode/char/270E/browsertest.htm
The pencil dingbat is Unicode version 1.1.0 released in June, 1993. https://www.fileformat.info/info/unicode/char/270e/index.htm I could be mistaken, but it probably should be supported in TBB.
Also, black flag dingbats don't seem to work on TBB on either Windows or Gnu+Linux: https://www.fileformat.info/info/unicode/char/2691/browsertest.htm This came out in Unicode 4, which was released 14 years ago. It's not very anarchist of us to not be able to view unicode black flags in Tail's main browser. :-)
It isn't all of the dingbats though, for instance, the Up Down Arrow dingbat does work: https://www.fileformat.info/info/unicode/char/2195/browsertest.htm
a regular multiplication sign works https://www.fileformat.info/info/unicode/char/00D7/browsertest.htm
but a "MULTIPLICATION X" does not https://www.fileformat.info/info/unicode/char/2715/browsertest.htm
Multiplication X is also Unicode 1.1 which is 24 years old.
When surfing the web, it isn't unusual to come across some of these and it looks silly when they don't render.
I got these example errors while trying to figure out what was going on with http://fed.wiki.org and ended up writing a github issue about it, only to close it after I found out that it was a Tor Browser bug: https://github.com/fedwiki/wiki/issues/97 There might be some background info in there worth reading if someone wants to dig into this.
Some people also were talking in this TBB issue about certain emojis not working in any TBB running in Gnu+Linux: https://trac.torproject.org/projects/tor/ticket/18172
I know that TBB is now only allowing whitelisted fonts. I'm assuming that this was just overlooked after TBB started to do the whitelisting and transfered over to the Noto fonts. I'm curious though, are there fonts that are shipped in Tails that display dingbats well that should be whitelisted in TBB?
I found that the "noto color emoji" font just started getting packaged in Debian. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849042
It was said that this should allow for color and black and white emojis once it is finished, but I don't know how to verify that.
In the mean time, that link also said that https://packages.debian.org/jessie/ttf-ancient-fonts offers black and white emojis. I wonder if it would render the dingbats too. I don't know how to look through the font to see if it has all of the Unicode 1 thru Unicode 4 dingbats (and beyond) though. If it does, perhaps we could whitelist it in the next TBB release.
I did see that Noto Emoji (not to be confused with Noto Color Emoji) has the pencil dingbat I referenced above: https://www.google.com/get/noto/#emoji-zsye Someone on that Noto Color Emoji Debian Bug page I linked to above said that they couldn't find the source code for it though. If Noto Color Emoji doesn't have these legacy black and white dingbats, does anyone know how to find the Noto Emoji source code?
I also looked at https://wiki.debian.org/Fonts/UnicodeCoverage to see if it might describe any packages that cover these old dingbats, but I wasn't able to figure anything out there. Perhaps it helps someone else.
In closing, can anyone help me figure out what debian packaged font should be whitelisted to get all these old Unicode Characters to work on webpages in TBB on Gnu+Linux systems? Can anyone inspect ttf-ancient-fonts to see if it is a good whitelisting font candidate for this or tell me how to do it?
#1 Updated by mercedes508 about 2 years ago
- Assignee set to Kurtis
- Priority changed from Normal to Low
I just tried to load those pages on both Tails and regular Tor browser, and the result is the same.
So it's Tor Browser specific, which means that you should probably send your request to Tor Browser rather than Tails bug tracker.
#3 Updated by Kurtis about 2 years ago
If anyone else finds this page and wants to follow the progress of getting this fixed, I'm going to be working in https://trac.torproject.org/projects/tor/ticket/18364 from now on to try to get this fixed.
#4 Updated by intrigeri about 2 years ago
If anyone else finds this page and wants to follow the progress of getting this
fixed, I'm going to be working in
https://trac.torproject.org/projects/tor/ticket/18364 from now on to try to get
Excellent! (and thanks for adding the link :)