Nice, but way too many abbreviated descriptions and no way to see the full name of a symbol without clicking on it. Needs a tooltip / title.<p>Or better, if what feels like 90% of all symbol names are abbreviated, your design simply doesn't work. This is especially apparent in the "arrows" section.
I’m looking at the currency block. Each box has a colored “drop shadow”. I spent a minute or so trying to figure out what the significance of the color is. Finally, I noticed that the color appears to cycle between cyan, magenta, and yellow. Is this a design element only, or do the colors actually have some meaning with respect to the symbol?
Purely cosmetic.
In hindsight, probably unnecessary — but once you add color, it’s hard to stop
Not the author, but it seems to be only stylistic
This is beautiful. Love the design. When I read the title I thought it was "one page per Unicode" so I click on the codes and hope a page will open with a giant Unicode where I can see about it in details.<p>Oh well! Still good.<p>When I click the "Click to copy" my UI reflex tells me to look for a "Copied!" or similar acknowledgement. But I don't see one, so there's uncertainty if it was copied safely to my invisible clipboard or not.<p>Please keep making this, it's good! What inspired you for the design? I like this style, and notice it around, but can't pinpoint.
Some constructive criticism:<p>Please don't display text directly on the grid background image. It makes it impossible to read the text easily. Currently, this is the case when you open the page for a specific symbol in the 'Usage & Context' section.
Very nice.<p>I found it odd, that tapping on a square “highlights” it, by making it “pop,” but nothing else really happens.<p>It took me a bit to figure out that I need to actually select the arrow in the upper right corner, to get the page.
Ohh, this is great! I actually was looking for something like this the other day. Thanks for sharing and nice work!
Planning to add more symbol-specific notes (confusables, common pitfalls, rendering quirks).
Curious what details people usually look for but can’t find.
I don't know how to find the ideal font for the missing glyph on my environment which is BSD.<p>Using the `unicode' command from plan9userspace, for example<p><pre><code> unicode 2ff0-2fff
</code></pre>
the last three symbols are shown inside emacs as squares with the four hex values inside.<p>Typing in the search field `2fff' finds `no match found'.
Good catch — I just pushed an update based on this.<p>The symbols search now supports code-point lookup, so you can search by:<p>U+2FFF<p>0x2FFF<p>plain hex (2fff, 4–6 digits)<p>This makes it possible to jump straight to a symbol page even when the glyph doesn’t render locally and you only have the code point (like the Emacs/BSD case you described).<p>One limitation to note: some symbols aren’t covered by common or default system fonts, so they may still appear as tofu boxes depending on the font stack. That’s a font coverage issue rather than Unicode itself.<p>Appreciate you calling this out — this was exactly the kind of workflow gap I wanted to catch.
On mobile, the expand icon covers 1/4 of each character so it is hard to see what they are
I'd like the hint to display the hidden parts of each box when hovered.<p>I don't need to be told on each one to "Click to Copy".<p>But nice concept.
I really like this. I appreciate the many "copy" buttons that make it easy to grab various font values once I find a character. Good job!
> We use cookies and similar technologies for analytics (Google Analytics) and session recording (Microsoft Clarity). Ads may be enabled in the future (Google AdSense). By continuing to use this site, you acknowledge this notice. You can manage cookies in your browser settings. EU/UK users: this serves as our cookie notice.<p>No. Please just give me an option to reject all tracking cookies instead of just kicking me in the face with a done deal.<p>Whoever wrote this 'EU/UK users: this serves as our cookie notice' is ignorant of the actual law. Have a look at:<p><a href="https://gdpr.eu/cookies/" rel="nofollow">https://gdpr.eu/cookies/</a>