pcapriotti / pcapriotti/optparse-applicative
Internationalization of usage help
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 959
- Forks
- 123
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 1
Description
I don't need this critically, but thought I'd suggest it anyway. The "obvious" way to do it seems to me to be having messages be algebraic types, probably one user-provided and one library-provided. Something like how errors are handled in reform.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the linked Reform error-handling reference first, then inspect how optparse-applicative currently represents usage-help messages. Define how user-provided and library-provided messages should be separated and localized; done should include an agreed design and corresponding internationalized usage help.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- cli, internationalization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100