-
Notifications
You must be signed in to change notification settings - Fork 14.5k
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
Link more clearly to localized READMEs #10622
Comments
Sorry for not replying sooner. And I think you've exactly understood my proposal!
In case of A, Thank you for your opinion, I appreciate it!
In case of B, I agree with your opinion. But what do you think of adding a link process about the file For example, it replace [
If so, localization team would be easier to add link |
That's a good point! ✨ So any PR that addresses this issue needs to specify that localizations of |
This commit adds a link about Localizing Kubernetes Documentation in README.md's Contributing to the docs section. Fixed : kubernetes#10485, kubernetes#10622 Signed-off-by: Claudia J. Kang <claudiajkang@gmail.com>
This commit adds a link process about the l10n README files in localization.md. Fixed : kubernetes#10485, kubernetes#10622 Signed-off-by: Claudia J. Kang <claudiajkang@gmail.com>
@zacharysarah Thank you! I created #10669 PR about this issue. 😄 |
* New link about Localizing Kubernetes Documentation This commit adds a link about Localizing Kubernetes Documentation in README.md's Contributing to the docs section. Fixed : #10485, #10622 Signed-off-by: Claudia J. Kang <claudiajkang@gmail.com> * Update l10n guide about adding l10n README files. This commit adds a link process about the l10n README files in localization.md. Fixed : #10485, #10622 Signed-off-by: Claudia J. Kang <claudiajkang@gmail.com>
This is a...
Problem
We can make it easier for localization teams to find
README-**.md
files (where**
is a two-letter language code) by linking to them from the main README and/or from the localization guidelines.Continuing #10485 (comment) as a separate issue:
@claudiajkang 👋
I apologize! 🙇 To make sure I understand, here are the specific actions I see proposed in your feedback. Are these correct? 👇
Proposed Solution
/content/en/docs/contribute/localization.md
to include links to variousREADME-**.md
files.README-**.md
files from the main EnglishREADME.md
file.README-**.md
files to include contact information in English.@claudiajkang Do I understand your proposal correctly? ☝️
If so, then:
A. I think updating the main README.md is an excellent idea. 👍
B. I'm ambivalent about adding
README-**.md
links tolocalization.md
. 😐Ideally contributors with a
README-**
available in their language would be readinglocalization.md
in that language as well, in which case the links would be circular. That's not inherently bad; I'm just not convinced that it's good.Page to Update:
/cc @tnir @idealhack
The text was updated successfully, but these errors were encountered: