Building a dictionary for a language the web ignores
348 words, one static page, no backend. What it takes to give a low-resource language a real learning tool.
When we started building a learning tool for Bodo, we went looking for the resources a learner would expect: a dictionary, a phrase list, verb tables, something to practise against. What we found was scattered, partial, and mostly written for linguists rather than for people trying to learn.
So we built the dictionary ourselves — 348 words, on one static page, with no backend at all.
Low-resource is a design constraint, not a footnote
A well-served language comes with spell-checkers, corpora, translation pairs and a hundred apps. A low-resource language comes with a handful of PDFs and a community that is doing the work by hand. If you wait for the tooling to arrive, you wait forever.
The useful move is to build the smallest thing that is genuinely helpful: a word list a learner can search, offline, on the phone they already have.
Why static and offline
Every dependency you add is a reason the tool stops working. A server can go down, a connection can drop, an API can change its terms. A static page has none of those failure modes.
- No build step. The source is the artefact; it will still run in ten years.
- No backend. Nothing to pay for, nothing to secure, nothing to migrate.
- No network. The dictionary loads once and then lives on the device.
What a word list has to do
A dictionary for learners is not the same as a dictionary for scholars. It has to answer the question a beginner actually has: what is this word, and how do I say it? That means plain definitions, a pronunciation cue, and enough examples to place the word in a sentence — not etymology and not a citation apparatus.
We kept the entries short on purpose. Long entries look thorough and get skipped.
Small tools compound
A single dictionary will not save a language. But it is one more place where the language exists online, one more thing a learner can open without asking permission, and one more piece that someone else can build on. For languages the web ignores, that is how the work gets done — a small, finished thing at a time.
Comments
Powered by GitHub Discussions. Sign in with GitHub to join the conversation.