i18n

[remkop]

Ideas:

• @option(..., i18nKey="myKey") -look up myKey in ResourceBundle
• @option(..., description="A b c d") -look up A_b_c_d in ResourceBundle
• look up fully qualified field name in ResourceBundle

[remkop]

The name of the resource bundle could be fixed or specified in @Command(resourceBundle = "name").
Resource bundle keys could be based on the option name (either long or short), for positional parameters, the key could be the index. Alternatively, we could define a new annotation attribute for the resource bundle key:

@Option(names = "--option1")                             String option1;
@Option(names = "--option2", descriptionKey = "option2") String option2;
@Parameters(index = "0")                                 String param1;
@Parameters(index = "0", descriptionKey = "param2")      String param2;

This may be interesting for reference: https://github.com/tomitribe/crest#help-text

[remkop]

Note on conflicts:

• Resource bundle set in a superclass are used if subclass doesn’t set its own resource bundle
• If subclass does set its own bundle that one is used (an empty bundle essentially disables the superclass bundle)
• Bundle set by mixins are used unless the “host” command sets its own resource bundle (then the mixin bundle is ignored, even for the options and positional parameters contributed by the mixin)
• Bundle set by parent command are used for all subcommands, unless the subcommand sets its own resource bundle