quoid
i18n and L10n
Internationalization (i18n) Localization (L10n) Translation (T9N)
@quoid talked to me a few months ago about localization considerations, since we now have developers in two languages, and we have a lot of international users.
But all the time we still have a lot of backlog and newly proposed items that urgently need to be solved and refactored should be completed first.
But we have not forgotten this consideration. Once we're done with new settings and some major refactoring. We will start the i18n and L10n process as soon as possible.
Besides English, the first supported language will be Chinese, which is one of the languages our developers use, and we have a lot of users from China. We will also add more languages based on user demand and contributor resources.
Once we complete the i18n work, we will welcome more contributors to our L10n and T9N work. We will update this issue at that time so that you can know our progress.
Languages:
- [x] English (US)
- [ ] 简体中文 - Chinese, Simplified
- [ ] 繁體中文 - Chinese, Traditional
A quick update on the progress of this issue. So far we have completed i18n for most texts and L10n for Chinese.
These files are located in:
- https://github.com/quoid/userscripts/tree/main/public/ext/shared/_locales
- https://github.com/quoid/userscripts/tree/main/src/app/_locales
Currently we adopt two implementations, one is the extension API browser.i18n, and the other is a similar custom implementation in non-extension environments, providing better flexibility.
The extension API has some limitations, for example it can only ever return the browser/system language without being able to select it in the app/extension.
In the future, we may abandon the former and unified adopt the simpler and more flexible custom implementation.