Skip to content
This repository has been archived by the owner on Dec 12, 2024. It is now read-only.

Chinese (zh) language option needs to be enabled in the interface #80

Closed
novusnota opened this issue Mar 4, 2024 · 1 comment
Closed
Assignees
Labels
i18n Internationalization (i18n) of English content
Milestone

Comments

@novusnota
Copy link
Member

  • Middleware and routing should enable language switching (next.config.js + new middleware.js in the root)
  • All the pages should get their empty Chinese counterparts, so that Chinese translators may start filling those in

Until then i18n support in routing is only implicitly enabled (one may add a /en prefix to any routes and they would continue working smoothly).

This issue is made as a follow-up to #79 in attempt to decrease the size of individual PRs.

@novusnota novusnota added enhancement i18n Internationalization (i18n) of English content labels Mar 4, 2024
@novusnota novusnota self-assigned this Mar 4, 2024
@novusnota novusnota added this to the v1.3.0 milestone Apr 25, 2024
@novusnota novusnota removed this from the v1.3.0 milestone May 3, 2024
@novusnota novusnota added this to the v1.4.0 milestone May 14, 2024
@novusnota novusnota modified the milestones: v1.4.0, v1.5.0 Jun 24, 2024
@novusnota novusnota modified the milestones: v1.5.0, v1.6.0 Sep 13, 2024
@novusnota
Copy link
Member Author

Resolved in tact-lang/tact#880, alongside with the migration of the docs to the compiler repo

@novusnota novusnota modified the milestones: v1.6.0, v1.4.0 Sep 30, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
i18n Internationalization (i18n) of English content
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants