yarlinghe

6 ms·

1.
by yarlinghe 9mo ago
Happy new year from China !!
2.
by yarlinghe 9mo ago
One thing I’ve noticed building a small “use it and leave” tool is that the models tend to self-select into roles. For me, Codex ended up being the reliable executor for actual logic and glue code, while Claude Code (especially the frontend
3.
by yarlinghe 9mo ago
24h update after the Show HN — quick recap. Based on the feedback here, I spent the last day tightening a few core things: - Navigation / mobile: tapping a card now opens the symbol page directly; copy is a separate, larger button. The
4.
by yarlinghe 9mo ago
Great example — thanks for the context. I added explicit linking for paired glyph parts (left/right halves) and reference links in Notes. This kind of symbol history is exactly the gap I want to fill.
5.
by yarlinghe 9mo ago
Good point. I added a Notes section and reworked “Related” to focus on things people actually get confused by (pairs, confusables, same block), not just category adjacency.
6.
by yarlinghe 9mo ago
Agreed. Updated the HTML section to recommend writing the literal character + UTF-8 by default. Numeric refs/entities are now explicitly framed as legacy / edge-case references.
7.
by yarlinghe 9mo ago
You’re right — the main index is curated. I added a /codepoint/… fallback so pasting a literal character or U+XXXX always lands you on a dev-friendly encoding page, even outside the curated sets. I also clarified this in the UI co
8.
by yarlinghe 9mo ago
Added a small “Font tips (if you see □)” section with system font notes and Noto suggestions. Also added a codepoint fallback page so you can still inspect encodings even when the glyph doesn’t render locally.
9.
by yarlinghe 9mo ago
Agreed — the small expand target was a mistake, especially on mobile. I switched to “tap card = open details” and moved copy into a dedicated, larger button. Much clearer now.
10.
by yarlinghe 9mo ago
Noted. Fixed.
11.
by yarlinghe 9mo ago
You’re right. The abbreviations (arrows in particular) made scanning worse than it should be. I’ve pushed a quick update: full names on hover/focus, plus a Compact / Readable toggle for the grid. Thanks for the nudge.
12.
by yarlinghe 9mo ago
Yep — fully agree. For modern HTML/CSS/JS, you should just write the character and serve UTF-8. The entities / codes are there purely as reference for legacy cases, debugging, or when you only have a code point and no rendere
13.
by yarlinghe 9mo ago
Yeah, mobile is rougher than desktop right now. Thanks for flagging it.
14.
by yarlinghe 9mo ago
Good points. The hover hint could definitely do more useful work, and the repeated “Click to Copy” is probably overexplaining. UI polish still very much in progress
15.
by yarlinghe 9mo ago
Purely cosmetic. In hindsight, probably unnecessary — but once you add color, it’s hard to stop
16.
by yarlinghe 9mo ago
Fair point — you’re right to call this out. I’ve now removed Microsoft Clarity (no session recording/heatmaps), and GA4 is opt‑in with a real “Reject all” option (default off). This is already deployed.
17.
by yarlinghe 9mo ago
Thanks — glad the copy buttons are useful. That was exactly the goal.
18.
by yarlinghe 9mo ago
Good catch — I just pushed an update based on this. The symbols search now supports code-point lookup, so you can search by: U+2FFF 0x2FFF plain hex (2fff, 4–6 digits) This makes it possible to jump straight to a symbol page even when the g
19.
by yarlinghe 9mo ago
Planning to add more symbol-specific notes (confusables, common pitfalls, rendering quirks). Curious what details people usually look for but can’t find.
20.
Show HN: One clean, developer-focused page for every Unicode symbol(fontgenerator.design)
198 points by yarlinghe 9mo ago|82 comments
21.
Show HN: Free Online Font Generator – Bold, Stylish Text Converter(fontgenerator.design)
1 points by yarlinghe 1y ago|0 comments
22.
Show HN: GlitchText – Free Online Zalgo and Weird Text Generator(glitchtext.cool)
1 points by yarlinghe 1y ago|0 comments