Repository navigation
i18n(ja): add Japanese translations 2026-05-11 - #5391
leaanthony wants to merge 1 commit into
Conversation
WalkthroughAdds extensive Japanese documentation across concepts, contributing, features, community pages, windows, and updates the Japanese translation cache. No source code changes. ChangesJapanese Documentation Localization Suite
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested labels
Poem
✨ Finishing Touches🧪 Generate unit tests (beta)
⚔️ Resolve merge conflicts
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 10
Note
Due to the large number of review comments, Critical severity comments were prioritized as inline comments.
🟠 Major comments (47)
docs/src/content/docs/ja/features/bindings/methods.mdx-18-24 (1)
18-24:⚠️ Potential issue | 🟠 Major | ⚡ Quick winこのページもコードブロック内は英語原文維持が必要です。
例コード内コメントの日本語化は、翻訳方針と不整合です。英語版コードブロックと一致させてください。
Based on learnings: For Wails documentation i18n/translation PRs, do not translate any text inside code blocks in MDX files.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/features/bindings/methods.mdx` around lines 18 - 24, The code block contains translated text and must remain identical to the English source; revert any translations inside the example so the Go snippet uses the original English content (ensure the type and method names GreetService and Greet and the returned string "Hello, " + name + "!" are exactly as in the English version), and verify no inline comments or strings inside that code block are localized.docs/src/content/docs/ja/contributing.mdx-45-53 (1)
45-53:⚠️ Potential issue | 🟠 Major | ⚡ Quick winコードブロック内テキストの翻訳が入っています。
このページの fenced code block 内（例: bash コメント、サンプル内文言）は英語原文維持が必要です。該当ブロックを英語版と一致させてください。
Based on learnings: For Wails documentation i18n/translation PRs, do not translate any text inside code blocks in MDX files.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/contributing.mdx` around lines 45 - 53, The fenced bash code block containing translated Japanese comments and possibly translated sample text must be reverted to the original English from upstream; locate the fenced code block with the bash comments and Git commands (the snippet showing "git clone https://github.com/YOUR_USERNAME/wails.git", "cd wails", and "git remote add upstream https://github.com/wailsapp/wails.git") and replace any translated comments/text inside that code block with the English original so it exactly matches the upstream English version; ensure no other code blocks in the MDX are translated similarly.docs/src/content/docs/ja/features/bindings/best-practices.mdx-18-41 (1)
18-41:⚠️ Potential issue | 🟠 Major | ⚡ Quick winコードブロック内容は翻訳せず、原文英語を維持してください。
このファイルの fenced code block 内コメントが日本語化されています。翻訳PRルール上、コードブロックは英語原文と一致させる必要があります。
Based on learnings: For Wails documentation i18n/translation PRs, do not translate any text inside code blocks in MDX files.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/features/bindings/best-practices.mdx` around lines 18 - 41, The fenced Go code block contains translated Japanese comments and identifiers that must match the original English; revert the code block contents to the original English version by restoring the comments and example names (e.g., replace Japanese comments and the "悪い例/良い例" text with the original English phrases and ensure types/methods like AppService, SaveFile, GetUser, SendEmail, ProcessPayment and the good examples FileService.Save, UserService.GetByID, EmailService.Send, PaymentService.Process are exactly as in the source English doc); update only the inner text of the fenced code block so the rest of the MDX remains unchanged.docs/src/content/docs/ja/features/bindings/methods.mdx-408-410 (1)
408-410:⚠️ Potential issue | 🟠 Major | ⚡ Quick winコードフェンス終端が崩れています（
```---）。コードブロック終端と区切り線が同一行で連結されており、レンダリングが不安定になります。
```と---を別行に分離してください。🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/features/bindings/methods.mdx` around lines 408 - 410, The code fence terminator and horizontal rule are merged as "```---"; split them so the code block ends on its own line with only ``` and place the --- horizontal rule on the next line (i.e., replace the single "```---" token with two separate lines: a line containing only "```" followed by a line containing only "---") to restore correct Markdown rendering in methods.mdx.docs/src/content/docs/ja/contributing/codebase-layout.mdx-13-22 (1)
13-22:⚠️ Potential issue | 🟠 Major | ⚡ Quick winコードブロック内の文言を英語原文に戻してください。
このファイルの fenced code block（例: ディレクトリツリー内コメント）が日本語化されています。i18n PR ではコードブロック内容は原文維持が必要です。
Based on learnings: For Wails documentation i18n/translation PRs, do not translate any text inside code blocks in MDX files.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/contributing/codebase-layout.mdx` around lines 13 - 22, The fenced code block showing the wails/ directory tree contains Japanese inline comments and must be reverted to the original English phrasing; locate the code block that lists the entries (the block starting with "wails/" and the tree entries like "v3/", "v2/", "docs/", etc.) and replace the Japanese comments (e.g., the arrowed comment after v3 and other Japanese descriptions) with the original English text used in the source (restore the original English directory comments for v3, v2, docs, website, scripts, mkdocs-website and the trailing meta files line) so that no text inside the fenced code block is translated.docs/src/content/docs/ja/features/bindings/methods.mdx-102-125 (1)
102-125:⚠️ Potential issue | 🟠 Major | ⚡ Quick winChange
sync.Mutextosync.RWMutexto match theRLock/RUnlockmethod calls.Line 104 declares
mu sync.Mutex, but lines 122–123 callRLock()andRUnlock(), which do not exist onsync.Mutex. Onlysync.RWMutexprovides read lock methods.Fix
type CounterService struct { count int - mu sync.Mutex + mu sync.RWMutex }🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/features/bindings/methods.mdx` around lines 102 - 125, The mu field on CounterService is declared as sync.Mutex but GetCount uses RLock/RUnlock which only exist on sync.RWMutex; change the declaration of mu in CounterService to use sync.RWMutex so Increment and Decrement can still call Lock/Unlock and GetCount can call RLock/RUnlock (update the mu type in the struct definition referenced by CounterService and keep the existing method calls in Increment, Decrement, and GetCount).docs/src/content/docs/ja/contributing/getting-started.mdx-81-82 (1)
81-82:⚠️ Potential issue | 🟠 Major | ⚡ Quick winコードブロック内テキストが翻訳されています
このPR方針では、コードブロック内（コメント含む）は原文英語のまま維持が必要です。該当箇所を英語に戻してください。
Based on learnings: “For Wails documentation i18n/translation PRs, do not translate any text inside code blocks in MDX files.”
Also applies to: 173-174, 192-197, 297-300
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/contributing/getting-started.mdx` around lines 81 - 82, The code blocks in the MDX (e.g., the block under the header "バグを再現して理解を深める") have been translated into Japanese but must remain in the original English; locate the fenced code blocks at the reported ranges (including the one under that header and the other ranges: 173-174, 192-197, 297-300) and revert their contents back to the original English text (including any comment lines inside those blocks), leaving non-code prose translated as-is.docs/src/content/docs/ja/contributing/runtime-internals.mdx-195-199 (1)
195-199:⚠️ Potential issue | 🟠 Major | ⚡ Quick winコードブロック内コメントが翻訳されています
Cコード内コメント（
外部ファイルドラッグ/内部 HTML5 ドラッグ）は原文英語に戻してください。コードブロック内は翻訳対象外です。Based on learnings: “For Wails documentation i18n/translation PRs, do not translate any text inside code blocks in MDX files.”
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/contributing/runtime-internals.mdx` around lines 195 - 199, The comments inside the C code block have been translated to Japanese; revert them to the original English text (e.g., change the Japanese comments following the return TRUE; and return FALSE; lines back to their original English phrases such as "external file drag" and "internal HTML5 drag") so that code blocks remain untranslated; locate the comments around the return TRUE/FALSE statements (and the surrounding g_free(name); line) and restore the original English comments.docs/src/content/docs/ja/community/templates.md-24-30 (1)
24-30:⚠️ Potential issue | 🟠 Major | ⚡ Quick winWails v3 の CLI プレフィックスが誤っています
このページのコマンドは
wails initではなくwails3 initに統一する必要があります（例示コマンドも同様）。Based on learnings: “When reviewing Wails documentation (including translated MDX pages), Wails v3 CLI commands must use the
wails3prefix.”🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/community/templates.md` around lines 24 - 30, Update the CLI prefix from `wails` to `wails3` throughout the text and examples: replace occurrences of the command string `wails init -n "Your Project Name" -t [以下のリンク[`@version`]]` and the example `wails init -n "Your Project Name" -t https://github.com/misitebao/wails-template-vue` with `wails3 init ...`, keeping the rest of the sentence about defaulting to the main branch and version-tag behavior unchanged.docs/src/content/docs/ja/contributing/asset-server.mdx-109-113 (1)
109-113:⚠️ Potential issue | 🟠 Major | ⚡ Quick winコードブロック内コメントが翻訳されています
URL() string // 開発: ...のようなコードコメントは翻訳せず英語原文を維持してください。Based on learnings: “For Wails documentation i18n/translation PRs, do not translate any text inside code blocks in MDX files.”
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/contributing/asset-server.mdx` around lines 109 - 113, The code block for the AssetServer interface has inline comments translated to Japanese; revert those comments to the original English text so comments inside code blocks remain in English. Update the comments for the methods URL(), Open(), and Close() in the AssetServer interface back to the original English phrases (e.g., "development: http://localhost:34115, production: wails://app", "start listening", "graceful shutdown") so the code block contains only English inline comments.docs/src/content/docs/ja/features/bindings/enums.mdx-395-395 (1)
395-395:⚠️ Potential issue | 🟠 Major | ⚡ Quick win表の構文が壊れています
|complex64,complex128| いいえ |---は行末の|---が混入しており、Markdown テーブルが崩れます。| いいえ |で終了させてください。🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/features/bindings/enums.mdx` at line 395, The Markdown table row containing the enum types `complex64`, `complex128` is malformed because it ends with an extra `|---`; update the row so it ends with `| いいえ |` (remove the trailing `|---`) to restore proper table syntax for the row that lists `complex64`, `complex128`.docs/src/content/docs/ja/concepts/build-system.mdx-242-268 (1)
242-268:⚠️ Potential issue | 🟠 Major | 🏗️ Heavy liftコードブロック内の文言は原文英語のまま維持してください
Taskfile/Vite 設定コード内の日本語コメント・説明文は、翻訳方針に反します。英語原文へ戻してください。
Based on learnings: “For Wails documentation i18n/translation PRs, do not translate any text inside code blocks in MDX files.”
Also applies to: 366-385
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/concepts/build-system.mdx` around lines 242 - 268, Revert the Japanese text inside the YAML code block so all in-code comments and descriptions are the original English (leave keys like tasks: build, build:windows, build:macos, build:linux and their cmds unchanged); replace the Japanese desc values and any in-block comments with the English originals and ensure the same fix is applied to the other similar code block later in the file (the block containing the same task names around the other section).docs/src/content/docs/ja/concepts/build-system.mdx-213-215 (1)
213-215:⚠️ Potential issue | 🟠 Major | ⚡ Quick win説明と CLI オプションが一致していません
「フロントエンドビルドをスキップ」と書かれていますが、
-skipbindingsはバインディング生成スキップの意味です。説明かコマンドのどちらかが誤っています。🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/concepts/build-system.mdx` around lines 213 - 215, The heading "フロントエンドビルドをスキップ（既存のものを使用）" and the command `wails3 build -skipbindings` disagree: `-skipbindings` skips binding generation, not the frontend build. Fix by making the two consistent—either change the heading to mention skipping binding generation (e.g., replace the heading text with "バインディング生成をスキップ") to match `-skipbindings`, or replace the command with the correct flag for skipping the frontend build (instead of `-skipbindings`) so it matches the current heading; update the text around these symbols accordingly.docs/src/content/docs/ja/features/bindings/models.mdx-454-456 (1)
454-456:⚠️ Potential issue | 🟠 Major | 🏗️ Heavy lift末尾セクションが壊れており、内容欠落の可能性があります。
## 高度なパターン---は見出しとして不正で、直後にファイルが終わっているため、区切りや後続内容が欠落しているように見えます。原文と照合して末尾セクションを復元してください。🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/features/bindings/models.mdx` around lines 454 - 456, The trailing section currently ends with a malformed heading string "## 高度なパターン---" and appears truncated; restore the missing end-of-file content by replacing that malformed heading with the correct heading and the original subsequent paragraphs from the source (compare with the original English file), ensuring the "Advanced patterns" section (or equivalent) is fully restored and that links and examples listed under it match the original content; look for the heading token "## 高度なパターン" (or the original "## Advanced patterns") in the upstream/English doc to copy the complete section into this Japanese file.docs/src/content/docs/ja/contributing/template-system.mdx-22-143 (1)
22-143:⚠️ Potential issue | 🟠 Major | 🏗️ Heavy liftテンプレート例のコードブロックは英語原文を維持してください。
このファイルでも code block 内テキストが翻訳されています。i18n ドキュメントの運用ルールに反するため、原文への差し戻しが必要です。
Based on learnings: For Wails documentation i18n/translation PRs, do not translate any text inside code blocks in MDX files.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/contributing/template-system.mdx` around lines 22 - 143, The JP translation erroneously translated text inside code blocks in docs/src/content/docs/ja/contributing/template-system.mdx; revert every code block content back to the original English source (e.g., the directory tree block beginning with "v3/", the command chains showing cmd/wails3/init.go → internal/commands/init.go → internal/templates.Load() → Template.CopyTo(dest), the placeholder table examples, the code sample for func (t *Template) Validate() error, and all inline shell/code examples) so that code blocks remain exactly as in the English source while keeping surrounding prose translated; search for triple-backtick sections and replace their inner text with the upstream English text.docs/src/content/docs/ja/contributing/standards.mdx-16-456 (1)
16-456:⚠️ Potential issue | 🟠 Major | 🏗️ Heavy liftこのファイルのコードブロックも翻訳せず原文維持が必要です。
サンプルコード内のコメント/テキストがローカライズされています。Wails i18n では code block の内容は英語原文を保つ運用です。
Based on learnings: For Wails documentation i18n/translation PRs, do not translate any text inside code blocks in MDX files.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/contributing/standards.mdx` around lines 16 - 456, The review notes that code block contents were localized and must remain in English; revert any translated text inside fenced code blocks (e.g., the bash snippet at the top, Go examples like type Closer, NewApplication, validate, Window tests, interface examples, and TS/Prettier JSON) back to the original English examples and ensure all fenced code blocks in the MDX are preserved verbatim (no localized comments or strings); search for the fenced blocks and restore their original English content so that code block literals are unchanged by translation.docs/src/content/docs/ja/contributing/extending-wails.mdx-34-238 (1)
34-238:⚠️ Potential issue | 🟠 Major | 🏗️ Heavy lift拡張ガイド内のコードブロックも英語原文に揃えてください。
このファイルでも code block 内が翻訳されており、i18n 運用ルールと不整合です。
Based on learnings: For Wails documentation i18n/translation PRs, do not translate any text inside code blocks in MDX files.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/contributing/extending-wails.mdx` around lines 34 - 238, Revert any translated text inside all code blocks back to the English originals so code examples are not localized: ensure the Go service example (package chat, type Service, func New, func (s *Service) Send), lifecycle stubs (func (s *Service) Init, Shutdown), generator registration (services.Register("chat", chat.New)), CLI example (init(), Add(), &cobra.Command with Use: "hello", RunE), runtime API example (func (w *WebviewWindow) SetOpacity), message processor constants/handlers (const MsgSetOpacity, handleSetOpacity), capability constant (const CapOpacity) and all other fenced code blocks match upstream English source; do not change prose outside code blocks.docs/src/content/docs/ja/faq.mdx-57-219 (1)
57-219:⚠️ Potential issue | 🟠 Major | 🏗️ Heavy liftFAQ 内のコードブロックは翻訳せず、英語原文を保持してください。
このファイルでも code block 内のコメント/文字列がローカライズされています。i18n ルール上、コードブロック内容は原文固定が必要です。
Based on learnings: For Wails documentation i18n/translation PRs, do not translate any text inside code blocks in MDX files.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/faq.mdx` around lines 57 - 219, The code blocks in this MDX were translated into Japanese but must remain in the original English; revert any localized text inside fenced code blocks back to the upstream English examples (e.g., the Go Greet function and its JavaScript usage: symbols Greet, func (s *Service) Greet, import { Greet }..., CLI examples like wails3 build/wails3 dev, API examples like app.Window.New(), window.Show(), app.SystemTray.New(), app.Dialog.OpenFile(), app.Event.Emit and OnEvent) so the code snippets and inline code/strings/comments exactly match the English source; do not change surrounding prose—only restore the content inside backtick-fenced blocks to the original English.docs/src/content/docs/ja/features/bindings/advanced.mdx-18-338 (1)
18-338:⚠️ Potential issue | 🟠 Major | 🏗️ Heavy liftコードブロックの内容を英語原文と一致させてください。
このページでは、複数の fenced code block 内でコメントやテキストがローカライズされています。Wails の i18n 方針では、コードブロック内は翻訳せず原文維持が必要です。ここがずれると、サンプルのコピペ再現性と他ロケール間の差分追跡が崩れます。
Based on learnings: For Wails documentation i18n/translation PRs, do not translate any text inside code blocks in MDX files.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/features/bindings/advanced.mdx` around lines 18 - 338, The code blocks in this MDX have been translated into Japanese but must remain in the original English; restore all fenced code blocks to match the English source exactly (e.g., the Go examples with the "//wails:inject" directives and MyService/Greet, the Result<T> TypeScript class, Person/Address examples, the auth and data service examples including functions like AuthService.Login, DataService.Process, and directives like //wails:internal and //wails:include), ensuring no comments or in-code text are localized so the examples are identical to the upstream English originals.docs/src/content/docs/ja/contributing/build-packaging.mdx-23-177 (1)
23-177:⚠️ Potential issue | 🟠 Major | 🏗️ Heavy liftビルド＆パッケージング例のコードブロックを原文（英語）に戻してください。
このページの fenced code block でも翻訳が入っており、i18n 方針に反します。コマンド/コードは英語原文固定で揃える必要があります。
Based on learnings: For Wails documentation i18n/translation PRs, do not translate any text inside code blocks in MDX files.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/contributing/build-packaging.mdx` around lines 23 - 177, The fenced code blocks in this MDX (the shell/terminal examples and tables containing command names like "wails3 build", Taskfile targets (`frontend:build`, `embed:assets`, `build:go`, `package:*`), filenames (`manifest.json`, `frontend/dist/`, `bundled_assetserver.go`, `tool_buildinfo.go`, `tool_package.go`) and inline flags (`-tags production`, `-ldflags "-s -w"`, `-X internal/buildinfo.BuildTime=$(date)`, `wails3 build -package deb`, etc.) must be restored to the original English text; locate the triple-backtick fenced code blocks and any inline code spans in this file (search for examples showing "wails3 build", the tables of Taskfile targets, and the flag examples) and replace the Japanese-translated command/flag/code text with the original English command lines, filenames, and flags so all code blocks remain untranslated per i18n policy.docs/src/content/docs/ja/features/bindings/models.mdx-18-452 (1)
18-452:⚠️ Potential issue | 🟠 Major | 🏗️ Heavy liftこのページのコードブロックも原文（英語）へ戻してください。
複数の fenced code block 内テキストが翻訳されており、Wails i18n のコードブロック不翻訳ルールに反しています。
Based on learnings: For Wails documentation i18n/translation PRs, do not translate any text inside code blocks in MDX files.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/features/bindings/models.mdx` around lines 18 - 452, The code blocks in models.mdx were translated to Japanese but must remain in English per Wails i18n rules; locate every fenced code block (search for markers like "type Person struct", "type User struct", "type Address struct", "type Team struct", "type Config struct", and generated JS/TS classes such as "export class User", "export class Person", "constructor(source = {})", and functions like "GetUser", "CreateUser", "UpdateUser") and restore the original English text inside those fences (both Go and generated JavaScript/TypeScript examples), leaving surrounding MDX prose translated as-is.docs/src/content/docs/ja/features/bindings/advanced.mdx-331-338 (1)
331-338:⚠️ Potential issue | 🟠 Major | ⚡ Quick winFix malformed code block ending on line 338
The last line contains extraneous backticks and a duplicate
//wails:injectdirective that breaks the code block formatting://wails:inject await InternalMethod("Hello " + arg + "!");`//wails:inject`Should be:
//wails:inject await InternalMethod("Hello " + arg + "!");This malformed syntax prevents proper MDX rendering and makes the code snippet incomplete.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/features/bindings/advanced.mdx` around lines 331 - 338, The final injected line for the example CustomMethod/InternalMethod snippet is malformed: remove the stray backtick and the duplicate "//wails:inject" suffix so the line ends as a normal statement; locate the injected block lines starting with "//wails:inject j*:" and specifically fix the line containing await InternalMethod("Hello " + arg + "!"); by deleting the trailing `//wails:inject` and backtick so the MDX code block closes correctly.docs/src/content/docs/ja/contributing/extending-wails.mdx-64-65 (1)
64-65:⚠️ Potential issue | 🟠 MajorChange
wails3 generatetowails3 generate bindings.The CLI requires an explicit subcommand. The command
wails3 generatewithoutbindingswill not work—users must runwails3 generate bindingsto generate the bindings. This is verified in the source code (v3/cmd/wails3/main.go) wherebindingsis registered as a required subcommand under thegenerateparent command. The correct form is already documented indocs/src/content/docs/guides/cli.mdxand other tutorials but is inconsistent here.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/contributing/extending-wails.mdx` around lines 64 - 65, Update the CLI example to use the required subcommand: replace the invocation `wails3 generate` with `wails3 generate bindings` so the documented command matches the registered subcommand (see generate -> bindings in v3/cmd/wails3/main.go) and ensures `window.backend.chat.Send("hi")` bindings are actually generated.docs/src/content/docs/ja/getting-started/your-first-app.mdx-191-199 (1)
191-199:⚠️ Potential issue | 🟠 Major | ⚡ Quick winコードブロック内コメントが翻訳されています
Line 192-199 のシェルコード内コメントが日本語化されています。翻訳PRでは fenced code の内容は英語原文のまま維持する必要があります。
Based on learnings: Do not translate any text inside MDX code blocks; keep code block contents exactly as in English source.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/getting-started/your-first-app.mdx` around lines 191 - 199, The fenced bash code block (starting with ```bash and containing commands like "wails3 package" and "wails3 task linux:create:appimage", "wails3 task linux:create:deb", "wails3 task linux:create:rpm", "wails3 task linux:create:aur") was translated into Japanese; revert the comments inside that code block back to the original English text so the code block content exactly matches the English source (do not alter the commands themselves, only restore the inline comments to their original English wording).docs/src/content/docs/ja/feedback.mdx-19-19 (1)
19-19:⚠️ Potential issue | 🟠 Major | ⚡ Quick win
wails doctorは v3 ドキュメントでは誤コマンドですLine 19 は
wails3 doctorに修正してください。現状のままだと利用者が誤コマンドを実行します（翻訳側だけでなく、必要なら英語ソース側にも同修正を反映してください）。Based on learnings: Wails v3 CLI commands must use the
wails3prefix (e.g.,wails3 doctor).🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/feedback.mdx` at line 19, Update the incorrect CLI command string "wails doctor" to the v3-correct "wails3 doctor" in the document (replace the literal text `wails doctor` with `wails3 doctor`), and if the same incorrect string exists in the English source update that as well so both translations use the `wails3` prefix consistently.docs/src/content/docs/ja/contributing/testing-ci.mdx-26-31 (1)
26-31:⚠️ Potential issue | 🟠 Major | ⚡ Quick winコードフェンス内（ディレクトリツリー注釈）が翻訳されています
Line 26-31 のような fenced block 内注釈は、翻訳対象ではなく原文維持が必要です。英語ソースと一致させてください。
Based on learnings: Do not translate any text inside fenced code blocks in i18n MDX files.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/contributing/testing-ci.mdx` around lines 26 - 31, The fenced code block containing the directory tree (e.g., lines with "├── internal/.../_test.go", "├── pkg/.../_test.go", etc.) was translated but must remain verbatim in English; revert the translated text inside that fenced block back to the original English lines and ensure the MDX i18n pipeline does not translate text inside fenced code blocks (preserve any fenced-block content exactly as in the English source).docs/src/content/docs/ja/features/notifications/overview.mdx-60-65 (1)
60-65:⚠️ Potential issue | 🟠 Major | ⚡ Quick winコードブロック内の文字列/コメントが翻訳されています
Line 60-65 を含む複数の fenced code が翻訳されています。翻訳PRではコードブロック内容を英語原文と一致させてください。
Based on learnings: Code block contents in locale MDX files must remain exactly in original English.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/features/notifications/overview.mdx` around lines 60 - 65, The code block in the MDX was translated into Japanese; restore the block to the original English text so code examples match the source. Locate the notifier.SendNotification call and the notifications.NotificationOptions literal (fields ID, Title, Subtitle, Body) and replace the translated strings/comments (e.g., "新しいカレンダー招待", "差出人: Jane Doe", "タップしてイベントを表示") with the original English phrases used in the upstream docs.docs/src/content/docs/ja/contributing/binding-system.mdx-36-38 (1)
36-38:⚠️ Potential issue | 🟠 Major | ⚡ Quick winコードフェンス内コメントが原文から変更されています
Line 36-38 のコードブロック内コメント（
// ...）が翻訳されています。翻訳ドキュメントではコードブロック内容を英語原文と一致させてください。Based on learnings: In Wails i18n docs, text inside fenced code blocks must remain exactly in original English.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/contributing/binding-system.mdx` around lines 36 - 38, The code block under the wails3 generate example has its inline comments translated to Japanese; restore the comments to the original English text so the fenced code exactly matches the English source (e.g., leave the command and function identifiers as-is and change the comments next to generator.Collect(), generator.Analyse(), generator.Render() back to their original English phrases), ensuring only the comment text is reverted and no symbols or formatting around wails3 generate / generator.Collect() / generator.Analyse() / generator.Render() are altered.docs/src/content/docs/ja/features/bindings/services.mdx-156-167 (1)
156-167:⚠️ Potential issue | 🟠 Major | ⚡ Quick winコードブロック内のコメントが翻訳されています
この範囲の Go コードコメント（例:
// リソースの初期化）は、翻訳PRの運用ルールに反します。fenced code は英語原文のままに戻してください。Based on learnings: Do not translate text inside fenced code blocks in locale MDX files.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/features/bindings/services.mdx` around lines 156 - 167, The comments inside the fenced Go code block were translated to Japanese; revert them to the original English comments so fenced code remains unchanged in locale MDX files—replace the translated lines (e.g. "// リソースの初期化", "// マイグレーションの実行", "// バックグラウンドタスクの開始") with their original English equivalents above the calls to u.db.Ping(), u.runMigrations(), and go u.backgroundSync(ctx) respectively, ensuring only comment text is changed and no code logic (function names u.db.Ping, u.runMigrations, u.backgroundSync) is modified.docs/src/content/docs/ja/contributing/setup.mdx-16-18 (1)
16-18:⚠️ Potential issue | 🟠 Major | ⚡ Quick winコードブロック内容が翻訳されています（原文維持ルール違反）
Line 16-18 を含む複数の fenced code でコメント文が日本語化されています。コードブロックは英語原文のまま保持してください。
Based on learnings: In Wails translation docs, code block contents (including shell comments) must remain exactly as original English.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/contributing/setup.mdx` around lines 16 - 18, Revert translated text inside the fenced code blocks back to the original English content: locate the code blocks containing strings like "https://go.dev/dl/ からダウンロード" and "go version # インストールを確認" and replace those comment/inline-text portions with the original English phrases (preserve the code exactly as in the upstream source, including shell comments) so that code blocks remain identical to the English original; ensure no other prose is changed.docs/src/content/docs/ja/features/bindings/services.mdx-613-613 (1)
613-613:⚠️ Potential issue | 🟠 Major | ⚡ Quick winリスト項目に区切り線が連結しておりMarkdownが壊れています
Line 613 の
...サービスは共有される---は---を独立行に分離してください。現状はリスト終端と水平線の構文が壊れます。🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/features/bindings/services.mdx` at line 613, 行内で末尾に続く水平線マーカーがリスト記法とつながってMarkdownが壊れているので、該当の行 "**スレッドセーフを忘れない** - サービスは共有される---" の末尾から "---" を切り離して独立した行に移動してください（つまりその行は "**スレッドセーフを忘れない** - サービスは共有される" にし、次の行に単独で "---" を置いてください）; これによりリスト終端と水平線が正しくレンダリングされます.docs/src/content/docs/ja/getting-started/your-first-app.mdx-232-243 (1)
232-243:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdmonition 構文が前文に連結されておりMDXとして不正です
Line 232 で
...しやすくなります。:::tip[Pro Tip]が同一行連結になっています。:::tipは改行して開始しないと崩れます。最小修正例
-これにより、Go モジュール名が Go のモジュール命名規則と一致し、コードを共有しやすくなります。:::tip[Pro Tip] +これにより、Go モジュール名が Go のモジュール命名規則と一致し、コードを共有しやすくなります。 + +:::tip[Pro Tip]🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/getting-started/your-first-app.mdx` around lines 232 - 243, The admonition opener `:::tip[Pro Tip]` is on the same line as the previous sentence (`...しやすくなります。`), which breaks MDX; fix by inserting a newline so the prior sentence ends on its own line and `:::tip[Pro Tip]` starts on the next line, and ensure the admonition body and the closing `:::` are each on their own lines (i.e., move `:::`, the fenced content, and the closing `:::` to separate lines) so the admonition is parsed correctly.docs/src/content/docs/ja/features/notifications/overview.mdx-234-243 (1)
234-243:⚠️ Potential issue | 🟠 Major | ⚡ Quick win通知カテゴリAPIのMarkdownテーブルが破損しています
Line 237 で行内容と区切り線が結合されており、以降の行が正しく表として解釈されません。テーブル区切りを分離してください。
最小修正イメージ
| `RegisterNotificationCategory(category NotificationCategory)` | 再利用可能な通知カテゴリを登録する | | `RemoveNotificationCategory(categoryID string)` | 以前に登録されたカテゴリを削除する | -|---------------------------------------------------|--------------------------------------------------------------| +| `RemoveAllPendingNotifications()` | 保留中のすべての通知を削除します（macOS および Linux のみ） | +| `RemovePendingNotification(identifier string)` | 特定の保留中の通知を削除します（macOS および Linux のみ） | +| `RemoveAllDeliveredNotifications()` | 配信済みのすべての通知を削除します（macOS および Linux のみ）| +| `RemoveDeliveredNotification(identifier string)` | 特定の配信済み通知を削除します（macOS および Linux のみ） | +| `RemoveNotification(identifier string)` | 通知を削除します（Linux 固有） |🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/features/notifications/overview.mdx` around lines 234 - 243, The Markdown table is broken because the separator row got merged into the `RemoveNotificationCategory(categoryID string)` row; split the combined line into a proper separator row so the header and body are separated, e.g. ensure there is a standalone separator line like "|---|---|" between the header and rows and that each method row (e.g. `RegisterNotificationCategory`, `RemoveNotificationCategory`, `RemoveAllPendingNotifications`, `RemovePendingNotification`, `RemoveAllDeliveredNotifications`, `RemoveDeliveredNotification`, `RemoveNotification`) is its own line with leading and trailing pipes so the table parses correctly.docs/src/content/docs/ja/features/events/system.mdx-361-362 (1)
361-362:⚠️ Potential issue | 🟠 Major | ⚡ Quick winFix the broken code-fence opening in the Pub/Sub section
Line 361 merges a prose label with a fence marker (
// サブスクライバー```go), which breaks markdown parsing. Put the prose line and fenced block on separate lines.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/features/events/system.mdx` around lines 361 - 362, The opening fenced code block is merged with prose ("// サブスクライバー```go") which breaks Markdown; edit the document so the prose comment and the Go fence are on separate lines: replace the single merged line with a standalone prose line (e.g., "// サブスクライバー") followed by a new line with the fence marker "```go", then keep the existing code starting with "app.Event.On("order-created", func(e *application.CustomEvent) {" inside that fenced block.docs/src/content/docs/ja/features/screens/info.mdx-407-409 (1)
407-409:⚠️ Potential issue | 🟠 Major | ⚡ Quick winSeparate FAQ text and footer separator into valid markdown blocks
Line 407 ends with
---, merging constructs and risking malformed rendering. Split the paragraph, separator, and CTA into separate markdown blocks.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/features/screens/info.mdx` around lines 407 - 409, The paragraph currently ends with a trailing '---' which merges the paragraph and the footer separator into a single malformed markdown block; edit the text around the trailing '---' so that the explanatory sentence about periodic polling is its own paragraph, the horizontal rule '---' is on its own line as a standalone markdown separator, and the CTA lines ("**ご質問がありますか？** [Discord]... [screen の例]...") are in a separate paragraph below the separator; ensure there are blank lines separating the paragraph, the '---' line, and the CTA so each renders as a distinct markdown block.docs/src/content/docs/ja/features/clipboard/basics.mdx-407-409 (1)
407-409:⚠️ Potential issue | 🟠 Major | ⚡ Quick winSeparate the bullet text from the horizontal-rule/footer transition
Line 407 ends with
---, which merges markdown constructs and can break rendering. Move the separator/footer to its own line block after the list.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/features/clipboard/basics.mdx` around lines 407 - 409, The markdown list item "**戻り値を確認する** - 失敗を適切に処理する" currently has the horizontal rule marker `---` appended to the same line, which can break rendering; edit the MDX so the list item ends without `---` and place the `---` on its own line immediately after the list (i.e., remove `---` from the bullet line and add a standalone `---` line following the list/footer).docs/src/content/docs/ja/features/screens/info.mdx-16-389 (1)
16-389:⚠️ Potential issue | 🟠 Major | ⚡ Quick winKeep all fenced code blocks identical to the English original
The code snippets contain localized text inside fences. In Wails translation docs, code block content must not be translated. Please restore the fenced code bodies from the English source exactly.
Based on learnings: For Wails documentation i18n/translation PRs, do not translate any text inside code blocks in MDX files.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/features/screens/info.mdx` around lines 16 - 389, The fenced code blocks in this MDX were translated to Japanese but must remain identical to the English source; restore each code fence block’s body to the original English code exactly (look for symbols to locate blocks: functions centreOnScreen, moveToScreen, positionTopLeft/TopRight/BottomRight, hasMultipleMonitors, getMonitorCount, listMonitors, chooseMonitor, MultiMonitorManager, NewMultiMonitorManager, CreateWindowOnScreen, CreateWindowOnEachScreen, ScreenMonitor, NewScreenMonitor, OnScreenChange, Start, checkScreens, createDPIAwareWindow, moveWindowToScreen, and the Screen struct) and do not change any code content or identifiers—only replace the localized text inside the fences with the English originals.docs/src/content/docs/ja/features/menus/systray.mdx-310-314 (1)
310-314:⚠️ Potential issue | 🟠 Major | ⚡ Quick winRepair broken markdown blocks (table/fence/separator)
The
```----------|...fragment and merged...小さすぎる---indicate malformed markdown boundaries. Please split into valid code-fence/table/separator blocks.Also applies to: 386-388
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/features/menus/systray.mdx` around lines 310 - 314, The markdown contains a malformed block where the fragment "```----------|--------|--------|-------|" and merged separators like "小さすぎる---" combine code-fence and table/separator syntax; fix by replacing that fragment with a proper fenced code block or a proper Markdown table and a distinct horizontal rule: remove the stray backticks before the table, ensure the table starts with a header row and a separator row using pipes and dashes (e.g., | OS | X | Y | Z | followed by |---|---|---|---|), and place any code examples inside triple backtick fences; also correct the other occurrence ("小さすぎる---") in the same style so table, code-fence, and horizontal rule are separate and valid.docs/src/content/docs/ja/features/menus/application.mdx-297-299 (1)
297-299:⚠️ Potential issue | 🟠 Major | ⚡ Quick winUnmerge malformed markdown boundaries (fence/heading/body)
```## カスタムメニューand...ください。## 完全な例indicate merged markdown constructs. Split these into proper standalone blocks to prevent parser/render issues.Also applies to: 506-508
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/features/menus/application.mdx` around lines 297 - 299, The markdown contains merged fence+heading sequences like "```## カスタムメニュー" and a similar merge before "## 完全な例"; split these into proper standalone constructs by closing or opening the code fence on its own line and placing the heading on its own line (i.e., ensure a line with just ``` starts/ends the fenced block and the next line contains "## カスタムメニュー" or "## 完全な例" as a separate heading), and apply the same fix to the other occurrence mentioned (lines around 506-508) so fences and headings are not concatenated.docs/src/content/docs/ja/features/menus/application.mdx-34-627 (1)
34-627:⚠️ Potential issue | 🟠 Major | ⚡ Quick winRestore all fenced code snippets to English-source verbatim
This file localizes content inside fenced code blocks (comments/text), which should not be translated in Wails i18n docs. Please copy code-fence bodies exactly from the English page.
Based on learnings: For Wails documentation i18n/translation PRs, do not translate any text inside code blocks in MDX files.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/features/menus/application.mdx` around lines 34 - 627, The fenced code blocks in this MDX were translated into Japanese but must match the English-source verbatim; locate the fenced blocks around functions like main(), createMenu(), and helper handlers (handleImport, handleExport, toggleFullscreen, toggleSidebar, toggleToolbar, showSettings, toggleDarkMode, openDocumentation, showAbout) and replace their block bodies with the original English-source code (preserve package/import lines, comments, string literals, and code exactly as in the canonical English doc), ensuring examples showing app.NewMenu(), menu.AddRole(...), app.Menu.Set(menu), app.Window.NewWithOptions(...), window.SetMenu(...), and menu item handlers are restored unchanged; do not translate any text inside fenced code blocks.docs/src/content/docs/ja/features/menus/systray.mdx-24-355 (1)
24-355:⚠️ Potential issue | 🟠 Major | ⚡ Quick winRevert translated text inside fenced code
Code snippets include localized content inside fences. In Wails translation PRs, code blocks must remain identical to English source. Please restore all fenced code bodies verbatim.
Based on learnings: For Wails documentation i18n/translation PRs, do not translate any text inside code blocks in MDX files.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/features/menus/systray.mdx` around lines 24 - 355, Restore every fenced code block in this MDX to the original English source (do not translate any code content); revert the translated Go snippets (e.g., the main function, package imports, variables like icon/iconDark, calls such as application.New, app.SystemTray.New(), systray.SetIcon, systray.SetLabel, menu.Add(...).OnClick, window.Hide(), systray.AttachWindow, SetWindowOffset, SetWindowDebounce, systray.OnClick/OnRightClick/OnDoubleClick, updateTrayIcon, pauseMenuItem.OnClick, rebuildTrayMenu, and the OnShutdown example) back to the verbatim English code from the canonical docs so that all fenced code blocks match the English source exactly.docs/src/content/docs/ja/features/events/system.mdx-18-539 (1)
18-539:⚠️ Potential issue | 🟠 Major | ⚡ Quick winDo not translate fenced code content
This page includes translated text/comments within code fences. For Wails i18n docs, code-fence content must stay exactly as in the English source. Please restore all code blocks verbatim.
Based on learnings: For Wails documentation i18n/translation PRs, do not translate any text inside code blocks in MDX files.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/features/events/system.mdx` around lines 18 - 539, The translated MDX includes changes inside fenced code blocks that must remain verbatim; restore every code fence block so its contents exactly match the English source (e.g., restore snippets containing app.Event.Emit(...), Events.On(...), app.Event.OnApplicationEvent(events.Common.ThemeChanged,...), window.OnWindowEvent(...), window.RegisterHook(...), NotificationService.Notify(...), and the JavaScript Events.Emit/Events.On examples) without any translation or comment edits, ensuring all triple-backtick blocks are reverted to their original English code content.docs/src/content/docs/ja/features/clipboard/basics.mdx-16-401 (1)
16-401:⚠️ Potential issue | 🟠 Major | ⚡ Quick winRevert translated content inside fenced code blocks
Code-fence bodies contain translated text/comments. These must match the English source exactly in translation PRs. Please restore all fenced code blocks verbatim from the original English document.
Based on learnings: For Wails documentation i18n/translation PRs, do not translate any text inside code blocks in MDX files.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/features/clipboard/basics.mdx` around lines 16 - 401, Revert all translated text inside fenced code blocks to match the original English source exactly: restore the literal contents of blocks that include usages of Clipboard.SetText, app.Clipboard.Text(), ClipboardService.CopyToClipboard, copyWithFeedback, pasteText, TextService.CopyText, DataService.PasteAndProcess, CopyService methods, ClipboardMonitor (including Start/Stop/checkClipboard), ClipboardHistory methods, and any JavaScript examples so the code/comments match the upstream English MDX verbatim; do not alter surrounding prose or non-code content.docs/src/content/docs/ja/features/dialogs/overview.mdx-374-376 (1)
374-376:⚠️ Potential issue | 🟠 Major | ⚡ Quick winFix code-fence termination and footer separator formatting
Line 374 uses ```````---`````, which is malformed markdown and risks broken rendering. Close the code fence, then place separator/footer content as separate markdown blocks.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/features/dialogs/overview.mdx` around lines 374 - 376, The markdown contains a malformed code-fence sequence "```---" which breaks rendering; fix by closing the open code fence (replace "```---" with a proper closing triple backtick "```"), then move the horizontal rule/ footer separator ("---") and the following footer text ("**ご質問がありますか？** ...") out of the code block into separate markdown blocks so the separator is its own line and the Discord/link text appears as normal paragraph content; update the snippet around the affected code fence to ensure there's a closing ``` and then the standalone --- and the paragraph with the Discord and example links.docs/src/content/docs/ja/features/menus/reference.mdx-20-357 (1)
20-357:⚠️ Potential issue | 🟠 Major | ⚡ Quick winKeep fenced code content identical to the English source
Several code blocks include translated/Japanese content (e.g., comments and inline explanatory text). In Wails i18n docs, code-fence content must remain exactly as the English original for reliability and copy/paste safety. Please restore these code blocks from the source English page verbatim.
Based on learnings: For Wails documentation i18n/translation PRs, do not translate any text inside code blocks in MDX files.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/features/menus/reference.mdx` around lines 20 - 357, Several fenced Go code blocks (e.g., those showing menu.Add, menu.AddCheckbox, menu.AddRadio, menu.AddSubmenu, menu.AddSeparator, menuItem.SetLabel/OnClick, SetEnabled/SetChecked, SetAccelerator, SetTooltip, menu.Update, etc.) have been translated; revert each code-fence to the exact English original from the source docs so code and inline comments match upstream verbatim. Locate each triple-backtick Go block in this file and replace its contents with the corresponding English block from the canonical English reference page, ensuring no comments, identifiers, or explanatory text inside code fences are translated.docs/src/content/docs/ja/features/dialogs/overview.mdx-16-373 (1)
16-373:⚠️ Potential issue | 🟠 Major | ⚡ Quick winDo not localize fenced code blocks
Multiple snippets contain translated comments/content. For Wails locale docs, fenced code blocks should remain exactly the English source text. Please restore all code fences verbatim.
Based on learnings: For Wails documentation i18n/translation PRs, do not translate any text inside code blocks in MDX files.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/features/dialogs/overview.mdx` around lines 16 - 373, Several fenced code blocks were translated into Japanese; revert every fenced code block back to the original English source (leave only surrounding prose translated). Specifically, restore the code examples that include app.Dialog.Info(), app.Dialog.Question(), app.Dialog.Warning(), app.Dialog.Error(), app.Dialog.OpenFile(), app.Dialog.SaveFile(), the deleteFile(...) function example, and all other fenced snippets so their contents match the English upstream verbatim; do not change code comments, strings, or identifiers inside triple-backtick blocks in this MDX file. Ensure no fenced code block contains Japanese translations before committing.docs/src/content/docs/ja/features/menus/reference.mdx-359-359 (1)
359-359:⚠️ Potential issue | 🟠 Major | ⚡ Quick winFix malformed merged markdown at the section end
Line 359 concatenates the “reason” lead-in and the final CTA into one broken line, which likely drops content and can render incorrectly. Split and restore this section from the English source.
Suggested structure fix
-**これが重要な理由：****ご質問がありますか？** [Discord](https://discord.gg/JDdSxwjhGf) で質問するか、[メニューの例](https://github.com/wailsapp/wails/tree/master/v3/examples/menu) をご覧ください。 +**これが重要な理由：** + +（この段落は英語ソースから復元） + +**ご質問がありますか？** [Discord](https://discord.gg/JDdSxwjhGf) で質問するか、[メニューの例](https://github.com/wailsapp/wails/tree/master/v3/examples/menu) をご覧ください。🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ja/features/menus/reference.mdx` at line 359, The final line merged the heading and CTA into one malformed sentence ("これが重要な理由：****ご質問がありますか？** ..."); split it into the proper structure by restoring the heading "これが重要な理由：" (as its own bold lead-in followed by the corresponding explanatory sentence from the English source) and place the CTA as a separate bold question "ご質問がありますか？" followed by the Discord link and the menu example link (https://discord.gg/JDdSxwjhGf and https://github.com/wailsapp/wails/tree/master/v3/examples/menu) so the heading, explanation, and CTA are distinct elements.
| ```d2 | ||
| direction: down | ||
|
|
||
| Start: "Application Start" { | ||
| shape: oval | ||
| style.fill: "#10B981" | ||
| } | ||
|
|
||
| Init: "Initialisation" { | ||
| Create: "Create Application" { | ||
| shape: rectangle | ||
| } | ||
|
|
||
| Register: "Register Services" { | ||
| shape: rectangle | ||
| } | ||
|
|
||
| Setup: "Setup Windows/Menus" { | ||
| shape: rectangle | ||
| } | ||
| } | ||
|
|
||
| Run: "Event Loop" { | ||
| Events: "Process Events" { | ||
| shape: rectangle | ||
| } | ||
|
|
||
| Messages: "Handle Messages" { | ||
| shape: rectangle | ||
| } | ||
|
|
||
| Render: "Update UI" { | ||
| shape: rectangle | ||
| } | ||
| } | ||
|
|
||
| Shutdown: "Shutdown" { | ||
| Cleanup: "Cleanup Resources" { | ||
| shape: rectangle | ||
| } | ||
|
|
||
| Save: "Save State" {--- | ||
|
|
||
| **アーキテクチャについて質問がありますか？** [Discord](https://discord.gg/JDdSxwjhGf) で質問するか、[API リファレンス](/ja/reference/overview) を確認してください。 No newline at end of file |
There was a problem hiding this comment.
ライフサイクル図のコードブロックが途中で壊れています。
{--- で途切れており、D2 ブロック/ファイル終端が閉じていません。MDX のパース失敗につながるため、原文の完全なブロックに戻してください。
修正イメージ（抜粋）
- Save: "Save State" {---
+ Save: "Save State" {
+ shape: rectangle
+ }
+}
+...
+```🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/src/content/docs/ja/concepts/architecture.mdx` around lines 285 - 328,
The D2 diagram block is cut off at `Save: "Save State" {---` causing an unclosed
`{` and missing the closing ```d2; restore the original/complete D2 block by
finishing the Save node (close its `{}`), close the Shutdown group braces
(matching `Shutdown: "Shutdown" { ... }`), and add the terminating ```d2 fence
so the MDX parses; look for the diagram symbols Save: "Save State", Shutdown:
"Shutdown", and the opening ```d2 to locate and properly close the structure.
| ```go | ||
| // Go | ||
| type User struct { | ||
| ID int `json:"id"` | ||
| Name string `json:"name"` | ||
| Email string `json:"email"` | ||
| } | ||
|
|
||
| func GetUser(id int) (*User, error) { | ||
| return &User{ | ||
| ID: id, | ||
| Name: "Alice",--- | ||
|
|
||
| **ブリッジについて質問がありますか？** [Discord](https://discord.gg/JDdSxwjhGf) で質問するか、[バインディングの例](https://github.com/wailsapp/wails/tree/master/v3/examples/binding) を確認してください。 No newline at end of file |
There was a problem hiding this comment.
構造体サンプルが途中で切れており、コードが不正です。
Line 389 の ,--- 以降で GetUser の戻り値・閉じ括弧・コードフェンスが欠落しています。ページ表示/可読性に直結するため、原文どおり完全なコードブロックへ復元してください。
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/src/content/docs/ja/concepts/bridge.mdx` around lines 378 - 391, The Go
example is truncated: the GetUser function return, closing braces and the
closing code fence are missing after the User struct and the partial return
(&User{ ... ,---). Restore the complete GetUser implementation to return a
properly constructed *User (populate ID, Name, Email), close the function with
the final brace, and add the closing triple-backtick to end the code block so
the User type, GetUser function, and code fence are syntactically correct (look
for the User struct and GetUser symbols to locate the snippet).
| ```go | ||
| app := application.New(application.Options{ | ||
| OnShutdown: func() { | ||
| // Save application state | ||
| saveState() | ||
|
|
||
| // Close connections----------|--------------------------------| | ||
| | macOS | アプリケーションは実行中のまま（メニューバーが残る） | | ||
| | Windows | アプリケーションが終了する | | ||
| | Linux | アプリケーションが終了する | | ||
|
|
||
| macOS は、ウィンドウがなくてもアプリケーションがメニューバーでアクティブなままになるというネイティブなプラットフォームの規約に従います。Windows と Linux はデフォルトで終了します。 |
There was a problem hiding this comment.
コードブロックとMarkdownテーブルが混在して壊れています
Line 315-318 と Line 367 で、Goコード・表・本文が連結されており、フェンス構造が破綻しています。MDXのレンダリング失敗または意図しない表示になります。コードブロックを正しく閉じ、表は独立セクションとして分離してください。
修正イメージ（構造分離）
- // Close connections----------|--------------------------------|
-| macOS | アプリケーションは実行中のまま（メニューバーが残る） |
-| Windows | アプリケーションが終了する |
-| Linux | アプリケーションが終了する |
+ // Close connections
+ closeConnections()
+ },
+})
+```
+
+| Platform | 最後のウィンドウを閉じたときのデフォルト動作 |
+|----------|-----------------------------------------------|
+| macOS | アプリは実行中のまま（メニューバーが残る） |
+| Windows | アプリケーションが終了する |
+| Linux | アプリケーションが終了する |Based on learnings: In translation PRs, code block contents and structure must remain intact (no translated/altered fenced code content).
Also applies to: 367-367
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/src/content/docs/ja/concepts/lifecycle.mdx` around lines 309 - 320, The
MDX mixes a fenced Go code block (the application.New(application.Options{ ...
OnShutdown func() { saveState() } snippet) with a Markdown table, breaking
rendering; close the Go fence right after the Go snippet (ensure the trailing
```go fence is present after the OnShutdown/saveState block and any closing
braces), then move the platform table into its own standalone Markdown section
(start a new paragraph and add the table with headers "Platform" and
"最後のウィンドウを閉じたときのデフォルト動作"), and ensure no code fences or inline backticks remain
around the table so the code block and the table are fully separated.
| ```bash | ||
| git push origin docs/improve-window-api-examples | ||
| ```PR内では: | ||
| - 文書をどのように改善したかを記述してください |
There was a problem hiding this comment.
MDX のコードフェンスが壊れています
```PR内では: となっており、フェンス終了と本文が連結されています。これはレンダリング/パース失敗の原因になります。フェンスを閉じた後に通常段落として分離してください。
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/src/content/docs/ja/contributing/getting-started.mdx` around lines 331 -
334, Close the MDX code fence so the triple-backtick is terminated on its own
line and separate the following text into a normal paragraph instead of being
appended to the fence (the offending token is the merged fence/text
"```PR内では:"); ensure the file at
docs/src/content/docs/ja/contributing/getting-started.mdx has the ``` closing
line after the git push block and then a new paragraph starting with "PR内では:"
describing how the document was improved.
| ```go | ||
| //go:build darwinpackage application | ||
|
|
||
| // macOS固有のコード | ||
| ``` |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
# First, let's check if the file exists and read the relevant lines
wc -l docs/src/content/docs/ja/contributing/standards.mdxRepository: wailsapp/wails
Length of output: 114
🏁 Script executed:
# Read the specific lines mentioned in the review
sed -n '435,450p' docs/src/content/docs/ja/contributing/standards.mdxRepository: wailsapp/wails
Length of output: 205
🌐 Web query:
Go build tag syntax specification //go:build directive
💡 Result:
Go build tag syntax for the //go:build directive (build constraints) 1) Where it goes / basic form - A build constraint (build tag) is a line comment beginning with //go:build. [1][2] - It must appear near the top of the file, preceded only by blank lines and other line comments. In Go files, it must appear before the package clause. [3] - To distinguish it from package documentation, a build constraint should be followed by a blank line. [3] 2) Expression language (the “syntax specification”) A //go:build line contains an expression over build tags using boolean operators and parentheses. [3] - Operators supported: || (OR), && (AND),! (NOT). [3] - Parentheses are supported to group subexpressions. [3] - Operators have the same meaning as in Go. [3] Example: [3] //go:build (linux && 386) || (darwin &&!cgo) 3) What counts as “satisfied” tags during a build When evaluating a //go:build expression, these tags are considered satisfied: [3][2] - GOOS (target OS), using the same spelling as runtime.GOOS. [3] - GOARCH (target architecture), using the same spelling as runtime.GOARCH. [3] - The compiler being used, either “gc” or “gccgo”. [3] - “cgo”, if the cgo command is supported (see CGO_ENABLED). [3] - Version tags of the form “go1.X” for the current toolchain’s supported versions (e.g., “go1.12” meaning Go 1.12 and later). [3] - Any additional tags provided by the -tags flag (see 'go help build'). [3] 4) Conversion / compatibility with the legacy // +build syntax - Go 1.17 introduced //go:build as a more readable build-constraint syntax, alongside the older // +build form. [4][3] - The gofmt tool keeps the two forms in sync and treats //go:build as the source of truth when both are present. [5] 5) How Go parses the expression internally (implementation constraints) - The go/build/constraint package parses “//go:build...” and also the legacy “// +build...” syntax, returning a boolean-expression AST (And/Or/Not/Tag). [4][6] - It enforces a complexity limit while parsing (to prevent stack exhaustion); a SyntaxError is returned for invalid expressions. [7] If you want, I can also provide the exact recommended style rules (spacing, using parentheses, and migration examples) using the official command help and/or gofmt behavior; tell me whether you’re targeting only modern Go (1.17+) or also want legacy // +build compatibility.
Citations:
- 1: https://pkg.go.dev/go/build@go1.25.6
- 2: https://golang.org/pkg/go/build/
- 3: https://pkg.go.dev/cmd/go/internal/help@go1.24.2
- 4: https://pkg.go.dev/go/build/constraint@go1.25.6
- 5: http://vcs-test.golang.org/design/draft-gobuild
- 6: https://github.com/golang/go/blob/go1.21.5/src/go/build/constraint/expr.go
- 7: https://go.dev/src/go/build/constraint/expr.go
Go の build tag サンプルが文法的に不正です。
//go:build darwinpackage application は無効です。darwin は有効な GOOS タグですが、darwinpackage と application を結合した形式は Go build tag 構文に違反しています。//go:build darwin と package application は分離し、build tag の後に空行を配置してください。
🔧 Suggested fix
-//go:build darwinpackage application
+//go:build darwin
+
+package application📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ```go | |
| //go:build darwinpackage application | |
| // macOS固有のコード | |
| ``` |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/src/content/docs/ja/contributing/standards.mdx` around lines 439 - 443,
The build tag line `//go:build darwinpackage application` is invalid; split it
into a proper Go build tag and package declaration by replacing that line with a
valid build tag `//go:build darwin`, add a single blank line immediately after
the build tag, and then put the package declaration `package application`;
ensure no other tokens are on the build-tag line and that the blank line
separates the build tag from the `package` statement.
| func (a *AuthService) requireAuth(token string) (*Session, error) { | ||
| a.mu.RLock() | ||
| session, ok := a.sessions[token] | ||
| a.mu.RUnlock() | ||
|
|
||
| if !ok { | ||
| return nil, errors.New("not authenticated") | ||
| } | ||
|
|
||
| if time.Now().After(session.ExpiresAt) {--- | ||
|
|
||
| **ご質問がありますか？** [Discord](https://discord.gg/JDdSxwjhGf) で質問するか、[binding examples](https://github.com/wailsapp/wails/tree/master/v3/examples/binding) をご確認ください。 No newline at end of file |
There was a problem hiding this comment.
認証サンプルが途中で壊れており、コードフェンスも欠落しています。
Line 363 の {--- でブロックが切断され、関数/コードブロックが閉じていません。MDXレンダリング不良の原因になるため、原文の完全なブロックへ戻してください。
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/src/content/docs/ja/features/bindings/best-practices.mdx` around lines
354 - 365, The code sample for AuthService.requireAuth is truncated and missing
the rest of the function and closing code fence; restore the full function body
for requireAuth (including the expiration check handling that returns an error
when time.Now().After(session.ExpiresAt), any needed mu unlocking, and the final
return of the session), remove the stray "{---" token, and re-add the proper
closing brace and MDX code fence so the example compiles and renders correctly
(look for symbols: func (a *AuthService) requireAuth, a.sessions,
session.ExpiresAt).
| **フロントエンド:** | ||
|
|
||
| ```html | ||
| <div class="login-dialog"> | ||
| <h2>Login</h2>--- | ||
|
|
||
| **ご質問がありますか？** [Discord](https://discord.gg/JDdSxwjhGf) で質問するか、[カスタムダイアログの例](https://github.com/wailsapp/wails/tree/master/v3/examples/dialogs) をご確認ください。 No newline at end of file |
There was a problem hiding this comment.
Critical: Login dialog frontend example is truncated.
The complete login dialog example is incomplete. Line 381 shows <h2>Login</h2>--- where the content abruptly cuts off. The frontend HTML/JavaScript implementation is missing, making this example unusable.
The Go backend code (lines 322-375) is complete, but the corresponding frontend code needed to create the actual login form UI is truncated. Readers cannot implement this pattern without the complete frontend example.
Expected frontend content
The complete frontend example should include:
- HTML form structure with username and password input fields
- Submit and Cancel buttons
- JavaScript/TypeScript code to handle form submission
- Event emission to communicate with the Go backend (
Submit()andCancel()methods) - Styling for the custom dialog appearance
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/src/content/docs/ja/features/dialogs/custom.mdx` around lines 377 - 383,
The frontend login dialog example is truncated at "<h2>Login</h2>---"; restore a
complete HTML/JS example that matches the Go backend by adding a full form with
username and password inputs, Submit and Cancel buttons, and JS/TS handlers that
call the backend dialog methods (e.g., invoke Submit() and Cancel()) and emit
events back to the Go code; include minimal CSS for the custom-dialog appearance
and an example of handling form submission (preventDefault, validate, call
Submit() with credentials) and cancel behavior so readers can reproduce the
pattern demonstrated by the Go backend.
| ### 終了確認 | ||
|
|
||
| ```go--- | ||
|
|
||
| **ご質問がありますか？** [Discord](https://discord.gg/JDdSxwjhGf) で質問するか、[ダイアログの例](https://github.com/wailsapp/wails/tree/master/v3/examples/dialogs) をご確認ください。 No newline at end of file |
There was a problem hiding this comment.
Critical: Exit confirmation example is truncated.
The "終了確認" (Exit Confirmation) section starting at line 380 is incomplete. Line 382 shows ````go---` which is malformed - it appears content was truncated during the documentation generation process.
This section should provide a complete example of how to implement an exit confirmation dialog, but the code example is missing entirely.
Expected content
The exit confirmation example should demonstrate:
- Using a Question dialog when the application is closing
- Checking for unsaved changes
- Handling Save/Don't Save/Cancel options
- Integration with window close handlers
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/src/content/docs/ja/features/dialogs/message.mdx` around lines 380 -
384, The "終了確認" section contains a malformed/truncated code block (```go---) and
must be replaced with a complete Go example showing an exit-confirmation flow:
add a sample ConfirmExit (or OnBeforeClose) function that checks an
unsavedChanges boolean, calls dialog.Question with buttons "Save", "Don't Save",
"Cancel" (using dialog.Question), and branches to call SaveChanges (or
SaveDocument) on "Save", allow close on "Don't Save", and cancel the close on
"Cancel"; ensure the example also demonstrates wiring this handler to the window
close event (e.g., OnBeforeClose or window's close handler) so readers can see
integration.
| // Transparent title bar--- | ||
|
|
There was a problem hiding this comment.
Incomplete code block - file appears truncated.
The macOS code block starts but is never completed or closed. This will break MDX rendering and prevent the page from displaying correctly.
The file appears to have been cut off during translation. The code block needs to be completed with proper macOS-specific window configuration examples, or removed if this section is not yet ready.
🔧 Recommended action
Either complete the code block with appropriate macOS window configuration examples, or remove the incomplete section:
<TabItem label="macOS" icon="apple">
**macOS 固有の機能:**
- ```go
- // Transparent title bar---
+ ```go
+ // macOS specific window features would go here
+ // This section needs to be completed
+ ```
**ご質問がありますか？** [Discord](https://discord.gg/JDdSxwjhGf) で質問するか、[ウィンドウの例](https://github.com/wailsapp/wails/tree/master/v3/examples) をご確認ください。Alternatively, refer to the English source to restore the missing content.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/src/content/docs/ja/features/windows/basics.mdx` around lines 415 - 416,
The MDX contains an unclosed/incomplete macOS code block starting at the comment
token "// Transparent title bar---"; fix by either completing the fenced code
block (add opening/closing ```go and populate with macOS-specific window
configuration example lines a la the English source) or remove that incomplete
section entirely so the MDX renders; update the block around the "// Transparent
title bar---" token accordingly and ensure the file contains a matching closing
triple-backtick.
| ## 完全な例 | ||
|
|
||
| 以下は、完全なイベント処理を備えた本番環境対応のウィンドウの例です： | ||
|
|
||
| ```go | ||
| package main | ||
|
|
||
| import ( | ||
| "encoding/json" | ||
| "fmt" | ||
| "os" | ||
| "github.com/wailsapp/wails/v3/pkg/application" | ||
| ) | ||
|
|
||
| type WindowState struct { | ||
| X int `json:"x"` | ||
| Y int `json:"y"` | ||
| Width int `json:"width"` | ||
| Height int `json:"height"` | ||
| Maximised bool `json:"maximised"` | ||
| Fullscreen bool `json:"fullscreen"` | ||
| } | ||
|
|
||
| type ManagedWindow struct { | ||
| app *application.Application--- | ||
|
|
||
| **ご質問がありますか？** [Discord](https://discord.gg/JDdSxwjhGf) で質問するか、[例](https://github.com/wailsapp/wails/tree/master/v3/examples) を確認してください。 No newline at end of file |
There was a problem hiding this comment.
Critical: Complete example is truncated and unusable.
The "完全な例" (Complete Example) section is incomplete. Line 420 shows app *application.Application--- which abruptly cuts off the struct definition. The code example cannot compile or be used by readers.
This appears to be a content generation or copy-paste issue where the full example was not included. The example needs to be completed to show the full ManagedWindow struct implementation and usage.
Expected structure
The complete example should include:
- Full
ManagedWindowstruct definition with all fields - Complete implementation of window event handlers
- State persistence logic
- UI update coordination
- Resource cleanup demonstration
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/src/content/docs/ja/features/windows/events.mdx` around lines 396 - 422,
The example is truncated at the ManagedWindow definition (shows "app
*application.Application---"); restore the full runnable example by completing
the ManagedWindow struct and all related methods (constructor, event handlers
such as OnResize/OnMove/OnClose or whatever handlers are referenced, Save/Load
state persistence using WindowState, UI update coordination, and cleanup),
ensure references to types like WindowState and application.Application are
consistent, and include the usage/demo code that constructs ManagedWindow, wires
event listeners to the application/window instance, and demonstrates state
persistence so the snippet compiles and is copy-paste usable.
Automated translation run via Wails Doc Translator agent — 2026-05-11.
QA Scores
Files Flagged for Human Review (score < 0.75)
All flagged files scored 0.650 due to code block count mismatches and import count mismatches:
features/bindings/methods.mdx— Code block count mismatch (src=29, tgt=23), Import count mismatch (src=9, tgt=7)features/bindings/models.mdx— Code block count mismatch (src=34, tgt=25), Import count mismatch (src=14, tgt=10)features/bindings/services.mdx— Code block count mismatch (src=23, tgt=22), Import count mismatch (src=2, tgt=1)features/menus/systray.mdx— Code block count mismatch (src=21, tgt=13), Import count mismatch (src=4, tgt=3)features/windows/multiple.mdx— Code block count mismatch (src=24, tgt=22), Import count mismatch (src=3, tgt=2)guides/events-reference.mdx— Code block count mismatch (src=20, tgt=15), Import count mismatch (src=19, tgt=15)reference/events.mdx— Code block count mismatch (src=35, tgt=33), Import count mismatch (src=22, tgt=21)reference/window.mdx— Code block count mismatch (src=60, tgt=42), Import count mismatch (src=5, tgt=3)Locales: ja
Files: 102 new translations
CC @leaanthony
Summary by CodeRabbit