Open Okabe-Junya opened 2 weeks ago
To move forward this PR, I would like to do the following:
Thanks so much for this!
Could you update this PR to add a section to the CNCF Localization Guides page (/docs/localization/README.md) to introduce these language-specific guides?
I think it would be good to have an English version of this as well (even if it's very rough or just an outline). I'd like to use this work as a template or starting point for other languages. I can't read Japanese, but I assume that there is a process being laid out here that could be generalized.
Thank you, @nate-double-u!!
Could you update this PR to add a section to the CNCF Localization Guides page (/docs/localization/README.md) to introduce these language-specific guides?
Ok!! I added ## Localization READMEs
section, https://github.com/cncf/techdocs/pull/259/commits/bb84976125b46934604070bf0be76448f275bcee.
I think it would be good to have an English version of this as well (even if it's very rough or just an outline)
SGTM!! Now, I create localization README template and will open another PR - IMO, it would be better to create another PR. Thank you :)
Thank you, @nate-double-u!!
😊
Could you update this PR to add a section to the CNCF Localization Guides page (/docs/localization/README.md) to introduce these language-specific guides?
Ok!! I added
## Localization READMEs
section, bb84976.
Perfect, thanks!
I think it would be good to have an English version of this as well (even if it's very rough or just an outline)
SGTM!! Now, I created localization template and will open another PR - IMO, it would be better to create another PR. Thank you :)
That's a good idea, it is a separate (related) thing, and should be in a separate PR—good call.
I think that running npm run fix:format
locally will fix the format/link checks.
This doesn't have to happen yet—we've still got time before the Japanese localization reviews are in.
Thank you :)
I think that running npm run fix:format locally will fix the format/link checks.
TBH, prettier does not work well for Japanese, since prettier breaks line after a certain number of characters (Please note that Japanese doesn't break lines except "。" (like .
))
So, I want to disable linter (at least the Japanese README)
That's fair—I think you can disable things per folder. @chalin to confirm as the lead on the reformatting project (note, they are away this week)
I’ve disabled prettier for Japanese README, https://github.com/cncf/techdocs/pull/259/commits/e2e6bf10fbda711801d0e6fceb5e3f0f0fe2695a
(I'll revert it if there are any issues.)
Hi all. Thank you for this initiative @Okabe-Junya. I was away. I'm back but still catching up. I'll get to this as soon as I can. In the meantime, let me cc a few extra people for feedback:
Thank you, I appreciate your support, chalin!
I have already informed katzchang, ymotongpoo about this PR. (I announced this PR on the #glossary-localization-japanese
channel in CNCF Slack, and they are there!)
Once we receive feedback from a-mccarthy, we can move forward! Thank you :)
Thank you for the clarifications @Okabe-Junya.
In addition to @a-mccarthy's feedback, I would appreciate if the following could formally approve this PR:
LGTM
LGTM
LGTM👍
Thank you for the wonderful review, @chalin. Your feedback is very thorough and helpful!
Based on your comments, I have made some revisions. I have also replied to some of your comments (to discuss)
Thanks!
ref. #153 Deploy preview: link
Feature Description
The Japanese Localization Guidelines include the following contents:
Background
https://github.com/cncf/techdocs/issues/153#issuecomment-2123992860