[ja] Add Japanese translation for getting started

[ymotongpoo]

• This PR is for a documentation page whose authoritative copy is in the opentelemetry.io repository.
• 🛑 (@chalin) Blocked on [i18n & ja] Improved fallback config and normalize en doc links #4627

Preview: https://deploy-preview-4616--opentelemetry.netlify.app/ja/docs/getting-started/

[ymotongpoo]

This PR needs to be merged after #4606

[chalin]

@ymotongpoo - hmm, there are issues with this PR, as can be surmised from the many labels that the labeling bot automatically added to this PR:

If you can, please to the following from your local environment:

• Ensure that youre main branch is at HEAD
• pull this PR (you might have to do a rebase on the pull)
• Rebase the branch of this PR from main
• Force push the branch of this PR

[chalin]

• I've submitted link-normalization updates to [i18n & ja] Improved fallback config and normalize en doc links #4627 that will make it easier to keep the same link paths in this PR. So until that PR is merged, this one will be blocked (FYI)
• See inline comment.

[ymotongpoo]

@chalin thank you for the comment. I force-pushed this branch. I hope it should fix the labels afterwards. (I don't have permission to change labels and GH Actions hasn't changed the labels yet.)

[svrnm]

@chalin thank you for the comment. I force-pushed this branch. I hope it should fix the labels afterwards. (I don't have permission to change labels and GH Actions hasn't changed the labels yet.)

I am not sure if the tooling is able to remove labels that have been set before, I manually removed them

[chalin]

@chalin thank you for the comment. I force-pushed this branch. I hope it should fix the labels afterwards. (I don't have permission to change labels and GH Actions hasn't changed the labels yet.)

Thanks. Did you rebase first?

There is still a problem with the PR in that we can't rebase from the web i/f:

Follow the instructions given earlier #4616 (comment):

If you can, please to the following from your local environment:

• Ensure that youre main branch is at HEAD
• pull this PR (you might have to do a rebase on the pull)
• Rebase the branch of this PR from main
• Force push the branch of this PR

The following PR has been merged and so this PR needs to be rebased because of that:

• [ja & zh] Normalize links & update some hashes #4634

[ymotongpoo]

@chalin Hmm, I rebased my fork first, rebased it with upstream/main, force-pushed then I added a couple more commits. I can't figure out why you are not able merge this PR. Let me try another force push.

[ymotongpoo]

@chalin I hope this push made it work.

[chalin]

For this page and the others too, ensure that you apply the changes made via:

• [i18n & ja] Improved fallback config and normalize en doc links #4627

Otherwise, the links given here refer to the en pages, which isn't what we want.

[ymotongpoo]

I see. I change them to point to ja pages.

[chalin]

I'd rather that you use relative paths as is done in the en page. That way we keep the ja and en versions "in sync".

[ymotongpoo]

My understanding is that #4627 was merged 2 days ago, so if I rebase onto main yesterday, the change was applied. Is it correct?

Anyway, I misunderstood your comment so I reverted the path change.

[chalin]

No worries @ymotongpoo. Merging of translation PRs is on hold. I'll get back to you as soon as I can.

[ymotongpoo]

I deleted the remote branch by mistake. Reopening.

[ymotongpoo]

@chalin @svrnm let me check the status. my understanding is that required steps to merge this and upcoming PRs are:

1. @katzchang gains the membership (REQUEST: New membership for @katzchang community#2146)
2. docs-ja-approvers team will be created after 1.
3. @katzchang (or any other approvers if others gain the membership) signs off the PR
4. @chalin or @svrnm merges the PR

Is this correct?

[svrnm]

@chalin @svrnm let me check the status. my understanding is that required steps to merge this and upcoming PRs are:

1. @katzchang gains the membership ([REQUEST: New membership for @katzchang community#2146](https://github.com/open-telemetry/community/issues/2146))

2. `docs-ja-approvers` team will be created after 1.

3. @katzchang (or any other approvers if others gain the membership) signs off the PR

4. @chalin or @svrnm merges the PR

Is this correct?

We are able to merge the PR without that being complete, we need to make this happen, but technically the PR is ready, however all translation PRs will be on hold / throttled back (not only new ones), as @chalin works on resolving core issues with the i18n-support features.

[chalin]

@ymotongpoo - ok, I see what is happening. You've specified that this PR is based on the English files from commit 93ab130. There have been updates to the pages in this PR since then.

Please use the following commit (or any more recent one) as your English-language file base:

• e7a6289

You can see the diff here:

• e7a6289#diff-2aa9d88e56f30c972fa5aeb63bcae20c8428572a6c6d2a229e57bafa72234628

[chalin]

Also note that the Localization page instructions and script have changed. For the updated pages, see:

• https://opentelemetry.io/docs/contributing/localization/#tracking-changes-to-english-pages

By the time that you are done updating this PR, when you run npm run check:i18n, there should be no ja pages listed. Ok?

[ymotongpoo]

Thank you @chalin for the confirmation. Because this is the PR for files under "Getting Started", I just updated the base revision of files under getting-started directory.

Thanks to your script, I'm aware that the following files need to be updated similarly, which will be fixed in the following PRs.

> check:i18n
> scripts/check-i18n.sh

Processing paths: content
1       1       content/en/_index.md - content/ja/_index.md
30      30      content/en/docs/concepts/components.md - content/zh/docs/concepts/components.md
4       5       content/en/docs/_index.md - content/zh/docs/_index.md
1       1       content/en/_index.md - content/zh/_index.md

[chalin]

Thanks to your script, I'm aware that the following files need to be updated similarly, which will be fixed in the following PRs.

Yes, that is ok. For this PR I wanted to ensure that the Getting started pages reflected the latest en versions, which they do now, thanks for synchronizing these pages.

[chalin]

Rebased PR that conforms to the new Translation tips. All checks are passing, so I'll merge this now.

[chalin]

👍🏻