You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
A clear and concise description of what the bug is.
After traditional Chinese translation introduced to the project, the translation key for Chinese is now zh-CN(Simplified Chinese) or zh-TW(Traditional Chinese) instead of zh. Old 'zh' key doesn't work anymore.
To Reproduce
Steps to reproduce the behavior:
Go to 'config.yml'
Set the language key to 'zh'
Start lazygit
Lazygit returns "language not found"
Expected behavior
A clear and concise description of what you expected to happen.
Load Chinese translation
Screenshots
If applicable, add screenshots to help explain your problem.
Version info: Run lazygit --version and paste the result here Run git --version and paste the result here
Additional context
Add any other context about the problem here.
There is a PR #2842 relates to that.
Note: please try updating to the latest version or manually building the latest master to see if the issue still occurs.
The text was updated successfully, but these errors were encountered:
Describe the bug
A clear and concise description of what the bug is.
After traditional Chinese translation introduced to the project, the translation key for Chinese is now zh-CN(Simplified Chinese) or zh-TW(Traditional Chinese) instead of zh. Old 'zh' key doesn't work anymore.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Load Chinese translation
Screenshots
If applicable, add screenshots to help explain your problem.
Version info:
Run
lazygit --version
and paste the result hereRun
git --version
and paste the result hereAdditional context
Add any other context about the problem here.
There is a PR #2842 relates to that.
Note: please try updating to the latest version or manually building the latest
master
to see if the issue still occurs.The text was updated successfully, but these errors were encountered: