Fix structural duplication and localization errors in the hindi translation file

[Urvi2727]

p5.js version

p5.js 1.11.11

What is your operating system?

Windows

Web browser and version

All browsers

Actual Behavior

Description

A review of the currently implemented Hindi localization file (hi.json) reveals significant structural defects, redundant code blocks, and incomplete translations. These legacy issues in the codebase need to be resolved to ensure proper JSON parsing and a consistent experience for Hindi-speaking users.

---

Identified Errors in Existing Codebase

• Major Structural Duplication: Within the current hi.json, the JSON restarts after the AssetList section, redefining several objects (Nav, Feedback, Searchbar, CollectionList, etc.) for a second time. This results in duplicate key errors in many standard JSON parsers.
• Incomplete Localization: The existing "Banner" key contains English text ("Donate Today!...") rather than the intended Hindi translation.
• Missing Keys: Essential strings for library version management (CustomVersionTitle and CustomVersionInfo) are currently absent from the Preferences section.
• Inconsistent Vocabulary: The term "Asset" is inconsistently handled in the live file, translated as "संपत्ति" (literal) in the Auth block and "ऐसेट" (technical) in the AssetList block.
• Technical Mistranslation: The current shortcut for renaming a variable is translated as "चरण का नाम बदलें" (Change Step Name), which is contextually incorrect for programming. It should be updated to "वैरिएबल का नाम बदलें".
• Redundant/Fragmented Validation: Validation logic in the current version is fragmented across ReduxFormUtils and NewPasswordView with overlapping and inconsistent phrasing.

Expected Behavior

The hi.json file should provide a consistent and fully localized experience for Hindi-speaking users. Specifically:

• Structural Integrity: The JSON should be valid and free of redundant or duplicated blocks.
• Full Localization: All UI elements, including the "Banner" section, should be translated into Hindi.
• Accurate Terminology: Technical terms like "Asset" and "Variable" should use standard transliterations ("ऐसेट" and "वैरिएबल") that are familiar to the developer community.
• UI Completeness: Missing phrases for version management (e.g., CustomVersionTitle) in the Preferences tab should be present and correctly displayed.
• Consistent Validation: Password and email validation messages should follow a unified phrasing across the platform.

Steps to reproduce

Steps:

1. just visit https://editor.p5js.org/
2. select हिन्दी as language

[Urvi2727]

Hey @raclim, here is the approach I took to audit and resolve the issues in hi.json:

Approach & Resolution

• Structural Audit: I identified and removed a massive redundant block where the JSON restarted after AssetList, redefining multiple objects like Nav and Feedback.

• Technical Standardization: I replaced the literal translation "संपत्ति" (property) with the standard technical transliteration "ऐसेट" (asset).

• Contextual Correction: I updated the RenameVariable string from "चरण" (step) to "वैरिएबल" (variable) to better reflect JavaScript programming concepts.

• Missing Key Sync: I manually integrated absent strings for library version management (CustomVersionTitle, CustomVersionInfo) and consolidated fragmented password validation logic.

• Localization Completion: I localized the English Banner text and updated legacy social media labels to ensure full UI coverage.

This cleanup ensures the file is structurally valid for parsing and uses terminology familiar to the Indian developer community.
Since the PR is ready, it would be great if you could assign me to it.

[Urvi2727]

Hi @raclim ma'am, I've opened PR #3813 with a fix. Whenever convinient, I'd really appreciate a review. Thanks!