DEV Community: Jimmy

Javanese Script Isn't Just "An Old Alphabet" — It's a Completely Different Writing System

Jimmy — Sat, 04 Jul 2026 17:18:55 +0000

Most of us think about writing systems the way we grew up with one: separate letters, one sound each, read left to right. But not every script works that way — and one great example is Aksara Jawa, the traditional Javanese script from Indonesia, which is still actively used, taught, and preserved today.
It's syllabic, not alphabetic
In Latin script, letters are independent — "k" is just "k" until you add a vowel next to it. Javanese script doesn't work like that. It's syllabic: each character already carries a built-in vowel sound.
There are 20 core characters called aksara carakan, and every one of them is pronounced with an inherent "a" sound by default. So the character ꦲ isn't just "h" — it's automatically "ha." To get a different vowel sound like "hi" or "ho," you attach a diacritic mark above, below, or beside the character instead of swapping the letter itself.
Consonant clusters need their own trick
Since every character defaults to ending in "a," writing a word that ends in a bare consonant (like the "k" at the end of "bapak") isn't as simple as just placing the letters next to each other. Javanese script uses smaller subjoined forms called pasangan, placed below or beside the main character, specifically to cancel out that default vowel.
There's also a separate set of characters (aksara swara) just for vowels that appear on their own at the start of a word, plus a special capitalized form (aksara murda) reserved only for honorifics, titles, and place names — not used across the whole alphabet like Latin capitals.
Why this matters for anyone working with text/Unicode
Javanese script actually has its own Unicode block, which means it's a real, standardized part of how text is digitally represented — not just a font trick. Scripts like this are a good reminder that "text" in software isn't a solved, universal concept. Encoding, rendering, and input methods all have to account for scripts that don't map cleanly onto the Latin alphabet most tooling assumes by default.
Trying it without learning the whole system first
If you just want to see Latin text converted into Javanese script (or the reverse) without manually working through vowel markers and pasangan rules, a translator does that instantly. I've been using Aksara Jawa Translator — it converts Latin text to Javanese script and back, has a virtual Javanese keyboard, and even supports translating text straight from an uploaded image.
Takeaway
Javanese script is a good example of how much variety exists in how humans have represented language in writing — and how much of that complexity gets abstracted away the moment you use a proper converter instead of building the mapping yourself.

Where Those "Cool Fonts" You See on GitHub, Discord & Instagram Actually Come From

Jimmy — Sat, 04 Jul 2026 17:11:30 +0000

If you spend time online — GitHub profiles, Discord bios, Instagram captions, TikTok usernames — you've definitely seen stylized text like this:

𝐂𝐨𝐨𝐥 𝐅𝐨𝐧𝐭𝐬 · 𝓒𝓸𝓸𝓵 𝓕𝓸𝓷𝓽𝓼 · Ⓒⓞⓞⓛ ⓕⓞⓝⓣ⓼ · 𝙲𝚘𝚘𝚕 𝙵𝚘𝚗𝚝𝚜

It looks like a custom font, but it isn't one. It's just Unicode — special characters that already exist in the text standard and happen to render as bold, cursive, circled, or monospace-looking letters in almost any app or browser, without needing any custom styling at all.
Why this matters even outside of "aesthetics"
For developers and content creators alike, this trick is genuinely useful:

GitHub README headers that stand out without designing a custom banner
Discord/Slack bios that look distinct from everyone else's plain text
Project launch posts on social media, where plain text is easy to scroll past
Terminal-friendly banners, since it's real text and not an image

Because it's just text (not an image or a font file), it copy-pastes cleanly into literally any input field — bios, comments, commit messages, anywhere.
The easy way to get it
You can look up the Unicode blocks and match characters manually, but that's tedious for anything beyond a few words. The simpler route is a generator that's already mapped out all the styles for you — type your text once, and copy whichever variant you like.
I've been using Cool Fonts for this — it has 170+ styles ready to go, so there's no manual lookup involved.
Takeaway
"Cool fonts" aren't magic or custom typography — they're just Unicode characters doing double duty. Once you know that, using them well (and quickly) is just a matter of having the right tool on hand.

I Built a Free Aesthetic Text Generator — Here's What the Data Taught Me About Users

Jimmy — Fri, 19 Jun 2026 05:18:33 +0000

A few months ago I launched a small side project — a free online tool that converts plain text into stylized Unicode fonts. No frameworks. No backend. Just HTML, CSS, vanilla JS, and a large Unicode character map.

The tool is called Tulisan Aesthetic and it targets content creators who want aesthetic text for Instagram bios, TikTok captions, Discord usernames, and WhatsApp statuses.

What I thought would be a weekend project turned into one of the most educational things I've shipped. Here's what I learned.

What the Tool Actually Does

Unicode contains thousands of mathematical and symbolic characters that visually resemble standard Latin letters — but aren't. This means you can "fake" font styles in plain text environments that don't support custom fonts (like social media bios).

For example:

Input:Hello World
Cursive output:𝓗𝓮𝓵𝓵𝓸 𝓦𝓸𝓻𝓵𝓭
Bold output:𝐇𝐞𝐥𝐥𝐨 𝐖𝐨𝐫𝐥𝐚
Fullwidth output:ＨｅｌｌｏＷｏｒｌｄ

The implementation is straightforward — a character map object that replaces each letter with its Unicode equivalent per style. The tricky part is handling edge cases: numbers, punctuation, non-Latin characters, and emoji spacing.

3 Things User Behavior Taught Me

Mobile-First Is Not Optional — It's Everything

Before launch, I assumed maybe 60% of users would be on mobile. The real number was over 85%.

This changed how I thought about the entire UX. The copy button needed to be large and thumb-friendly. The font list needed to scroll smoothly without jank. Input field auto-zoom on iOS had to be disabled (font-size: 16px minimum — learned this the hard way).

If you're building any tool targeting general consumers or social media users, design mobile-first from day one. Desktop is secondary.

The "Copy" Button Is the Entire Product

I initially built a clean multi-column grid layout showing all font styles at once. Looked great on desktop. Terrible on mobile.

After watching how users actually behaved, one thing became clear: they only care about the copy button. Everything else is noise.

I rebuilt the layout as a single scrollable list — each style on its own row with a clearly visible copy button. Engagement improved immediately. Time-on-site went up. Bounce rate dropped.

Lesson: identify the single action your tool exists to enable, and make that action effortless. Everything else is secondary.

SEO Traffic Compounds Faster Than You'd Expect in Underserved Niches

I did zero paid promotion. All growth came from organic search.

The key insight: most existing tools in this niche had terrible Core Web Vitals. Slow load times, layout shift from ads, unoptimized JavaScript. By building something lightweight and fast, I ranked faster than I expected — not because my content was exceptional, but because the technical baseline was simply better.

For developers building niche tools: performance IS your SEO strategy. A fast, clean tool will outrank a bloated one in an underserved niche.

The Tech Stack (Intentionally Simple)

Frontend: Vanilla HTML/CSS/JS — no framework overhead
Unicode map: JSON object with 50+ style mappings per character
Copy functionality: navigator.clipboard.writeText() with fallback for older browsers
Hosting: Static hosting (fast, cheap, zero maintenance)
Analytics: Lightweight script — no cookie banners needed

Total page weight: under 80KB. Lighthouse score: 98+. That's the goal for any utility tool.

What I'd Do Differently

Add more languages from day one. Traffic came from Indonesia, Brazil, and Spanish-speaking markets simultaneously. I wasn't prepared for that.
Build the copy feedback earlier. A small "Copied!" confirmation toast sounds trivial — users actually noticed and asked about it before I added it.
Create supporting content earlier. Blog posts targeting "how to use aesthetic fonts on Instagram" brought in significant long-tail traffic. I should have published those at launch, not three months later.

Try It

If you want to see the live tool: tulisanaestheticid.com

It's fully open to use — no login, no paywall. If you're curious about any part of the implementation, drop a comment. Happy to discuss the Unicode mapping approach or the SEO strategy in more detail.