RespondKit 0.6.3 — client strings translated into 51 locales

RespondKit 0.6.3

Release notes

The shared client catalog is translated. The strings 0.6.2 moved into localization/messages now show in the user's language on iOS, Android, web and React Native: the empty state, the "Ask us anything" subtitle and the attach menu.

• 51 locales. ar, bg, bn, ca, cs, da, de, el, es, et, fi, fil, fr, fr-CA, gu, he, hi, hr, hu, id, it, ja, kn, ko, lt, lv, ml, mr, ms, nb, nl, or, pa, pl, pt-BR, pt-PT, ro, ru, sk, sl, sr, sv, ta, te, th, tr, uk, ur, vi, zh-Hans and zh-Hant. This is ReceiptGenie's shipped set, which also covers Captioner and SubPorter. Every key in the catalog is translated, not only the three surfaces that read it today. Other views still use English literals.
• Locale fallbacks. Web and React Native map legacy codes (iw, in, tl, no), choose Traditional Chinese for zh-TW, zh-HK and zh-MO, send Portuguese outside Brazil to pt-PT, reduce regional variants to the base language, and fall back to English. iOS uses Foundation's matching. On Android, Hebrew and Indonesian ship as values-iw and values-in, the codes Android still reports, and Bokmål also ships as values-no.
• Web without a host locale. When context.locale is unset, the web widget now reads the catalog and formats transcript dates using the browser language. Before, it used English.

Upgrade and compatibility

Use 0.6.3 for the npm packages, v0.6.3 for SwiftPM and 0.6.3 for Maven. No API or protocol change.

• iOS: the host app must declare a language for RespondKit's strings to show in it (ReceiptGenie declares all 51).
• Android hosts that override RespondKit strings for Hebrew or Indonesian must place the overrides in values-iw or values-in.

Operator checklist

1. Publish GitHub release v0.6.3, which runs the npm publish workflow. Publish Maven Central per docs/native/releases.md.
2. Point ReceiptGenie at 0.6.3.