Remove the translation `-Z` options

[JonathanBrouwer]

Proposal

This MCP proposes to remove the compiler options for translation, that is the following 3 unstable commandline options used to translate diagnostics messages:

    -Z                      translate-additional-ftl=val -- additional fluent translation to preferentially use (for testing translation)
    -Z              translate-directionality-markers=val -- emit directionality isolation markers in translated diagnostics
    -Z                                translate-lang=val -- language identifier for diagnostic output

This MCP explicitly does not propose changing anything about the way diagnostics are currently represented, that is, struct diagnostics will still be represented by fluent messages.

Why?

• Nobody is currently working on translation, and it seems like things will stay this way
• Not all messages in the compiler are currently translatable, and it seems like it will stay this way
• It is unclear whether fluent (which is what these options explicitly refer to) is even powerful enough to properly translate diagnostic messages to other languages
• Even though these options are not in the way that much, I see no good reason to keep them

Mentors or Reviewers

I (@JonathanBrouwer) am willing to do the work necessary to make this change.

Process

The main points of the Major Change Process are as follows:

• File an issue describing the proposal.
• A compiler team member who is knowledgeable in the area can second by writing @rustbot second or kickoff a team FCP with @rfcbot fcp $RESOLUTION.
  • Refer to Proposals, Approvals and Stabilization docs for when a second is sufficient, or when a full team FCP is required.
• Once an MCP is seconded, the Final Comment Period begins.
  • Final Comment Period lasts for 10 days after all outstanding concerns are solved.
  • Outstanding concerns will block the Final Comment Period from finishing. Once all concerns are resolved, the 10 day countdown is restarted.
  • If no concerns are raised after 10 days since the resolution of the last outstanding concern, the MCP is considered approved.

You can read more about Major Change Proposals on forge.

[rustbot]

Important

This issue is not meant to be used for technical discussion. There is a Zulip stream for that.
Use this issue to leave procedural comments, such as volunteering to review, indicating that you second the proposal (or third, etc), or raising a concern that you would like to be addressed.

Concerns or objections can formally be registered here by adding a comment.

@rustbot concern reason-for-concern
<description of the concern>

Concerns can be lifted with:

@rustbot resolve reason-for-concern

See documentation at https://forge.rust-lang.org

cc @rust-lang/compiler

[jdonszelmann]

I think this is right, I don't think translation has much push at the moment, and I agree with point 2 too: not all errors will be structured diagnostics @rustbot second

[rustbot]

The final comment period is now complete, this major change is now accepted. 🎉

As the automated representative, I want to express gratitude to the author for their work and everyone else who contributed to this major change proposal.

If you think this major change shouldn't have been accepted, feel free to remove the major-change-accepted label and reopen this issue.

Note

Further progress is now tracked over at rust-lang/rust#152919.