The apps currently send localized strings across the JS bridge to mobile-html. Initially (T205550) this was a convenient tradeoff, but it's becoming more of a burden as more functionality is added to the page. For example, if we wanted to start showing reference types (book, website, etc) as show in the designs for T244615, the clients would have to be updated to pass all of those strings across the bridge.
- Utilize banana-i18n and the strings from the iOS app to read localizations from the server-side and client-side JS (patch open)
- Expose new endpoint for /data/i18n/pcs endpoint via RESTBase T247096
- Add the project to translatewiki (tracked by T246659)
- mobile-html is localized based on the language of the page regardless of user Accept-Language since it's part of the article content - de.wikipedia.org shows German strings, es.wikipedia.org shows Spanish strings
- Accept-Language is used to detect variant for wikis that support variants (zh, sr, etc)
- If a string is missing for a given language, english is used as a fallback