Somali and English from the first day, never later. Everyone agrees with that sentence until the deadline. Then the Somali strings become a ticket for after launch, and the ticket stays open.
So we stopped treating the second language as a translation step. A field does not exist until it has both. Here is a request form the way ActiveLoop draws one, with the strings it is built from underneath.
| String | Somali | English |
|---|---|---|
| form.title | ||
| field.name | ||
| field.phone | ||
| field.district | ||
| error.required | ||
| action.send | ||
| notice.received |
Ready to ship. Every string has Somali and English.
Try breaking it
Clear one of the Somali strings. The form does not quietly fall back to English. It shows the gap where the person at the counter would see it, and the check below it says the form would not ship. That check is the whole idea. A missing string is a bug you can count, not a feeling.
Switch which language reads first. Nothing moves except the order, because both lines were always there. Send the form empty and the message comes in both, too. An error a person cannot read is not an error message.
Still on the bench
The Somali here is ours, and it has not yet been read at a real counter. That is the test that matters. If a label reads wrong to you, that is exactly the kind of report we want, and the community page says where to send it.


