Add Hindi language support

[fromsaurav]

Description

This PR adds support for Hindi language to HeadLamp. Hindi is one of the most widely spoken languages in the world, particularly in India, and this addition will make HeadLamp more accessible to Hindi-speaking users.

Changes

• Added Hindi to the list of supported languages in config.ts
• Created Hindi translation files for:
  • app.json
  • glossary.json
  • translation.json

The translation files include commonly used UI elements, Kubernetes terminology, and general application text translated to Hindi.

Fixes #3244
Refer the attachment for demo of changes

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: fromsaurav
Once this PR has been reviewed and has the lgtm label, please assign sniok for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[illume]

Thanks.

Can you please confirm if you used machine translation?

It seems the structures generated are different to the ones we're using. Please see other files to see the structure.

The Kubernetes and other jargon words are often not translated, because there are no good translations that make sense. Please consider if words like Kubernetes, and Pods are accurate? Can you please check the Kubernetes docs to see if they use the same ones? https://kubernetes.io/hi/docs/home/

[fromsaurav]

Thank you for reviewing,

I didn't use machine translation for this work. I manually translated the content, focusing on making it natural and understandable to hindi speakers,
I'll adjust the translation files to match the existing structure used in other language files.
For Kubernetes terminology, I've checked the documentation as you suggested. I'll follow their approach of keeping technical terms like "Kubernetes" and "Pods" untranslated where appropriate, for consistency with the docs.

i'll update the pr with fixing the consistency of technical words with docs and other issues suggested,

Would you be able to share an example of a specific structural difference you noticed, so I can make sure I address it correctly?

[illume]

Nice one, thank you.

i'll update the pr with fixing the consistency of technical words with docs and other issues suggested,

Would you be able to share an example of a specific structural difference you noticed, so I can make sure I address it correctly?

I must be mistaken. I thought the error was caused by nested json. Please ignore this comment.

[fromsaurav]

Nice one, thank you.

i'll update the pr with fixing the consistency of technical words with docs and other issues suggested,
Would you be able to share an example of a specific structural difference you noticed, so I can make sure I address it correctly?

I must be mistaken. I thought the error was caused by nested json. Please ignore this comment.

@illume Thanks for the update! When i thought to take a look again for updation , i noticed there is much scope in making this fixing better, I've made all the suggested changes, keeping technical terms consistent with the Kubernetes docs. The structure now matches the other language files while maintaining natural Hindi phrasing throughout. Also reduced the PR size significantly with better output.
Pushing the changes, Thank You !

[illume]

Thanks @fromsaurav

We will have to wait for someone else who knows Hindi to review this. Will try and find someone on Monday.

Cheers!

[fromsaurav]

Thanks @fromsaurav

We will have to wait for someone else who knows Hindi to review this. Will try and find someone on Monday.

Cheers!

Yeah surely, thanks!

[illume]

Oh by the way...

We follow a linux kernel style of commit messages. With the context at the front followed by an action word and the rest.
Would you mind changing the commit to something like this? It would be a good idea to squash the commit into one commit (but we can also do that at the end before we merge if you prefer).

frontend: app: i18n: Add Hindi language

[fromsaurav]

Oh by the way...

We follow a linux kernel style of commit messages. With the context at the front followed by an action word and the rest. Would you mind changing the commit to something like this? It would be a good idea to squash the commit into one commit (but we can also do that at the end before we merge if you prefer).

frontend: app: i18n: Add Hindi language

oh sorry, my bad ! I'm fine with you squashing the commits during the merge process in the same linux kernel style. Thank you for the update!

[joaquimrocha]

Thank you @fromsaurav !