i18n (JP) - Draft of Japanese text for "Quick Start" Section

[J1-takai]

i18n (JP) Translation for "Quick Start" section

• What does this PR change? Give us a brief description.
  This is a trial translation work for "Tauri Doc 2.0 Japanese Version" from the scratch. If there are any similar activities already on-going, please disregard this pull request. If not, my drafts would need technical proof-reading as I have almost no knowledge on programming - my only programming experiences were introductory courses for FORTRAN and COBOL using punch cards data loading some 40 years ago, HA HA! No rush - Please take your time.
• Closes #

[netlify]

✅ Deploy Preview for tauri-v2 ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	cab5ade
🔍 Latest deploy log	https://app.netlify.com/sites/tauri-v2/deploys/67a8234dffebd20008511294
😎 Deploy Preview	https://deploy-preview-3111--tauri-v2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 90 (🔴 down 9 from production) Accessibility: 100 (no change from production) Best Practices: 100 (no change from production) SEO: 100 (🟢 up 8 from production) PWA: 80 (no change from production) View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[vasfvitor]

FYI you need to register the locale at https://github.com/tauri-apps/tauri-docs/blob/v2/locales.json and https://github.com/tauri-apps/tauri-docs/blob/v2/lunaria.config.json and it's possible to translate labels here https://github.com/tauri-apps/tauri-docs/blob/v2/astro.config.mjs

and you can track translations here https://v2.tauri.app/contribute/translate-status/ and I'm 99% sure there's no need to add rev on the files, as the tracker already does this, unless there's something else I'm missing

if you still need help with the technical stuff you can tag me

and if by any chance you know someone who could help to review your translation, they're welcome.

[J1-takai]

@vasfvitor
thank you for your suggestions on .json files above. I added "jp" locales and hopefully there are correctly done. For the third one on "label" translation, this will be a little bit complicated work and not all of the labels are translated/fixed, I'd like this to be left as is for the time being.
About the Rev Status table, I know this translation-status page, but since I do not know whom to ask about the similar data base for the jp translations, I decided to have a separate file just for my memorandum. Once the jp pages are issued, the same kind of the Rev management will be better idea.

Lastly, I reviewed Netlify error reports but I could not find the error locations (Tauri Doc site is highly automated and beyond my comprehension - the more I change the files, the more errors are coming...). If you have time, would you kindly help to correct the affected files so that they are merged into the main branch?

Thank you for your kind assistance in advance.

[vasfvitor]

hi @penginnu, @Kenzo-Wada, @takavfx we just enabled Japanese locale, does any of you still interested in helping out?. We could use some help on reviewing this PR (just the basics to ensure it's ok and nothing is off, no need to be picky) and continue with the translation effort on other pages.

[vasfvitor]

notes:

• use absolute links for internal navigation and prefix it with /jp
• internal anchors also needs to be updated, but only if the "heading" was translated/changed:

heading: Migrate to New Window Api
link anchor: #migrate-to-new-window-api

translated: 新しい Window API への移行
anchor: #新しい-window-api-への移行 (lower case)

if unsure about the anchor you can always go to the page, find the heading and click at it, then the anchor will be appended to the site url

live preview is posted above by the bot, but here it is anyway https://deploy-preview-3111--tauri-v2.netlify.app/jp/

[J1-takai]

@vasfvitor
Links/Anchor description: I will re-check my translation files once again before I submit the next PR for "Core Concepts" section.

BTW, I saw the preview of the JP pages which are very nicely created. Thank you again for your kind helps. I also noted that "Japanese" is already added to Tauri's top page language selector.

[J1-takai]

@vasfvitor
May I ask some questions?

• In "Check Formatting" section, there seems to be some actions ([request] increase depth for TOC in the right side of references pages #2444, ..., Fix Broken links #2416, Fix JS API Reference link are broken.  #2415 etc.) which are shown as "awaiting approval". Is there anything I can do about them?
• Or can I "close pull request" as the PR#3111 is approved?

[vasfvitor]

Is there anything I can do about them?

Usually a maintainer have to manually run workflows, I'll now.

Or can I "close pull request" as the PR#3111 is approved?

you mean this button?

simply speaking "close" is "delete" and "merge" is "integrate". It's possible to reopen once close. And only the team can merge.

The PR status is not 'approved', technically speaking. Is it ready for review? It would be good if you can bring someone native to review this.

Ah, I'm not sure if you noticed, but there's an option to mark this PR as a draft and then when everything is ready you can mark as "ready to review"

[vasfvitor]

@J1-takai I ran the "format" command and this is the changes it has done bb2d450 It shouldn't change the meaning of anything.

and I did a quick research and found out that it should be "ja" and not "jp" for the locale. I'll make the changes
https://news.ycombinator.com/item?id=5047300