fix(hi): localize remaining English tags and strings in Hindi glossary#3615
fix(hi): localize remaining English tags and strings in Hindi glossary#3615NETIZEN-11 wants to merge 2 commits intocncf:mainfrom
Conversation
NETIZEN-11
requested review from
Alianait,
Jacob953,
Okabe-Junya,
Rocksnake,
Saim-Safdar,
Submarinee,
aliok,
brunoguidone,
canogluonur,
hanyuancheung,
hwchiu,
inductor,
jessicalins,
jihoon-seo,
johnlinp,
kaitoii11,
kirkonru,
mertssmnoglu,
naonishijima,
ntheanh201,
seokho-son,
shurup,
thaomike,
thuanpham582002,
tico88612,
tym83,
waleed318,
ydFu,
yuichi-nakamura and
yunkon-kim
as code owners
NETIZEN-11
requested review from
92nqb,
Arindam200,
CathPag,
DaveVentura,
Imtiaz1234,
asem-hamid,
bcubk,
caniszczyk,
electrocucaracha,
guillaumebernard84,
hlipsig,
iamNoah1,
krol3,
mitul3737,
nate-double-u,
raelga,
ramrodo,
sajibAdhi,
seb-835 and
sestegra
as code owners
✅ Deploy Preview for cncfglossary ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
shurup
left a comment
shurup
left a comment
There was a problem hiding this comment.
Hi! I don't see any tags being actually translated in the i18n/hi.toml file. Am I missing something?
Please also be aware that if this PR aims to make the translation for the Hindi glossary, it shouldn't affect files from any other localisations. Otherwise, you'll need to get approvals from all the translation teams, which you don't really want. The same is relevant for modifying the layout/partial files in the same PR — why are they affected?
Finally, see the note regarding DCO (i.e. "Action required" above). Clicking the relevant link displays more details on how to resolve this issue.
|
Hi @shurup, Thank you for the review and the feedback. You’re right — I’ll update the I’ll also address the DCO requirement and update the commit shortly. Please let me know if there is any preferred approach for handling the translations. |
…tion - Fix translation quality issues throughout the file - Replace English mixed terms with pure Hindi translations - Add complete sign language section with proper Hindi terminology - Ensure consistent translation quality throughout Signed-off-by: Nitesh <nitesh@example.com>
NETIZEN-11
force-pushed
the
fix/tag-localization
branch
from
cd0a894 to
84e222b
Compare
|
Hi @shurup, I've updated the PR to address the feedback.
Please let me know if anything else needs to be adjusted. |
- Rename 'cloud native apps.md' to 'cloud-native-apps.md' - Rename 'service discovery.md' to 'service-discovery.md' - Fix status capitalization in service-discovery.md - Add missing tags field in service-discovery.md - Fix tags format in cloud-native-apps.md Signed-off-by: Nitesh <nitesh@example.com>
3 participants
Summary
This PR completes the localization of remaining English tags and strings in the Hindi glossary section.
What Has Been Done
Why This Change Is Important
Some tags and strings in the Hindi glossary were still appearing in English, which created inconsistency in the localized content. This update ensures a fully localized and consistent experience for Hindi readers.
Closes #3615
Please let me know if any refinements or terminology adjustments are required. I would be happy to improve further.