UI/UX Terminologies for Hmar & Mizo
Photo credit: image by pngtree.com
Teaching Technology to Speak Hmar and Mizo
I’ve realized lately that language in technology is about more than just words—it’s about context. When we use an app, we don’t just read; we navigate. But for Hmar and Mizo speakers, that navigation often feels broken. This is why I’ve decided to focus my project on creating a dedicated UI/UX translation dataset for our languages.
The Context Trap
The biggest hurdle isn’t vocabulary; it’s intent. Take a simple English word like “Next.” * Is it the next person in a line?
- Is it the next page in a book?
- Or is it the “Next” button on a signup form?
In Hmar or Mizo, the “right” word changes depending on that answer. Right now, if you use Google Translate for a Mizo website, it often translates “Home” as “In” (meaning a literal house) instead of something like “Tualbul” (the starting point/main hub). It feels clunky and unnatural, like the technology doesn’t actually “know” us.
Why This Matters
If we want our languages to survive and thrive in the digital age, they have to feel intuitive. If an app feels “wrong” or confusing in Mizo, people will just switch back to English. A dedicated UI/UX dataset would fix this by:
- Ensuring Accuracy: Using terms that fit a screen, not just a dictionary.
- Consistency: Making sure “Settings” or “Submit” means the same thing whether you’re on a banking app or a social media site.
- Better Adoption: Making technology feel like it was actually built for us.
The Struggle of a Native Speaker
Even as a native speaker, I’ll admit this is harder than I thought. I find myself staring at words like “Submit” or “Cancel,” trying to find the version that sounds natural for a button. Some words don’t have a direct 1:1 translation, and others require a bit of creative thinking to fit the digital context.
| Term | Hmar | Mizo |
|---|---|---|
| Next | Anawk | Aleh |
| Home | Tuolbul | Tualbul |
| Submit | Thawlut | Pekluh |
| Settings | Siemremna | Siamremna |
Moving Forward
This is the direction I’m committing to. Once I finish the initial draft of the dataset, I’m going to need help. I’ll be seeking verification and feedback from other speakers to make sure these aren’t just “my” words, but words that work for everyone.
This isn’t just a technical task for me; it’s about making our digital future feel a little more like home.
Update (March 2026)
Since I first wrote this, I’ve moved from theory to messy, hands-on practice—and it has been a major reality check.
I spent a significant amount of time editing .po and .mo files on Linux Mint, eventually translating the entire desktop panel. But the experience taught me two things. First, the sheer volume of strings in a modern desktop environment is staggering; it is simply too much work for one person to maintain alone.
To keep the project manageable, I decided to “strip down” the scope. I started over with a minimalist Ubuntu Server base and a lightweight Window Manager (WM), figured that fewer UI elements meant a more achievable translation goal. I even got as far as translating parts of the Subiquity installer before taking a step back.
The second realization was more personal: UI Shock. Even as a native speaker who has used computers for decades, seeing my own language on the screen was surprisingly disorienting. After years of “thinking” in English-language interfaces, the translated UI felt “unfriendly” at times, and I found myself getting confused by terms I thought I knew. It made me realize that building a native-language digital world isn’t just a linguistic hurdle—it’s a psychological one. We aren’t just translating words; we’re trying to re-wire how we navigate the digital space.
The Refined Strategy: Hybrid Translation
After all these experiments, I’ve decided to change my approach once again. I’ve realized that even when a translation is contextually correct, it can still feel “out of place” because our digital muscle memory is so deeply rooted in English.
Instead of trying to translate every single button and menu item, I’m moving toward a Hybrid Model. The goal isn’t to create a 100% Mizo or Hmar interface, but to create one that is actually useful.
My new focus will be on translating:
- Errors: So users know exactly what went wrong.
- Warnings: To prevent accidental data loss or security issues.
- Confirmations: To ensure the user is fully aware of the actions they are taking.
I believe this is the most sustainable way forward. By keeping standard navigation terms in English, we avoid the “UI Shock” and maintain familiarity, while using our native languages for the most critical communication—where clarity and understanding matter most. It’s not about translating the whole world; it’s about making the most important parts of it accessible.
