[hi] Localize /en/docs/reference/glossary/app-container.md

[rolfedh]

[hi] Localize /en/docs/reference/glossary/app-container.md

Instructions

• Review a few examples of localized glossary entries.
• In the examples, notice which elements are translated and which ones are not.

Translating the frontmatter

In the frontmatter, that is, between the --- markers that enclose the first dozen lines:

• Translate the title and short_description values.
• Do not translate the id, aka, tags values. We will systematically translate those later on in a separate project.

Translating the content body

Below the frontmatter, in the content body:

• Translate almost everything.
• If you encounter a glossary shortcode, for example, {{< glossary_tooltip text="containers" term_id="container" >}}, translate the text value. But do not translate the term_id value.

Procedure:

1. In this issue, assign this issue to yourself by commenting: /assign <your_github_id>
2. Open PR [hi] Localize app-container.md #35942.
3. In the PR, select all the lines in the file and click + to comment.
4. In the comment, click the +/- suggestion icon (screenshot 2).
5. In the suggestion, localize the content to Hindi.
6. IMPORTANT: Click the Start a review button.
7. IMPORTANT: Click Review changes, Comment, and Submit review.

Note: By completing these steps, your GitHub profile will give you credit for performing a code review!

As follow-up steps, I will do the following:

• Apply your suggested localization to the PR.
• Ask a reviewer to review the localized content.
• Update the content as needed.
• Get the PR approved and merged.

This feature issue is part of the following project:

• [hi] Umbrella issue for translating glossary entries to Hindi #35600

[rolfedh]

/language hi
/good-first-issue

[k8s-ci-robot]

@rolfedh:
This request has been marked as suitable for new contributors.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

/language hi
/good-first-issue

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[bishal7679]

/triage accepted

[taniaduggal]

/assign

[nitishfy]

@rolfedh I appreciate your contribution! Here's a little suggestion:

Please assign the issue to yourself before raising the PR for that issue. @taniaduggal self-assigned her first but the PR was raised by you. This might lead to sudden confusion.

[taniaduggal]

@nitishkumar06 I firstly checked the file,it is not localize . That's why I assigned it to myself.

[bishal7679]

@nitishkumar06 Thanks for giving your valuable time 👍
Actually some misunderstanding happened here. I think @rolfedh raised a demo PR for this term in english which has not localized in hindi yet. Thats why @taniaduggal got assigned.

[rolfedh]

@nitishkumar06 @taniaduggal @bishal7679 I created two issues like this one, each linked to PRs that contain an unlocalized file. I intended to provide a way for absolute newcomers to contribute localized content by using comments. This way they don't need to sign a CLA, setting up a fork/local clone of the repo, learning git, etc.

I welcome anyone self-assigning these issues to take on the localization task. Please provide feedback to help me improve it for future contributors.

After I have this raft of issues and pull requests merged, let's do a quick retrospective. I'll use your feedback to update the templates and processes we use to help avoid any confusion as we scale this up to more and more contributors.

Here's the original explanation of this experiment: #35600 (comment)

[taniaduggal]

/assign @anubha-v-ardhan

[nitishfy]

/assign

[nitishfy]

/unassign