i18n (JP) - Draft of Japanese text for "Quick Start" Section #3111
Conversation
✅ Deploy Preview for tauri-v2 ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
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. |
|
@vasfvitor 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. |
|
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. |
|
|
||
| Tauri 1.0 アプリを Tauri 2.0 に移行する場合に発生する可能性のある一般的な流れです。 | ||
|
|
||
| ### コア・モジュールの移行 |
There was a problem hiding this comment.
core is the name of package so you don't translate it, for example see how it was done in zh-cn https://tauri.app/zh-cn/start/migrate/from-tauri-1/#core-%E6%A8%A1%E5%9D%97%E8%BF%81%E7%A7%BB
There was a problem hiding this comment.
@vasfvitor
Thank you for your detailed checks over my translation files. Regarding the translation "Core", probably I regarded this "Core" in the header as a common noun because the word is not back-quoted like Core. [NOTE: Luckily (?) the translation of "Core" in this part is just a phonetic transcription ("コア" is pronounced as "Ko-Ah" = Core), and is ambiguous enough to mean either "core" package (proper noun) or common noun "core" = central portion.
Anyway, I will stick to the rule of "proper nouns such as module names, product names (Tauri, Linux, ...), etc. to be shown as in English texts". Is this OK?
There was a problem hiding this comment.
("コア" is pronounced as "Ko-Ah" = Core)
interesting
Anyway, I will stick to the rule of "proper nouns such as module names, product names (Tauri, Linux, ...), etc. to be shown as in English texts". Is this OK?
I'm not sure I got it 100%, but yeah, it's ok
|
notes:
heading: Migrate to New Window Api translated: 新しい Window API への移行 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/ |
|
@vasfvitor 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. |
i18n (JP) Translation for "Quick Start" section
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.