⛔ #168 feat(i18n): add next-intl internationalization scaffold +2,044 -793 20d ago by
tksuns12 ↗ analysis ↗ GitHub ## Summary
tksuns12/mike
@tksuns12's fork of Mike, quietly exploring how to make the app speak more than one language.
This is @tksuns12's fork of Mike. Right now it sits level with upstream - nothing has landed that sets it apart yet - so the interesting part is what @tksuns12 has been sketching rather than shipping.
The one thread we've seen is internationalization: a proposal to retrofit the frontend so the interface can be served in more than one language. The notable design call is that a reader's language would be remembered by a preference on their side rather than baked into the web address, so switching languages doesn't mean navigating to a different URL.
Beyond that, there isn't much to report. If you're curious whether the i18n direction has progressed, @tksuns12's GitHub is the place to look - this fork is still in its opening moves.
What's in it
- Multi-language interface (proposed) @tksuns12 has drafted a plan to let the app's frontend be presented in more than one language.
- Preference-based language selection Language would be chosen and remembered per reader rather than encoded in the URL, so switching locales doesn't change the address you're on.
Direction
i18n
Activity
A groundwork pass to make every screen translatable, without touching a single link.
Threads of work (detailed view)
tksuns12 teaches Mike to speak other languages
A groundwork pass to make every screen translatable, without touching a single link.
Pull requests (detailed view)
⛔ Closed without merge (1)
by
tksuns12 · opened 2mo ago · closed 20d ago