processing / processing/p5.js-web-editor

i18n Sync: Update Settings and SubmitSaveAllSettings Keys Across Locale Files

Open
#3,510 9 comments 0 reactions 1 assignee View on GitHub

@artonsena1a-ops is already working on this.

Since Oct 16, 2025.

Area: Translation Good First Issue Help Wanted Ready for Work
Dominant language
JavaScript
Stars
1.7k
Forks
1.7k
Avg merge
3d 4h
Merged PRs (30d)
8

Description

p5.js version

No response

What is your operating system?

Windows

Web browser and version

Chrome 1.79.119

Actual Behavior
  • Some locale files still use outdated keys, such as:

"SubmitSaveAllSettings": "Save All Settings"

"Settings": "Account Settings"

  • These values have been updated only in the English locale, where:

"SubmitSaveAllSettings": "Save All Settings" was replaced with "SaveAccountDetails": "Save Account Details"

"Settings": "Account Settings" (under AccountView) was updated to "Settings": "My Account"

  • Other locale files have not yet been updated, leading to inconsistent UI translations across languages.
Expected Behavior
  • All supported locale files should include the updated keys with proper translations:

"SaveAccountDetails": "Save Account Details",
"Settings": "My Account"

  • Outdated keys like "SubmitSaveAllSettings" should be removed.

  • The UI should reflect consistent wording across all languages when these sections are displayed.

Steps to reproduce

#3509 Refer to this PR for the changes.

Steps to Reproduce

  1. Switch to a non-English language (e.g., Spanish, French)

  2. Navigate to My Account page (previously Settings)

  3. Observe:
    - The header still says "Account Settings".
    - The save button still says "Save All Settings".

  4. Compare this with the English version, which correctly says:
    - "My Account"
    - "Save Account Details"

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.