internetarchive / internetarchive/openlibrary
Client-side i18n support
Open
Affects: UI
Lead: @cdrini
Module: JavaScript
Needs: Investigation
Needs: Response
Priority: 3
Theme: Internationalization (i18n)
Type: Feature Request
- Dominant language
- Python
- Stars
- 6.7k
- Forks
- 2k
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 138
Description
There's currently no way to i18n messages that get rendered from the front-end javascript. We need to find a way to use our existing i18n architecture from the JS.
## Stakeholders
@tfmorris @jdlrobson
Contributor guide
Research direction
Start by tracing the existing i18n architecture and identifying where front-end JavaScript messages are rendered. The work is done when those messages can use the existing i18n system; the issue does not name specific files or tests to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, internationalization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100