Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support translating the compiler diagnostics #4

Open
Manishearth opened this issue Feb 19, 2020 · 2 comments
Open

Support translating the compiler diagnostics #4

Manishearth opened this issue Feb 19, 2020 · 2 comments

Comments

@Manishearth
Copy link
Member

Manishearth commented Feb 19, 2020

This is mostly a tracking issue, the actual implementation of this should be done working with the compiler and release team. But feel free to discuss the overall plan here.

Previous discussion: https://internals.rust-lang.org/t/translating-the-compiler/10376

Blocked on rust-lang/rust#61132

Once we have that implemented as a custom derive , we need to:

  • Provide a way to produce separate Fluent (or other format) files based on these diagnostics. This can either be done by making the compiler build produce auxiliary files (by having the proc macro be impure), or by writing a separate tool that finds and parses these
  • Sync these to a separate repo, hooked up to Pontoon, where they can be translated
  • Allow the compiler to use the Fluent strings picked up from the sysroot instead
  • As a part of the release process of Rust, allow language packs containing these strings to be installed via rustup
  • Allow the compiler to pick up the "default" language from a rustup setting
@Manishearth
Copy link
Member Author

cc @estebank

@davidtwco
Copy link
Member

Just learnt about this issue: work has started on this, there's a document summarizing the effort and a document with a list of all pull requests contributing to the effort.

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

No branches or pull requests

2 participants