Clarify or unify the four localization and translation features in the project view

[Ceciliai]

What are you trying to do that you can't?

What happened?
After using the Translate feature in the Learn environment, there is currently no option to return to English or switch to another language once a translation has been applied.

I first noticed this limitation while testing the Evaluate 16–21 section of Learn → The Verse (1/8). Once I selected Chinese as the target language, the interface and content remained permanently in Chinese. Even refreshing or reopening the page did not restore the English version.

---

Steps to reproduce:

1. Open the Learn environment, e.g., The Verse 1/8.
2. Navigate to Evaluate 16–21.
3. Click the Translate button in the bottom toolbar.
4. Select 中文 (Chinese) as the destination language.
5. Try switching back to English or choosing another language.

---

Expected behavior:

Users should be able to toggle freely between English and other languages (e.g., Chinese).

The system should provide a clear and accessible way to revert to the original English interface.

Ideally, the language switch could also be used dynamically — for example, letting bilingual learners compare both versions.

---

Actual behavior:

Once translation is applied, there is no visible control or option to switch back to English.

Even reloading the page or reopening the scene keeps the selected language active.

The lack of a toggle makes it inconvenient for bilingual or multilingual users who learn more effectively by reading both languages.

Why this is an important improvement:

Many learners on the platform are bilingual or multilingual (for example, international students, heritage speakers, or language learners).

For these users, reading both English and their native language helps them better understand programming concepts.

The current one-way translation design limits flexibility and accessibility.

A simple toggle or “Reset language to English” option would make the experience smoother and more inclusive.

---

What is your idea?

Suggested enhancements:

Add a language toggle button to switch between English and other available languages.

Provide a “Return to English” or “Reset language” option in the Translate menu.

Optionally allow side-by-side bilingual view in future updates for educational clarity.

[amyjko]

This is a misunderstanding of the purpose of the translate functionality. That feature translates code in a project into other languages, adding those languages to the implementation. It does not change the language the code is rendered in.

This confusion reveals a general design problem that we have to resolve: there are four different translation features in the interface:

• Translate: Adds translations to a project's code
• Interface locale chooser: Changes the languages used in the user interface (but not the project)
• Editor locale chooser: Changes the preferred language of the editor, only showing the names, text literals, and documentation with the chosen locale
• Output locale chooser: Changes the preferred language for textual output.

These show up in four different places in the interface, leading to ambiguity about their different purposes. Creators are also not reading tooltips or instructions, which limits our ability to teach creators their different purpose.

Labeling this needs design and updating title to reflect the learnability problem.