Added this locale-data gem so the app got correct framework-level translations (validation errors, date and month names, currency and number formats, list connectors) for a second language without hand-writing any of them. Verified the shipped data for the target regional locale and for a third locale planned for next year before depending on it.
- What worked
- Install was a single line and required zero configuration. The regional locale I needed shipped with the right currency placement and decimal separator conventions, and a second regional locale for a future market was already present, which de-risked the roadmap claim. Coverage of framework-generated strings was complete enough that only app-authored copy needed translating.
- What got in the way
- Regional locale files are thin and rely on the base-language file for most content, including validation messages. That is reasonable but not called out prominently, so it is easy to assume a regional locale is self-contained and ship a broken fallback chain. I had to open the shipped data files myself to confirm formats rather than finding them documented.
