Hacker News new | ask | show | jobs
by the8472 3650 days ago
I have a font for that, but the character is unreadably small while it's perfectly fine for latin characters.

Many other unicode symbols also suffer from this problem. E.g. ␀ is the printable version of the unprintable NUL (\0) control character, but it's so small at 13.3px / 10pt CSS font size that it's difficult to distinguish from the other control pictures.

␀ ␁ ␂ ␃ ␄ ␅ ␆ ␇ ␈ ␉ ␊ ␋ ␌ ␍ ␎ ␏ ␐ ␑ ␒ ␓ ␔ ␕ ␖ ␗ ␘ ␙ ␚ ␛ ␜ ␝ ␞ ␟ ␠ ␡

How those look on display w/o pixel scaling: https://i.imgur.com/lAAyjXu.png

6 comments

Imagine if ﷽ was sized to a monospace font.
For someone who can't see this glyph, here some different renders:

http://i.imgur.com/g7igcwP.png

In the name of god, that has to be the most complex glyph I have ever seen.
> In the name of god, that has to be the most complex glyph

And actually it is in the Arabic "name of God," thanks!

https://en.wiktionary.org/wiki/%D8%A8%D8%B3%D9%85_%D8%A7%D9%...

I didn't know there's a whole ligature as a single code point U+FDFD available, thanks sscotth. The code point is also easy to remember.

(It, accidentally, also most probably represents the words first said by the Orlando shooter when calling 911, when the translation in the transcription is compared.)

Is this the biggest glyph in Unicode?

https://en.m.wikipedia.org/wiki/Biangbiang_noodles#/media/Fi...

Biang from Biang biang noodles is also fairly complex (though not supported by Unicode)

Just tried it in Emacs, renders just fine

(M-x ucs-insert FDFD)

They are also very small on my computer (Chrome on OS X 10.11.5, external non-'Retina' monitor), but they are vertically aligned instead of diagonal:

http://i.imgur.com/kKfLYgx.jpg

Interestingly in Safari the hieroglyph is shown (still small though), I wonder why Chrome can't find it?

Funny how the OS won't even try some of them...

http://imgur.com/oQEHbA7

FWIW on my screen, they're really distinguishable: https://i.imgur.com/IdUK8MV.png.
That looks like your browser is somehow misinterpreting the character set of the page. What you're seeing appears to be something like code page 437 (https://en.wikipedia.org/wiki/Code_page_437) rather than unicode.

What browser/os are you using? Is it possible you're going through a proxy that is altering the HTTP headers?

Could be that he has a font that provides code page 437-like outlines for those codepoints.
The spade symbol[0] is codepoint 9824, the acknowledge control picture[1] (␆) is codepoint 9222. They shouldn't be using the same glyph.

[0] http://www.fileformat.info/info/unicode/char/2660/index.htm [1] http://www.fileformat.info/info/unicode/char/2406/index.htm

With DejaVu they are distinguishable enough:

http://i.imgur.com/WemOI28.png

On Android N with Chrome 51

http://m.imgur.com/tKnyPad