New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
minor: make i18n support and Chinese translation #3790
Conversation
- make i18n using i18next - add Chinese (Simplified) support
- split translations from i18n.ts to several .ts files in lib/gui/app/i18n - make a README for new language changes - add zh-TW instead of only zh-CN
An error occurred whilst building your landr site preview:
|
Thanks, nice work @RoderickQiu why the check fails is described here and here, the |
@RoderickQiu Whilst I still occasionally comment on some of the issues, I no longer have anything to do with the Etcher project 🙂 |
Optimized several translations. This commit itself is only a patch, but as a pull request must have at least one commit with a change-type. Change-Type: minor
more direct string-concatenation, thanks to @lurch
Yeah unfortunately I believe the ResinCI logs are only viewable by Balena employees? 🤷 ("Resin" is what "Balena" used to be called https://www.balena.io/blog/resin-io-changes-name-to-balena-releases-open-source-edition/ ). |
lib/gui/app/i18n/en.ts
Outdated
flashSucceed_other: 'Successful targets', | ||
flashFail_one: 'Failed target', | ||
flashFail_other: 'Failed targets', | ||
to: 'to ', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With the recent changes, I think message.to
and message.target
are now unused?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, you are right. Will delete them later.
Ahh...So how can I contact a balena employee? Those public members of balena github team doesn't seem to be connected with etcher project?? Could you help @mcraa you seems like an active maintainer, thanks. |
Don't worry @RoderickQiu the CI is not that reliable sometimes the upload fails after a successful build sometimes the worker does not start.
I hope you can reproduce it, otherwise I will have a look later. |
Oh yeah I ran that script and it showed that type-error. This problem really seems weird, might be a problem of i18next or the CI itself?? But surprisingly, by changing all the However, as the test script itself is not i18n-ed now, some asserts are failing. But I'm sure that could be solved soon. |
- use `import * as i18next from 'i18next';` instead of `import i18next from 'i18next';` and add an specific env to bypass mocha test - optimized several translations
according to a suggestion of @lurch
The build was ok, just the upload failed at the end. |
Yes @RoderickQiu, we will run it again |
Hello, any update on this? Does it means that I should push a blank commit to let it mergeable again? |
No @RoderickQiu, you are good. |
@balena-ci test |
Hello, any update on this? Just asking. |
Hi, sorry for this taking so long. |
@mcraa @builder555 @zwhitchcox any of you folks have any bandwidth to get this over the line? Looks like an extremely valuable contribution... |
@RoderickQiu hello, thanks for you patience. Could you please rebase on master and resolve a couple of conflicts to get this over the line. |
Hello, glad to see some conversation again. However, I've been quite busy lately and I hope I can be freer next week to do some stuff. |
Currently, the new CI does not work well with PRs from external repos (security reasons). |
@mcraa you should go ahead and do that anyway as external contributor flow may take a while (it's not trivial). |
@mcraa external contributor support has shipped, so @RoderickQiu can now rebase, resolve conflicts and hopefully push one last time. |
OK, but sadly I just directly went forward for a merge... And of course it failed and it seems that I cannot revert it... |
Please rebase on master. there shouldn't be any modifications of files under |
Sorry for my delay, but I've never done a rebase and failed to do this on the master. I had a second try just for now. After a unsuccessful attempt which again turned out to be a merge, I finally realized the way to make a rebase. However, after the rebase it seems that every commit come to co-assign with my name... Is that normal to have this? Please, have a look at https://github.com/RoderickQiu/etcher/tree/i18n-conflict-resolve-2 and if it's satisfying, I will open a new pull request base on that branch. Or if I am messing up things, please tell me because I've never done that. @ab77 |
Replaced by #3936 |
Add the long-wanted i18n support using i18next, fixed #308 and fixed #3692.
Tested on macOS 12 and it's been running fluently.
Example (zh-CN on macOS):
It works generally fine and has support for more languages, as shown in this markdown.
However, there are few problems:
I sincerely hope that my pull request can be merged.