30 min | i18n of back-end error messages (ad hoc conversation) | @Zak Burke | @Julian Ladisch's institution has allotted him some time for UXPROD-371 (i18n of error messages received from APIs); even though it is not highly ranked overall it is crucial to a select audience. His initial foray led to STRIPES-750, which some front-end devs discussed, concluding that backend modules should be responsible for providing localized text in their responses given an Accept-Languages header in the requests they receive. Depending on whom you ask, English-only responses from APIs constitute a bug (some UI devs see it this way) or an unimplemented feature. If this work is pushed to the back-end, there are implications for other teams, i.e. it's not as simple as saying "Julian can implement this in mod-foo" because mod-foo may forward a response from mod-bar, etc. (NB: the work won't be isolated to a single module on the front-end either). Next steps: present UXPROD-371 before the TC (goal: ask for the conclusions reached in STRIPES-750 to be accepted or rejected; @Zak Burke ) present an initial proposal for handling l10n on the backend (goal: ask for endorsement of the proposal; @Julian Ladisch ) make sure we invite @Peter Murray , who is wise in the ways of Lokalise. @md331 (Deactivated) notes that there were many bumps on the road to building a successful integration.
|