-
-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
multi languages support for buildin cli cmd's descriptions #22761
Comments
Gitea uses urfave/cli to build a cli app, but it has no buildin translation support :( |
The idea is good, but it's not worth to spend time on it. |
Sorry, I don't think we have enough resources to do that. I proposal to close this. |
|
@delvh @wxiaoguang @lunny If it's no necessary to do this, I will close this later. |
I understood your description before. That's why I said "The idea is good, but it's not worth to spend time on it.". If you meant "commands themselves", I would say "that's impossible" at that time. The CLI is mainly for site admin, they should have the basic English ability. I ever saw some GNU tools do i18n for their CLI, in the end few people (site admin) use or like them. |
@yp05327 I think it would be possible to do this with some fairly basic changes and a little magic related to looking at locale environment variables, so I'm gonna reopen this feature request. However I'm not going to take any action to make it happen myself - at least not right now. If you're interested in making this happen reach out to me on discord and we can chat. |
At the moment, I think we shouldn't spend time on CLI i18n. The reasons are:
So, I have objection for this change at the moment ..... |
I think so. |
Feature Description
Gitea website support multi languages, but the build in cli cmd's descriptions only support English.
I think we can add multi languages support to gitea cli's descriptions.
The language will based on system setting or env variable such as
GITEA_CLI_LANG
.I will work on this
Screenshots
No response
The text was updated successfully, but these errors were encountered: