Skip to content

i18n: make remaining user-facing CLI error messages translatable#460

Open
AngryDavee wants to merge 1 commit into
zcash:mainfrom
AngryDavee:i18n/translatable-cli-error-messages
Open

i18n: make remaining user-facing CLI error messages translatable#460
AngryDavee wants to merge 1 commit into
zcash:mainfrom
AngryDavee:i18n/translatable-cli-error-messages

Conversation

@AngryDavee

Copy link
Copy Markdown

Small contribution toward #321 (ensure all CLI messages are translatable).

I audited the CLI output for untranslated user-facing strings. Most are already wrapped in fl!. The remaining user-facing strings I found are two error contexts that reach the user through the Error Display impl in error.rs:

  • components/chain.rs: "ChainState indexer is not running"
  • components/json_rpc.rs: "Only one RPC bind address is supported (for now)"

This PR wraps both via crate::fl! and adds the corresponding entries to i18n/en-US/zallet.ftl (a new ## Chain errors section, and err-init-single-rpc-bind alongside the other init errors).

Per the exclusions in #321, I deliberately left untranslated:

  • .expect() panic messages (internal invariants)
  • JSON-RPC error strings

Verified locally with cargo build -p zallet.

Happy to adjust scope per your intent for the issue (for example, if the (for now) bind-address message is intentionally left untranslated as a temporary limitation, I can drop that one).

Refs #321

Wraps the two remaining user-facing error-context strings that surface in
CLI output (components/chain.rs and components/json_rpc.rs) in the fl!
Fluent framework, and adds the corresponding entries to
i18n/en-US/zallet.ftl. Leaves .expect() panic messages and JSON-RPC errors
untranslated, per the exclusions noted in the issue.

Refs zcash#321
@AngryDavee AngryDavee force-pushed the i18n/translatable-cli-error-messages branch from 2301105 to 0c36cb6 Compare June 7, 2026 21:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant