Skip to content

I18n: normalize runtime and operator-facing messages to a single primary language #32

@francescobianco

Description

@francescobianco

Summary

User-facing strings are mixed between English and Italian across diagnostics, docs-adjacent assets, and parts of the validation flow. In agent-driven environments this inconsistency makes failures harder to classify and parse automatically.

Reproduction

  1. Inspect responses, comments, and generated guidance across the repo.
  2. Notice the language switches in operator-facing and user-facing text.

Expected

One primary language for runtime/user-facing messages, or a clear i18n strategy.

Actual

The project mixes languages without an explicit policy.

Suggested scope

Start by normalizing runtime errors and test-facing strings to English, then optionally add translated docs separately.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions