Skip to content

Localization team discussion issue #178

Open
@sebasmagri

Description

@sebasmagri

During RustDay in Mexico City, erickt, brson and I discussed about the benefits of having a dedicated localization team in the project.

The goals of such a team would include:

  • Orchestrate Rust content i18n
    • Documentation (partnering with -docs)
    • Videos (Amara)
    • Blog posts / Websites
  • Coordinate efforts to bring/improve i18n/l10n tooling into the ecosystem
  • Evaluate feasibility and implement i18n/l10n into the core tools
    • Compiler error messages (LANG/LC_* compliant on *nix?)

What else should we consider? What examples from other communities and open source projects can we use?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions