Back to journal

Localization reaches beyond the visible heading

On November 7, I worked on Romanian and English copy across locdemunca.ro. A page can have the correct translated heading while its smaller interactions still use the other language. Notifications, map labels and error messages are easy to miss during a quick visual review, yet they become important precisely when someone needs help understanding what happened.

One change made the notification region's accessible name follow the route language. This matters even though the label is not a large block of visible text: it describes the region to assistive technology. Another localized the titles used for grouped map markers, retaining the actual marker count. Switching languages therefore changes the description around the data, rather than changing or inventing the data itself.

The work also carried the selected language into shared contact and newsletter requests and their fallback error text. A failure message should remain understandable in the language of the form that produced it. In the pricing helpers, recognized standard badges and feature phrases gained consistent Romanian and English labels. Unknown custom text continued through unchanged. That avoids turning a localization pass into an uncontrolled rewrite of content supplied elsewhere.

The larger correction was merged on November 7. These examples show the practical scope of the work: translate the words owned by the application at the place where people encounter them, including less visible and unsuccessful states. They do not imply changes to prices, plan benefits, stored content or the underlying action. A language switch should help someone understand the same product, not quietly give them a different product.

Reflection

For locdemunca.ro, bilingual consistency depends on the whole interaction. Headings introduce a page; small labels and recovery messages carry people through it. Reviewing both layers makes localization more than a check of the first screenful.