Skip to content

Fix: Improve Hindi translations for accuracy and consistency#2422

Open
swdeveloperabhi wants to merge 3 commits intoOWASP:masterfrom
swdeveloperabhi:fix-hindi-translations
Open

Fix: Improve Hindi translations for accuracy and consistency#2422
swdeveloperabhi wants to merge 3 commits intoOWASP:masterfrom
swdeveloperabhi:fix-hindi-translations

Conversation

@swdeveloperabhi
Copy link

Changes Made:

  • Reviewed Hindi translations against English content
  • Corrected inaccurate and inconsistent translations
  • Improved clarity and readability

Testing:

  • Verified changes locally

Impact:

Improves user experience for Hindi-speaking users.

Closes #2381

@swdeveloperabhi
Copy link
Author

Hi, I noticed that the CI checks are failing due to test coverage dropping below the required threshold. Since my changes are limited to translation updates, I believe this might not be directly related to my modifications.

Please let me know if there’s anything specific I should adjust, or if this is expected.

@sydseter
Copy link
Collaborator

sydseter commented Feb 28, 2026

@swdeveloperabhi You do not need to worry about the test coverage. I have several Hindi speakers that will review your work. I hope you will accommodate their comments and requests. I will be merging your work once all comments are resolved. Stay turned.

@sydseter
Copy link
Collaborator

And apologies about the mixup between Hindu and Hindi. I mean no disrespect. I am also aware there are several variants of Hindi. I don’t mind having several dialects represented as separate translations. I just need someone to take ownership as I am not a Hindi speaker myself.

@Mysterio-17
Copy link
Contributor

Overall, this looks like great work, the translations are clear, consistent, and technically accurate. Thank you for taking the time to contribute and improve the Hindi localization

I’ve added a couple of small suggestions inline, but otherwise this looks good.

@swdeveloperabhi
Copy link
Author

@sydseter No worries at all.

@swdeveloperabhi
Copy link
Author

@Mysterio-17 Thank you for the feedback—I’m glad the translations meet the expectations. I’ll go through the inline suggestions and update the PR accordingly.

@swdeveloperabhi
Copy link
Author

I’ve addressed the suggested changes. Please let me know if anything else needs improvement.

@Adarshkumar0509
Copy link
Contributor

image hii @swdeveloperabhi I Just noticed something small while going through the diff on line 322 in the CR7 card, it looks like there's an extra Hindi character before desc: `ाdesc:` instead of `desc:`. Might be worth fixing to avoid any yaml parsing issues.

@Adarshkumar0509
Copy link
Contributor

@swdeveloperabhi Just noticed that the AZK card hasn't been updated in this PR. As mentioned by @sydseter in issue #2381, the name "Ryan" on the AZK card should be replaced with "Adrian". Could you please include that change as well?

@SachinAditya
Copy link
Contributor

Thank you for pointing this out.
You’re absolutely right regarding gender agreement. Updating to “कर सकती है” maintains grammatical consistency. I appreciate the suggestion.

@Mahaboobunnisa123
Copy link

@swdeveloperabhi, I focused mainly on language consistency and readability.

Many of the sentence rewrites read more naturally in Hindi and improve clarity while keeping the technical meaning intact (especially across several VE, CR and C cards). The phrasing feels less literal and more readable for Hindi-speaking users. Overall flow is better in multiple descriptions, which makes the cards easier to understand during review or gameplay.

This might be worth checking:

  • In a few places, card blocks look like they may contain repeated or mixed id: entries (for example around some VE / AT / SM sections). I may be wrong here, but this looks like a possible edit/merge artifact, so a quick YAML validation would help.
  • Please confirm this against the English source: some paragraph entries for example T00020, T01210, T01290 look like they change meaning rather than only improving wording. It would be good to verify whether these were intentional content updates or translation refinements.
  • I noticed mixed usage of attacker names (sometimes transliterated into Hindi, sometimes kept in English). Not necessarily incorrect, but a consistency pass could make the style more uniform.
  • Similar terms like “validation / सत्यापन / वैलिडेशन” appear in different forms - this might be worth standardizing so terminology stays consistent across the deck.

Overall, the translation quality looks solid, these suggestions are mainly for consistency and clarity.

@sydseter
Copy link
Collaborator

sydseter commented Mar 1, 2026

@swdeveloperabhi When it comes to names, we should keep the English version and not use the Hindi equivalent. Reason being that these names are real individuals that exist. Sometimes project members other times chapter leaders.

@swdeveloperabhi
Copy link
Author

@sydseter @Mahaboobunnisa123 @Adarshkumar0509 Noted, thank you for the feedback. I’ve incorporated the suggested changes and updated the PR.

@sydseter
Copy link
Collaborator

sydseter commented Mar 1, 2026

@Mahaboobunnisa123 @Adarshkumar0509 have a final look. It looks to me like your commentary have been addressed. Please go through one more time and flag if you have more suggestions. Otherwise tell me it looks good enough and I’ll merge it.

@Adarshkumar0509
Copy link
Contributor

@sydseter Went through the latest changes translations look accurate and natural, names are correctly kept in English, and the AZK card has been updated to Adrian as requested. From my end, this looks good to merge 👍

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

Successfully merging this pull request may close these issues.

Review the Hindu websiteapp 3.0 translation against the english

6 participants