-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
i18n support for urfave/cli #980
Labels
area/v3
relates to / is being considered for v3
help wanted
please help if you can!
kind/feature
describes a code enhancement / feature request
Milestone
Comments
coilysiren
added
kind/feature
describes a code enhancement / feature request
kind/discussion
is for discussion
area/v2
relates to / is being considered for v2
status/triage
maintainers still need to look into this
labels
Dec 7, 2019
coilysiren
added
help wanted
please help if you can!
and removed
area/v2
relates to / is being considered for v2
labels
Dec 27, 2019
This issue or PR has been automatically marked as stale because it has not had recent activity. Please add a comment bumping this if you're still interested in it's resolution! Thanks for your help, please let us know if you need anything else. |
Yes please |
I'm moving this to target 3.x given the expected scope. |
3 tasks
dearchap
added
area/v3
relates to / is being considered for v3
and removed
help wanted
please help if you can!
kind/discussion
is for discussion
labels
May 21, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/v3
relates to / is being considered for v3
help wanted
please help if you can!
kind/feature
describes a code enhancement / feature request
What problem does this solve?
We have many users of this CLI from all over the world, so it may be useful to provide translations for our error messages? Possibly ones that default to the language set by the user's environment variables? That would likely make the CLI easier to use for them.
Solution description
This is more-so a discussion and idea generation issue, rather than an explicit feature spec.
The text was updated successfully, but these errors were encountered: