Does the Options title support customization?

[ice909]

I want to do internationalization, but the Options: title don't seem to be customizable

[phlptp]

probably not easily right now. It would probably take a custom formatter to do that. Might be something to consider going forward though

[ice909]

One more

This Positionals: can I customize it?

// add sub command install
    auto *cliInstall =
      commandParser.add_subcommand("install", _("Installing an application or runtime"))
        ->group(CliBuildInGroup)
        ->fallthrough();
    cliInstall->usage(_(R"(Usage: ll-cli install [OPTIONS] APP

Example:
# install application by appid
ll-cli install org.deepin.demo
# install application by linyaps layer
ll-cli install demo_0.0.0.1_x86_64_binary.layer
# install application by linyaps uab
ll-cli install demo_x86_64_0.0.0.1_main.uab
# install specified module of the appid
ll-cli install org.deepin.demo --module=binary
# install specified version of the appid
ll-cli install org.deepin.demo/0.0.0.1
# install application by detailed reference
ll-cli install stable:org.deepin.demo/0.0.0.1/x86_64
    )"));
    cliInstall
      ->add_option("APP",
                   options.appid,
                   _("Specify the application ID, and it can also be a .uab or .layer file"))
      ->required()
      ->check(validatorString);

[phlptp]

I'll have to get back to you on that not something I have looked into much

[ice909]

Okay, thank you.

[phlptp]

with the recent updated to the formatter this is possible

auto fmtr=app.get_formatter();
\\this will change the label name
fmtr->label("POSITIONALS", "positionals");

recognized labels are "POSITIONALS", "REQUIRED", "Usage", "OPTIONS", "SUBCOMMAND", "SUBCOMMANDS", "Env", "Needs", "Excludes", and all the type names

this is only available in Main until a 2.5 release is made, which will hopefully be in the near future.

[phlptp]

Adding an answer with some of the details from previous reply.
The answer to the question is yes, CLI11 support customization of most fields.

See Formatting.
Recognized labels that can be changed are:

"POSITIONALS", "REQUIRED", "Usage", "OPTIONS", "SUBCOMMAND", "SUBCOMMANDS", "Env", "Needs", "Excludes", and all the type names.

These can be set by

auto fmtr=app.get_formatter();
\\this will change the "POSITIONALS" label name
fmtr->label("POSITIONALS", "positionals");

This is currently available in the main code branch and soon to a 2.6 release

[ice909]

How long will it take to get to 2.6?

[henryiii]

@phlptp, let me know when you think it's ready. I notice all PRs seem to be in.

[phlptp]

Other than an update to the changelog and readme, I think everything we want to change for a 2.6 release is in place.