i18n(ja): "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	8dda9e2
🔍 Latest deploy log	https://app.netlify.com/sites/tauri-v2/deploys/67bdd9c2ff319400083bb63f
😎 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: 100 (no change from production) Accessibility: 100 (no change from production) Best Practices: 100 (no change from production) SEO: 100 (no change 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]

@penginnu hi again, thanks for your help. You can start at this PR

just ignore those files listed here concept directory: 26fb977 as they are intended for another PR and are incomplete

those files are to be reviewed:
src/content/docs/ja/index.mdx
src/content/docs/ja/rss.mdx

General guidelines https://github.com/tauri-apps/tauri-docs/blob/4f3f5012e5a463653c8f61861de9ea7eba8727f5/.github/TRANSLATING.md

The main point is to avoid typos, sentences that are too far from the original meaning, unrelated/uneeded changes

[penginnu]

@vasfvitor Thank you!
I will proceed to review the following documents.

• src/content/docs/ja/index.mdx
• src/content/docs/ja/rss.mdx
• src/content/docs/ja/start/**/*

I have some knowledge of astrojs, tauri and nodejs, but I am not familiar with translations, so I may cause you some inconvenience ...

[penginnu]

This is a review for rss.mdx. And, an easily found tag error.
Looking forward to working with you!

[J1-takai]

@vasfvitor @penginnu

Thx for ur quick actions. Since I am a non-programmer (& retired old man), @penginnu-san's reviews on the technical aspect of my translations are highly appreciated.

Regarding a feature branch idea, this may be a good idea to proceed the large document site like Tauri. I will check how to do it.
I use the VSCode for my translation (.md editing only) but only limited functions are used as a beginner 🔰. This is probably why the format errors occurs on my translated files. I shall improve someday.

[vasfvitor]

@J1-takai have you managed to copy the "concept" page drafts to a new branch?

[vasfvitor]

This is probably why the format errors occurs on my translated files. I shall improve someday.

Format errors will happen regardless, it's just a way to ensure we have a default formatting, so we can track only real changes, not formatting. If you can manage to, run pnpm format, it will format based on our set of rules

[J1-takai]

@vasfvitor Yes, I copied the concept files into the separate folder. Also I am now working using the new branch "Concept-ja". As for running pnpm format, I cannot find the way how to do it. Note: Node v23.7.0 and pnpm v10.3.0 were successfully installed in my Linux PC. How can I use pnpm in VS Code?

[vasfvitor]

basically you open a terminal at the cloned repository and run pnpm i once to install the packages. Afterwards pnpm format will be available. It can be your system terminal or vscode's integrated. To preview locally you need to run pnpm dev:setup once, then pnpm dev to start the local server

[J1-takai]

@vasfvitor
Thank you for your advice on "pnpm format". I tried this but there seems to be no PATH to Node.js from VS Code (I received "No pnpm command is found" message. I'll check the solution somehow.

[vasfvitor]

you should be able to open any terminal and enter pnpm -v, and node -v. If any of those doesn't work, then you gotta review their installation, usually making sure they're on PATH. You don't need to specifically use vscode integrated terminal. You can open any terminal and cd cloned-tauri-docs-repo

[J1-takai]

@vasfvitor Thank you for your many advice, but the problem still exists - this time I tried the node/pnpm in the local directory of Tauri-Docs, but the error message "pnpm CLI is missing" occurred - in the local directory Node -v works but pnpm -v failed. I decided to put this issue aside for the time being and proceed the translation work. Thank you again for your help.

[J1-takai]

@vasfvitor @penginnu
I updated the JA Translation Tracker files as attached. Looks like lots of fun(?) ahead!!
Tauri i18n(ja) Translation Status List 2025-02-15.xlsx

[vasfvitor]

it's ok, last note is that generally you'd have to run corepack enable pnpm to enable it. I assume you may have installed npm that comes with node, and not pnpm that you have to enable

[J1-takai]

@vasfvitor
Thank you for your "last" note. After fiddling "corepack", re-installation of "nvm" & "node.js", changing pnpm version to "9.x.x" etc several times, suddenly the pnpm format [seemed to have] worked (I think) in the local directory: see screenshot below.

Most of the files are shown "unchanged" (of course), but my changed files in CONCEPT folder seems to be prettified (I do not know what or where is changed though). In any case, this must be a good omen for i18n(ja). Thank you for your patience. Now it's time to get back to work!!

[J1-takai]

@vasfvitor thank you very much for your great support on this. I'll continue my effort on the remaining sections one by one.