Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ja] Translate content/en/docs/reference/glossary/customresourcedefinition.md into Japanese #46445

Closed
Okabe-Junya opened this issue May 18, 2024 · 11 comments · Fixed by #46725
Closed
Assignees
Labels
area/localization General issues or PRs related to localization good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. language/ja Issues or PRs related to Japanese language triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@Okabe-Junya
Copy link
Member

Okabe-Junya commented May 18, 2024

Note that this issue is for Japanese Speaker

This is a Feature Request

What would you like to be added

Translate content/en/docs/reference/glossary/customresourcedefinition.md into Japanese

Why is this needed

There is no Japanese translation for this page

Comments

日本語に翻訳する際は、以下のドキュメントを参考にしてください。


/area localization
/language ja
/good-first-issue

@k8s-ci-robot
Copy link
Contributor

@Okabe-Junya:
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:

This is a Feature Request

What would you like to be added

Translate content/en/docs/reference/glossary/customresourcedefinition.md into Japanese

Why is this needed

There is no Japanese translation for this page

Comments

日本語に翻訳する際は、以下のドキュメントを参考にしてください。


/area localization
/language ja
/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-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot added area/localization General issues or PRs related to localization good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. language/ja Issues or PRs related to Japanese language help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 18, 2024
@baswanthd
Copy link

/assign

@baswanthd
Copy link

Find the below link and this what you are expecting after translation.
customresourcedefinition.md

@Okabe-Junya
Copy link
Member Author

Thank you for your interest in the Japanese localization project!

Metadata keys are typically not translated. Also, note that we have some localization-specific rules; see https://kubernetes.io/ja/docs/contribute/localization/

Please note that these issues are created for Japanese speakers, thank you

@tamilselvan1102
Copy link
Contributor

tamilselvan1102 commented May 27, 2024

Find the below link and this what you are expecting after translation. customresourcedefinition.md

@baswanthd
Don't translate key words. only translate content.
Please follow the procedure as mentioned above by @Okabe-Junya

@tamilselvan1102
Copy link
Contributor

@baswanthd
I would like to raise a PR, if you are not working on it.

@bells17
Copy link
Contributor

bells17 commented Jun 6, 2024

/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jun 6, 2024
@tamilselvan1102
Copy link
Contributor

/assign

@tamilselvan1102
Copy link
Contributor

@Okabe-Junya
PRのレービュウをお願いします。

@Okabe-Junya
Copy link
Member Author

Thanks @tamilselvan1102,

When opening a PR, please include close #<issue-number> in the description (so the issue will be automatically closed when the PR is merged).

Additionally, there is no need to mention (or /cc) me when you create a PR. There are many active reviewers in the Japanese l10n team. Only mention me if there is no response after a few days.

Thank you

@tamilselvan1102
Copy link
Contributor

@Okabe-Junya
understood, thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/localization General issues or PRs related to localization good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. language/ja Issues or PRs related to Japanese language triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants