Why Every Language Matters
Why treating smaller or regional languages as first-class languages changes who can participate, learn, and contribute.
People notice when their language is treated as a real language and when it is treated as an optional afterthought.
That distinction affects trust, participation, comprehension, and willingness to contribute.
Why English-only systems exclude people
English-only software often feels normal to the people building it because they already operate comfortably in English. But the same interface can quietly increase cognitive load for students, volunteers, librarians, administrators, and community contributors who think, read, or teach more naturally in another language.
The result is not only inconvenience. It is unequal participation.
Why smaller languages matter in practice
Smaller languages are often discussed as cultural symbols. They are also practical working languages.
They are the languages people use when they:
- learn new material
- explain a process to family or colleagues
- introduce a tool in a school or library
- document local knowledge
- decide whether software feels meant for them
Let Books context
Let Books is built for multilingual educational book collections and multilingual communities. Respecting Slovenian, Bosnian, Croatian, Macedonian, Albanian, and both Serbian scripts is not cosmetic. It is part of whether the project is serious about the people it claims to serve.
A better default
A better default is simple.
Design the project so more than one language can belong from the beginning. Then let quality improve in stages.
Durable takeaway
Every language does not need identical maturity on day one. But every language that a project claims to support should be treated as a legitimate destination, not a decorative checkbox.