i18n(ko): add Korean translations 2026-05-11#5392
Open
leaanthony wants to merge 1 commit into
Open
Conversation
Contributor
WalkthroughAdds a large set of Korean documentation pages across concepts, features, guides, and contributing, plus credits/FAQ/feedback, and updates translation-cache timestamps. No source code or APIs changed. ChangesKorean Documentation Import and Cache Refresh
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~30 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}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 16
Note
Due to the large number of review comments, Critical severity comments were prioritized as inline comments.
🟡 Minor comments (11)
docs/src/content/docs/ko/community/links.md-21-21 (1)
21-21:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winUse official capitalization for “GitHub”.
Line 21 says
Github Issues; change it toGitHub Issuesfor consistency with official naming.🤖 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/ko/community/links.md` at line 21, The link text "[Github Issues]" uses incorrect capitalization; update the markdown link label to "GitHub Issues" (i.e., change the link text in the entry currently written as [Github Issues](https://github.com/wailsapp/wails/issues) to [GitHub Issues](https://github.com/wailsapp/wails/issues)) so the official "GitHub" capitalization is used everywhere.docs/src/content/docs/ko/contributing/standards.mdx-439-443 (1)
439-443:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winFix malformed Go build-tag example.
Line 440 currently shows
//go:build darwinpackage applicationas one line. It should be two lines so the example is syntactically correct.Suggested fix
-//go:build darwinpackage application +//go:build darwin + +package application🤖 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/ko/contributing/standards.mdx` around lines 439 - 443, The example build-tag line is malformed: replace the single incorrect token "//go:build darwinpackage application" with two separate build-tag lines so the Go build tags are valid; locate the occurrence of the string "//go:build darwinpackage application" and split it into two lines such as "//go:build darwin" and "//go:build application" (ensuring each build tag appears on its own line in the example).docs/src/content/docs/ko/features/bindings/models.mdx-454-454 (1)
454-454:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winSplit merged heading and divider token.
Line 454 combines a heading and horizontal rule (
## 고급 패턴---). This should be split to render correctly.Suggested patch
-## 고급 패턴--- +## 고급 패턴 + +---🤖 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/ko/features/bindings/models.mdx` at line 454, The markdown line "## 고급 패턴---" combines a level-2 heading and a horizontal rule; split it into two lines by making the heading "## 고급 패턴" and placing the horizontal rule on the following line as "---" so the heading and divider render separately in models.mdx.docs/src/content/docs/ko/features/windows/options.mdx-220-224 (1)
220-224:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winAdd missing list marker for consistency.
Line 222 is missing the
-prefix that the other list items have:**사용 사례:** - 고정 크기 애플리케이션 - 과도한 리소스 사용 방지 +- 과도한 리소스 사용 방지 - 디자인 제약 유지🤖 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/ko/features/windows/options.mdx` around lines 220 - 224, The second bullet in the list under "사용 사례:" is missing a leading "-" marker; update the list so each item uses the same markdown list prefix (add "-" before "과도한 리소스 사용 방지") so the three items ("- 고정 크기 애플리케이션", "- 과도한 리소스 사용 방지", "- 디자인 제약 유지") are consistently rendered.docs/src/content/docs/ko/features/bindings/services.mdx-613-613 (1)
613-613:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winRemove trailing markdown artifact
서비스는 공유됨---has a dangling---suffix. This should be cleaned to avoid malformed rendering.🤖 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/ko/features/bindings/services.mdx` at line 613, Remove the trailing markdown artifact " ---" from the sentence containing "서비스는 공유됨---" so it reads "서비스는 공유됨"; locate and edit the paragraph in docs/src/content/docs/ko/features/bindings/services.mdx where that exact string appears and delete the dangling hyphens to prevent malformed rendering.docs/src/content/docs/ko/contributing/testing-ci.mdx-3-16 (1)
3-16:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winUse standard term for race conditions
경동is non-standard here and reads unclear. Consider replacing with경쟁 상태or데이터 레이스consistently.🤖 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/ko/contributing/testing-ci.mdx` around lines 3 - 16, The term "경동" is non-standard—replace all occurrences (e.g., the table row label "경동 감지" and the descriptive phrase "런타임 및 브리지의 데이터 경동 포착") with a single consistent term such as "데이터 레이스 감지" (or alternatively "경쟁 상태 감지") and update the adjacent examples (`go test -race`, `wails3 dev -race`) to match the chosen wording so the heading and description remain consistent.docs/src/content/docs/ko/features/keyboard/shortcuts.mdx-14-23 (1)
14-23:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winAlign API naming in prose with examples
The text says
KeyBindingsbut code usesapp.KeyBinding. Please make the prose consistent with the actual API name used in examples.🤖 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/ko/features/keyboard/shortcuts.mdx` around lines 14 - 23, Update the prose to match the actual API name used in the example: change references to `KeyBindings` to `KeyBinding` so the text consistently refers to app.KeyBinding; ensure any explanatory sentence mentioning the manager uses the exact identifier `KeyBinding` to avoid confusion with `KeyBindings`.docs/src/content/docs/ko/contributing/codebase-layout.mdx-78-78 (1)
78-78:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winCorrect v3 CLI command prefix.
Use
wails3 init -t <framework>instead ofwails init -t <framework>.Based on learnings: Wails v3 documentation should use the
wails3command prefix.🤖 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/ko/contributing/codebase-layout.mdx` at line 78, Update the CLI command examples to use the v3 prefix by replacing any occurrence of "wails init -t <framework>" with "wails3 init -t <framework>" in the documentation; look for the exact string "wails init -t <framework>" (e.g., near the packager list item) and update it so all examples and instructions consistently use "wails3 init -t <framework>".docs/src/content/docs/ko/contributing/index.mdx-78-78 (1)
78-78:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winUse
wails3prefix for v3 CLI command examples.
wails init -t <framework>should bewails3 init -t <framework>for consistency with v3 CLI docs.Based on learnings: When reviewing Wails documentation, 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/ko/contributing/index.mdx` at line 78, Update the CLI example string in the "템플릿 시스템" entry: replace the incorrect `wails init -t <framework>` command with the v3-prefixed `wails3 init -t <framework>` so all Wails v3 docs consistently use the `wails3` prefix; locate the sentence containing the `템플릿 시스템` table row and change the command text accordingly.docs/src/content/docs/ko/features/windows/frameless.mdx-787-787 (1)
787-787:⚠️ Potential issue | 🟡 Minor | ⚡ Quick win불릿 문장 끝의
---를 제거하세요.Line 787의
---는 잔여 마크업으로 보이며 문서 렌더링에 노이즈를 만듭니다.🤖 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/ko/features/windows/frameless.mdx` at line 787, Remove the trailing residual markup by editing the bullet line that reads "버튼에 no-drag를 잊지 마세요" and delete the ending '---' so the line becomes a normal bullet text without the stray dashes; locate the exact string "버튼에 no-drag를 잊지 마세요---" and replace it with "버튼에 no-drag를 잊지 마세요".docs/src/content/docs/ko/features/clipboard/basics.mdx-407-407 (1)
407-407:⚠️ Potential issue | 🟡 Minor | ⚡ Quick win불릿 끝의
---잔여 마크다운을 제거하세요.Line 407의
---가 본문에 노출되어 렌더링 품질을 떨어뜨립니다.🤖 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/ko/features/clipboard/basics.mdx` at line 407, Remove the trailing markdown rule markers by editing the bullet line that currently reads "**반환값 확인** - 실패를 우아하게 처리하세요---" and delete the trailing '---' so the rendered bullet ends cleanly (e.g., "**반환값 확인** - 실패를 우아하게 처리하세요"). Ensure no extra markdown rule markers remain adjacent to the bullet text.
🤖 Prompt for all review comments with 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.
Inline comments:
In `@docs/src/content/docs/ko/concepts/architecture.mdx`:
- Around line 285-328: The D2 diagram block is truncated at the node "Save:
\"Save State\" {---", breaking parsing; restore the missing closing braces and
the closing triple-backtick fence so the diagram is complete (ensure every
opened block such as Start, Init, Create, Register, Setup, Run, Events,
Messages, Render, Shutdown, Cleanup, and Save has matching closing braces) and
place the closing ``` fence immediately before the final paragraph that begins
"**아키텍처에 대해 질문이 있으신가요?**" so the text after the diagram is outside the fenced
diagram block.
In `@docs/src/content/docs/ko/concepts/bridge.mdx`:
- Around line 389-391: The MDX code block tail is corrupted by the stray '---'
in the snippet containing `Name: "Alice",---`; locate the snippet that includes
that exact string and restore the full original fenced code block content
(remove the stray '---' artifact), ensure the block is properly terminated with
the matching fence (triple backticks or proper MDX block delimiter), and verify
the block's contents are intact and not truncated (references: the snippet
containing `Name: "Alice",---`).
In `@docs/src/content/docs/ko/concepts/lifecycle.mdx`:
- Around line 315-320: The OnShutdown example in the "OnShutdown" section has
its fenced code block interrupted by table rows and a concatenated paragraph;
fix it by closing the MDX/markdown code fence for the OnShutdown example before
the table (and ensure there is a blank line after the closing fence), move the
platform table out of the code block into normal markdown, and ensure the
subsequent paragraph is separated by a blank line from the table so the MDX
parses correctly; locate the broken example by searching for the "OnShutdown"
header and the surrounding fenced code block in the file.
In `@docs/src/content/docs/ko/contributing/asset-server.mdx`:
- Line 75: Remove the stray Chinese character '为' from the Korean sentence
mentioning `assetserver_dev.go` so the phrase reads naturally (e.g.,
"assetserver_dev.go 는 단순히 해당 대상으로 프록시합니다.")—edit the line in
docs/src/content/docs/ko/contributing/asset-server.mdx to delete the '为'
character or replace the machine-translated fragment with the correct Korean
equivalent `대상으로`.
In `@docs/src/content/docs/ko/contributing/getting-started.mdx`:
- Around line 331-334: The markdown fence is broken because the sequence
"```PR에서..." merges the code fence and text; locate the PR submission section
containing the malformed fence (the line that begins with "```PR...") and split
it so the triple backticks are on their own line to open/close the code block
and the PR instruction text is plain text outside the fence; ensure you add a
closing triple backtick after the example command and that the PR instructions
(e.g., "PR에서 다음 내용을 명시하세요:" and the list item "어떤 문서를 개선했는지") are rendered as
normal text following the fenced block.
In `@docs/src/content/docs/ko/features/bindings/best-practices.mdx`:
- Around line 326-365: The documentation's Go auth example is truncated inside
the requireAuth method (AuthService.requireAuth) at the check "if
time.Now().After(session.ExpiresAt) {" which leaves the function and the fenced
code block unclosed and breaks rendering; restore the missing closing logic for
the expiry check (e.g., return an error and delete expired session from
a.sessions while holding mu), properly unlock the mutex, close the requireAuth
function, and add the closing ``` to end the fenced Go block so the rest of the
page renders correctly.
In `@docs/src/content/docs/ko/features/bindings/methods.mdx`:
- Around line 102-125: The mutex field mu in CounterService is declared as
sync.Mutex but GetCount calls RLock/RUnlock (which only exist on sync.RWMutex),
so change the declaration of mu in CounterService from sync.Mutex to
sync.RWMutex so Increment and Decrement continue to use Lock/Unlock and GetCount
can use RLock/RUnlock; update the mu type in the struct definition
(CounterService.mu) accordingly.
In `@docs/src/content/docs/ko/features/dialogs/custom.mdx`:
- Around line 379-383: The MDX file contains a malformed/truncated HTML code
block where the line with <h2>Login</h2> includes trailing dashes and the
login-dialog block is not closed, breaking the rest of the page; edit the
snippet around the <div class="login-dialog"> and the <h2>Login</h2> line to
remove the trailing `---`, add the missing closing elements for the login dialog
(e.g., complete the rest of the login markup and add </div>), and ensure the
surrounding triple-backtick fence is properly closed so the code block renders
correctly.
In `@docs/src/content/docs/ko/features/dialogs/file.mdx`:
- Around line 328-330: Replace the malformed closing code-fence marker "```---"
with the correct YAML/doc separator "---" in the docs entry (remove the stray
backticks); locate the string "```---" in
docs/src/content/docs/ko/features/dialogs/file.mdx (near the end of the example)
and change it to just "---" so the document closes properly.
In `@docs/src/content/docs/ko/features/dialogs/message.mdx`:
- Around line 382-384: The document has a malformed closing code fence
"```go---" (a copy-paste of the prior code block) that should be a plain closing
frontmatter/section marker; find the token "```go---" in
docs/src/content/docs/ko/features/dialogs/message.mdx (look for the code fence
around the end of the example) and replace it with a simple `---` so the
document closes correctly and the following text ("**질문이 있으신가요?** ...") renders
as intended.
In `@docs/src/content/docs/ko/features/dialogs/overview.mdx`:
- Line 374: The Markdown code block is left unterminated because the invalid
closing token "```---" is used; locate the literal "```---" (the incorrect fence
closure) in the document and replace it with the proper code-fence closing token
"```" so the preceding code block is correctly terminated and the page rendering
is fixed.
In `@docs/src/content/docs/ko/features/menus/systray.mdx`:
- Around line 310-314: The markdown has a corrupted table/markdown fence near
the platform/troubleshooting sections: remove the stray/merged separator
fragments (e.g. the "```----------|--------|..." and concatenated '---' pieces),
restore a valid Markdown table header/separator row (use proper pipe-delimited
header and a matching "| --- | --- | --- | --- |" separator), ensure any
triple-backtick fences are balanced or removed, and fix the trailing '---' that
got appended into list text; apply the same cleanup to the other occurrence
referenced (lines ~386-388) so the platform and troubleshooting sections render
correctly.
In `@docs/src/content/docs/ko/features/screens/info.mdx`:
- Around line 339-343: The MDX page has an unclosed Go fenced code block
starting at the function createDPIAwareWindow which causes prose to be rendered
inside the code fence; fix by closing the```go fenced block after the function
body (e.g., ensure the block contains only the Go code for func
createDPIAwareWindow(screen *Screen) *application.WebviewWindow { ... } and add
the closing ```), and move the following Korean prose ("질문 있으신가요? ...") back
outside the code fence so the markdown/MDX parses correctly.
In `@docs/src/content/docs/ko/features/windows/basics.mdx`:
- Around line 411-417: The macOS TabItem (label="macOS") in
docs/src/content/docs/ko/features/windows/basics.mdx opens a Go code fence but
the file ends abruptly, breaking MDX structure; fix it by closing the opened Go
fence (add the missing ```), then close the TabItem container (</TabItem>) and
any surrounding Tabs/TabGroup container that was opened earlier so the tab
structure is balanced; ensure the closing tokens are placed immediately after
the intended macOS code/example and that the TabItem label="macOS" block is
properly terminated.
In `@docs/src/content/docs/ko/features/windows/options.mdx`:
- Around line 1000-1002: Replace the malformed frontmatter/code-fence markers in
the MDX: locate the stray "```---" and any accidental "```go" lines in the
document (near the closing frontmatter around the block with "질문 있으신가요?") and
change them so the frontmatter is closed with a single line containing only
"---"; remove the extraneous backtick fences to ensure a proper MDX frontmatter
close.
- Line 421: In the BackgroundColour initialization using application.RGBA (the
struct with fields R, G, B, A) replace the incorrect field name H with B so the
struct literal uses R, G, B, A; locate the BackgroundColour: application.RGBA{R:
0, G: 0, H: 0, A: 255} entry and change the H field to B to match the RGBA
struct fields.
---
Major comments:
In `@docs/src/content/docs/ko/community/templates.md`:
- Around line 23-31: Update the v3 CLI command examples by replacing the `wails
init` invocations with `wails3 init` so copy/paste works for Wails v3;
specifically change the quoted command strings `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` to use `wails3 init`
instead.
In `@docs/src/content/docs/ko/concepts/bridge.mdx`:
- Around line 84-388: The PR localized text inside fenced code and d2 diagram
blocks but these must remain verbatim; locate the fenced snippets (look for the
symbols/blocks: GreetService, Greet, Add, Divide, Example, Sum, GetConfig, User,
GetUser and the d2 diagram block) and revert any translated content inside those
```go, ```typescript, ```javascript and ```d2 fences back to the original source
examples, ensuring code, embedded commands and the d2 diagram source are exactly
as upstream (no Korean localization) while leaving surrounding explanatory text
translated.
In `@docs/src/content/docs/ko/concepts/lifecycle.mdx`:
- Around line 176-307: Restore all code block contents in this MDX to the
original English text (do not translate code). Revert the translated Go examples
so MyService struct and its methods (ServiceStartup, ServiceShutdown), the app
initialization snippet (app := application.New(...),
application.NewService(&MyService{})), the context example using ctx :=
app.Context(), and the ShouldQuit/OnShutdown callback examples are exactly the
original English source code and strings; ensure the fenced code blocks for the
examples (including the background goroutine with ticker and the ShouldQuit
dialog snippet) match the English docs verbatim.
In `@docs/src/content/docs/ko/contributing.mdx`:
- Around line 45-224: The code blocks marked with ```bash and ```go in the
translated contributing.mdx contain localized inline comments and explanatory
text that must remain identical to the English source; locate the fenced blocks
(look for the triple-backtick markers ```bash and ```go and the sample commands
and Go example functions like ProcessData) and replace their internal content
with the original English code/comment text from the source locale so the fenced
code block content is not localized while leaving surrounding prose translated.
In `@docs/src/content/docs/ko/contributing/codebase-layout.mdx`:
- Around line 13-22: The fenced directory tree block has been translated into
Korean; restore the original English source exactly as in the upstream canonical
copy (the triple-backtick block starting with "wails/" and the lines for "v3/",
"v2/", "docs/", "website/", "scripts/", "mkdocs-website/", and "*.md") so the
code/tree block remains identical to the English source, and scan the file for
any other fenced code/tree blocks (notably the block covering lines 28-38) and
revert those to the original English text as well.
In `@docs/src/content/docs/ko/contributing/getting-started.mdx`:
- Around line 68-333: The code blocks in the MDX (fenced triple-backtick)
sections were translated and must remain exactly as the English source; revert
any translated shell/git examples (e.g., the blocks containing "git clone
https://github.com/YOUR_USERNAME/wails.git", "cd v3", "go build -o ../wails3
./cmd/wails3", "git checkout -b fix/issue-123-window-crash", etc.) back to their
original English content, leaving surrounding prose localized as needed, and
verify every fenced code block in this file matches the upstream English MDX
verbatim.
In `@docs/src/content/docs/ko/contributing/runtime-internals.mdx`:
- Around line 187-201: The inline comments in the C code block inside function
is_file_drag were translated to Korean; revert those comment strings back to
English so the snippet matches the original source language (replace the comment
after return TRUE with something like "external file drag" and the comment after
return FALSE with "internal HTML5 drag"), ensuring no other code changes are
made.
In `@docs/src/content/docs/ko/contributing/setup.mdx`:
- Around line 15-287: Several fenced code blocks (```bash, ```json, etc.) were
translated into Korean; restore their original verbatim English contents so
examples match the English source. Locate every fenced block (e.g., the shell
blocks showing go/node/npm commands, the VS Code settings JSON block, and
platform-specific install snippets) and replace the translated comments/lines
with the original English text from the canonical English docs, preserving
fences and formatting exactly (including `export GOPATH`, `go install ...`,
`node --version`, the JSON object for .vscode/settings.json, and the build/test
commands for v3).
In `@docs/src/content/docs/ko/contributing/standards.mdx`:
- Around line 45-456: The code blocks were translated to Korean; restore all
fenced code examples to their original English/source content (do not translate
code inside ```go```, ```typescript```, ```json```, ```bash``` blocks).
Specifically revert the translated examples such as the Closer/CloseInterface
types, error handling snippets (result, err := doSomething()), ValidationError
type, package application comment, NewApplication, (a *Application)
processEvent, (w *Window) setTitle/updateEverything, validate(), RunWithContext,
SafeCounter, startWorker, TestValidate table, the Prettier JSON, TypeScript
greet/process and WindowOptions/interface examples, and any other fenced code
blocks so the code text matches the original English examples exactly.
In `@docs/src/content/docs/ko/contributing/template-system.mdx`:
- Around line 22-201: The localized MDX has translated fenced code blocks that
must remain in English; restore every fenced snippet back to the original
English text (e.g., the directory tree block, the call chain block containing
"cmd/wails3/init.go", "internal/commands/init.go", "internal/templates.Load()",
"Template.CopyTo(dest)", the substitutions table examples, and any command
examples like "task --taskfile Taskfile.yml deps" and "wails3 init -n demo -t
qwik-ts") so code/command examples are exact matches to the English source while
keeping surrounding narrative translated.
- Around line 157-189: Fix the malformed command and tables: replace the en-dash
`–help` with the correct double-hyphen `--help` in the example `go run
./v3/cmd/wails3 --help`; then correct the broken markdown tables where `*`
bullet rows were inserted into table blocks by either converting those `*` lines
into proper pipe-delimited table rows (e.g., for the "작업 | 위치" table) or moving
them out of the table as regular list items (for entries like the DevPort note,
`.tmplignore`, and DevPort stdout hint). Update references to
`frontend/Taskfile.yml`, `DevPort`, `.tmplignore`, and
`internal/commands/init.go` as needed so the table structure and surrounding
lists are valid Markdown.
In `@docs/src/content/docs/ko/contributing/testing-ci.mdx`:
- Around line 24-209: Revert any translated text inside fenced code blocks back
to the original English verbatim: restore the tree block beginning with "v3/"
and its inline comments, the Go examples (e.g. "go test ./... -cover", the
TestColourParseHex snippet), Taskfile commands ("task test", "task integration",
"task ci"), the YAML Race Detector snippet (the - name: Race Detector / if:
matrix.os == 'ubuntu-latest' / run: go test -race ./...), and any build-tag
examples (e.g. "//go:build !windows"); ensure only the fenced blocks are changed
and keep the surrounding Korean prose as-is so the code/text matches the English
source exactly.
In `@docs/src/content/docs/ko/faq.mdx`:
- Around line 196-211: Revert any translated inline comments and section-label
text inside fenced code examples back to English so source-code parity is
preserved; specifically change the comment after window.Show() and any
comments/labels within the Go/JavaScript examples so they match the originals
(e.g., the snippet around window := app.Window.New(); window.Show(), and the
event examples using app.Event.Emit("my-event", data) and OnEvent("my-event",
handler)). Ensure no code-block text is localized in this MDX file.
In `@docs/src/content/docs/ko/features/bindings/advanced.mdx`:
- Around line 338-340: Restore the corrupted //wails:inject example by returning
the directive lines to plain comment lines inside the fenced Go block: remove
the spliced backticks and inline ``//wails:inject``, ensure the call to
InternalMethod("Hello " + arg + "!") appears as a commented example line
(//wails:inject await InternalMethod("Hello " + arg + "!");) and keep the Go
type declaration (type Service struct{}) and surrounding backticks intact so the
Go example is valid and copy-pastable.
In `@docs/src/content/docs/ko/features/bindings/best-practices.mdx`:
- Around line 19-41: The fenced Go code examples have been localized (Korean
labels/comments) but must remain identical to the original English examples;
restore the code fence contents to the original English text (e.g., revert
"AppService", its methods SaveFile/GetUser/SendEmail/ProcessPayment and the
comments "❌ Bad: God object" / "✅ Good: Focused services" and the
FileService/UserService/EmailService/PaymentService examples) so that every
fenced block matches the English source exactly; apply the same fix to the other
affected fenced blocks mentioned (lines 48-57, 64-71, 78-108, 118-136) ensuring
only the file's surrounding MDX translation remains localized while the code
fences are unchanged.
In `@docs/src/content/docs/ko/features/bindings/enums.mdx`:
- Around line 386-397: The final table row for "complex64, complex128" currently
contains a merged separator "`| 아니요 |---`" which breaks the Markdown table;
locate the row containing "complex64, complex128" and change it to end with just
"`| 아니요 |`", then place the horizontal rule "`---`" on its own line (optionally
with a blank line separating the table and the HR) so the table and the section
break are separate.
In `@docs/src/content/docs/ko/features/bindings/methods.mdx`:
- Line 408: 문서의 코드 펜스가 잘못 닫혀 있어 렌더링 오류가 발생합니다: 현재 종료 토큰 ```--- 를 찾아 이를 단순한 코드 펜스
종료 ``` 로 수정하고 구분선(---)은 코드 블록 바깥의 별도 줄로 이동해 분리하세요(대상 텍스트: the malformed closing
fence "```---" in docs/src/content/docs/ko/features/bindings/methods.mdx).
In `@docs/src/content/docs/ko/features/bindings/models.mdx`:
- Around line 317-379: Revert the localized Korean comments inside the fenced
JavaScript examples back to English by restoring original inline comments in the
code blocks that reference the bindings (e.g., User from
'./bindings/myapp/models' and service calls CreateUser, GetUser, UpdateUser from
'./bindings/myapp/userservice'); ensure code block contents remain identical to
source language (English) for all examples showing new User(),
User.createFrom(...), CreateUser(user), GetUser(1), and UpdateUser(user).
In `@docs/src/content/docs/ko/features/bindings/services.mdx`:
- Around line 14-594: The fenced Go code blocks have been translated into
Korean; revert every fenced code block back to the original English source
verbatim (do not change identifiers or formatting). Locate the code blocks by
the unique types and functions shown (e.g., GreetService / NewGreetService /
Greet, CalculatorService, CounterService, UserService / NewUserService / GetUser
/ ServiceStartup / ServiceShutdown, DatabaseService / NewDatabaseService /
periodicCleanup, NewEmailService, NotificationService, OrderService, and the
test functions like TestCalculatorService_Add and TestUserService_GetUser) and
replace each translated block's contents with the exact English text from the
canonical English docs so inline comments, strings and code remain unchanged.
In `@docs/src/content/docs/ko/features/browser/integration.mdx`:
- Around line 16-503: The fenced code blocks in this translation were localized
(comments and strings changed); revert every fenced code snippet back to the
original English source exactly (restore code blocks such as main, setupMenu,
openWithConfirmation, generateHTMLReport/generateAndOpenReport,
isValidURL/openSafeFile and all examples) so the code content matches the
English docs verbatim while leaving surrounding prose translated.
- Around line 168-171: The isValidURL function parameter shadows the standard
library url package, breaking url.Parse(url); rename the parameter (e.g., change
func isValidURL(url string) to func isValidURL(rawURL string)) and update the
body to call url.Parse(rawURL), or alternatively import the net/url package with
an alias and use that alias when calling Parse; update both English and Korean
snippets so the function name isValidURL uses the new parameter name
consistently.
In `@docs/src/content/docs/ko/features/clipboard/basics.mdx`:
- Around line 16-401: Several fenced code blocks in this MDX were translated
(comments and string literals) and must be reverted to the original English;
locate the code blocks containing symbols like app.Clipboard.SetText,
app.Clipboard.Text, ClipboardService.CopyToClipboard, copyWithFeedback,
pasteText, TextService.CopyText, DataService.PasteAndProcess, CopyAsJSON,
CopyAsCSV, ClipboardMonitor.checkClipboard, ClipboardHistory.Copy and
NewClipboardHistory and restore every comment, message string, and in-code text
inside those fenced blocks back to the original English wording (do not change
code logic), ensuring only the surrounding MDX prose remains translated.
In `@docs/src/content/docs/ko/features/dialogs/custom.mdx`:
- Around line 16-375: The code blocks in this MDX were translated (Korean) but
must remain identical to the source-language examples; revert all translated
inline comments and any altered code-text back to the original English text
inside every fenced code block (examples containing symbols like Customdialog,
NewCustomdialog, Show, Close, ShowModaldialog, Formdialog, NewFormdialog,
Submit, Cancel, ShowConfirmdialog, ShowInputdialog, Progressdialog,
NewProgressdialog, Logindialog, NewLogindialog, etc.) so the code fences match
the upstream source exactly.
In `@docs/src/content/docs/ko/features/dialogs/overview.mdx`:
- Around line 16-373: Several fenced code blocks were inadvertently translated
into Korean; revert those blocks to their original English content so code
examples remain exact (do not localize text inside fenced code). Locate the
translated blocks containing examples using identifiers like app.Dialog.Info(),
app.Dialog.Question(), app.Dialog.OpenFile(), app.Dialog.SaveFile(),
dialog.AddButton(), SetTitle(), SetMessage(), PromptForSingleSelection(),
PromptForMultipleSelection(), and the deleteFile/deleteFile() example, and
replace the translated comments/messages with their original English strings so
the code fences match the source-language examples exactly.
In `@docs/src/content/docs/ko/features/environment/info.mdx`:
- Around line 431-616: The fenced Go code block is not closed before the
admonitions: add a closing ``` fence immediately after the end of the Go code
(after the closing brace of toggleTheme) so the code block ends, then place the
:::tip[...] and :::danger[...] admonitions as separate Markdown blocks; locate
the functions toggleTheme, applyDarkTheme, applyLightTheme (and the final
closing brace) in the diff to find the proper spot to insert the ``` fence and
ensure the admonitions follow outside the code block.
In `@docs/src/content/docs/ko/features/events/system.mdx`:
- Around line 342-363: The last Pub/Sub example is cut off at the subscriber
marker; restore a complete subscriber example after the publisher code (e.g.,
show how to register a handler for "order-created" via app.Event.On or
equivalent), ensure the final code block closes properly, and move the visual
separator `---` out of the code fence so it appears as plain text between
sections; look for the OrderService.CreateOrder method and the
o.app.Event.Emit("order-created", order) call as the publisher, and replace the
incomplete `// 구독자---` region with a full subscriber snippet
(registering/unregistering a listener and handling the Order) followed by the
closing backticks and then the `---` divider.
In `@docs/src/content/docs/ko/features/keyboard/shortcuts.mdx`:
- Around line 16-429: Restore all fenced code blocks to the original English
source (do not localize comments or inline code). Revert changes inside the
```go``` blocks so symbols like application.New, app.KeyBinding.Add, main(),
openFile(), showKeyboardShortcuts(), window.EmitEvent(), and other code-level
identifiers are exactly as in the upstream English examples; ensure only
surrounding prose is translated while every fenced code block content is
identical to the repository's English originals.
In `@docs/src/content/docs/ko/features/menus/application.mdx`:
- Around line 34-497: Several fenced code blocks (e.g., the Go example starting
with "package main" and func main(), the snippets using app.NewMenu(),
app.Menu.Set(menu), UseApplicationMenu, createMenu(), rebuildFileMenu(), and
other code fences in the "메뉴 생성"/"동적 메뉴"/"메뉴에서 창 제어" sections) were translated;
revert those fenced code blocks to the original English source so code and
inline comments are identical to upstream (do not translate code or code
comments). Locate and replace each translated fenced block with the verbatim
English snippet from the upstream docs for the corresponding examples (package
main example, basic menu example, Set the application menu example,
createMenu/rebuildFileMenu functions, viewMenu examples, Tabs examples),
ensuring all code fences and in-code comments match the English originals
exactly.
- Around line 297-354: The MDX has merged tokens that break parsing—specifically
the combined fence+heading token "```## 사용자 정의 메뉴" and merged admonition
":::caution[...]..."—so split them onto separate lines: ensure triple backticks
are on their own lines surrounding code blocks (e.g., open with ``` then a
newline then the code, and close with ``` on its own line) and ensure any
admonition markers like ":::caution" start and end on their own lines with their
content between; locate the merged tokens "```## 사용자 정의 메뉴" and any ":::caution"
occurrences in the file and separate the fence/heading and admonition markers
accordingly.
In `@docs/src/content/docs/ko/features/menus/context.mdx`:
- Around line 333-340: The example mistakenly disables cutMenuItem twice: after
creating copyMenuItem you should call copyMenuItem.SetEnabled(false) instead of
cutMenuItem.SetEnabled(false); update the snippet where copyMenuItem is
initialized (the contextMenu.Add("Copy") block) to call
copyMenuItem.SetEnabled(false) and keep copyMenuItem.OnClick(handleCopy) as is
so the copy item is correctly disabled by default.
- Around line 27-623: The fenced code examples have been translated into Korean;
revert every fenced code block so the contents are identical to the original
English source (do not localize any code inside triple-backtick blocks).
Specifically restore the Go examples (e.g., the contextMenu :=
app.NewContextMenu(), createFileMenu/createImageMenu/createTextMenu,
parseFileData, handler stubs) and all HTML snippets (textarea and div examples
with --custom-contextmenu and --custom-contextmenu-data) back to their exact
English text from the source so code blocks remain verbatim.
In `@docs/src/content/docs/ko/features/menus/reference.mdx`:
- Line 359: The tail of the section was accidentally concatenated: split the
merged headings "**이것이 중요한 이유:**" and "**질문 있으신가요?**" and restore the missing
explanatory body for the "이것이 중요한 이유:" heading; add a short explanatory
paragraph describing why menus matter (e.g., purpose, top-level vs nested items,
keyboard/accessibility notes) under the "**이것이 중요한 이유:**" heading, then keep the
"**질문 있으신가요?**" heading followed by the existing Discord and example links
(Discord and 메뉴 예제) as separate content; ensure headings have proper Markdown
spacing/newlines so they render as distinct sections.
- Around line 20-357: Some fenced code blocks were translated into Korean;
restore all code block contents to the original English verbatim (do not
translate comments or strings inside the fenced Go examples). Locate the Go
snippets that call menu.Add, menu.AddCheckbox, menu.AddRadio, menu.AddSubmenu,
menu.Update, and OnClick and revert any translated comments/strings back to the
source English text so the fenced code remains identical to upstream examples;
leave surrounding prose translated if desired but ensure every fenced code block
content matches the original exactly.
In `@docs/src/content/docs/ko/features/menus/systray.mdx`:
- Around line 24-309: Some code fences in this MDX were translated; restore
every fenced code block to the original English source so code/content is
identical to upstream — specifically revert the Go examples (the package main
block including the //go:embed icon declaration and main(), the systray usage
snippets that call application.New, systray.SetIcon/SetDarkModeIcon,
menu.Add(...).OnClick, systray.AttachWindow(window), the updateTrayIcon()
function, and rebuildTrayMenu(status) function) back to the original English
text exactly as in the English docs; do not change any identifiers, comments, or
strings inside the ```go``` fences and ensure lines 322-355 code fence content
is restored too.
In `@docs/src/content/docs/ko/features/notifications/overview.mdx`:
- Around line 73-107: Revert the translated Korean text inside the code fences
back to the original English code exactly as in the source: restore identifier
and string literals such as categoryID, notifications.NotificationCategory,
NotificationAction entries ("OPEN", "ARCHIVE", Title values), HasReplyField,
ReplyPlaceholder, ReplyButtonTitle, notifier.RegisterNotificationCategory,
notifier.SendNotificationWithActions and notifications.NotificationOptions to
their original English forms; do the same for the other affected code blocks
(lines called out: 113-129, 137-149, 252-304) so the MDX code blocks match the
English source exactly.
- Around line 234-244: The markdown table has a stray separator sequence that
broke the row around the API list; remove the malformed fragment and ensure each
API entry is a separate table row (e.g. `RegisterNotificationCategory`,
`RemoveNotificationCategory`, `RemoveAllPendingNotifications`,
`RemovePendingNotification`, `RemoveAllDeliveredNotifications`,
`RemoveDeliveredNotification`, `RemoveNotification`) so the table columns remain
aligned and render correctly by splitting the combined/broken line into
individual `| method | description |` rows corresponding to the existing
function names.
In `@docs/src/content/docs/ko/features/platform/dock.mdx`:
- Around line 23-36: The fenced Go code blocks have been translated into Korean
but must match the original English source exactly; revert the translated
comments and any altered code text in the affected MDX snippets (e.g., the block
using dock.New(), application.New(application.Options{...}), and
application.NewService(dockService)) back to the original English wording so the
code inside fenced ```go blocks is identical to the English docs across locales;
update all listed ranges and any other fenced go blocks in this file to the
English source comments and code.
In `@docs/src/content/docs/ko/features/screens/info.mdx`:
- Around line 16-335: Several fenced Go code blocks in this MDX (examples
include the Screen struct, centreOnScreen, moveToScreen,
positionTopLeft/positionTopRight/positionBottomRight,
MultiMonitorManager.CreateWindowOnScreen, and ScreenMonitor.checkScreens) have
been translated into Korean; revert each code block's contents back to the
original English source so code, comments, and string literals exactly match the
source-language MDX. Locate each fenced ```go``` block (e.g., the examples
around Screen struct, window positioning helper functions, multi-monitor manager
methods, and screen monitor) and restore original English comments and printed
strings without altering code structure or formatting; ensure no inline
translations remain inside any fenced code block.
- Around line 18-73: The documentation uses the wrong API field name: replace
occurrences of app.Screens with the singular app.Screen so the calls match the
Wails v3 API (e.g., change app.Screens.GetPrimary() to app.Screen.GetPrimary(),
app.Screens.GetCurrent(window) to app.Screen.GetCurrent(window),
app.Screens.GetByID(...) to app.Screen.GetByID(...), and similarly ensure
examples using GetAll() call app.Screen.GetAll()); update all examples that
reference app.Screens to app.Screen for consistency with the actual methods
GetAll, GetPrimary, GetCurrent, and GetByID.
In `@docs/src/content/docs/ko/features/windows/basics.mdx`:
- Around line 16-403: Several fenced code blocks (Go examples creating and
manipulating windows using application.New, app.Window.New(),
app.Window.NewWithOptions, methods like SetTitle, SetSize, Center, Show, Run,
SetBackgroundColour, SetAlwaysOnTop, SetResizable, Close, Destroy, OnClose,
OnDestroy, Flash, SnapAssist, SetIcon, and event usage like
app.Event.Emit/app.Event.On) have been translated into Korean; revert those
fenced code blocks back to the original English source exactly as in the English
docs so code content matches upstream. Locate each fenced block in this file
(the top package main example and all subsequent ```go blocks shown) and replace
the translated/modified snippets with the original English examples from the
canonical English docs, preserving language, formatting, and code text verbatim.
Ensure no changes are made to code fences themselves—only restore the code
content to the English source.
In `@docs/src/content/docs/ko/features/windows/events.mdx`:
- Around line 400-422: The example was truncated at the ManagedWindow
declaration: restore the missing parts of the ManagedWindow struct and its
methods (e.g., ensure ManagedWindow contains app *application.Application and
any fields/methods used later such as SaveState/LoadState or Show/Hide if
referenced), remove the stray '---' from inside the code block (it should be
outside as the separator in the doc), and close the Go code block (add the
missing closing brace(s) for the struct/functions and the final ``` marker).
Specifically, complete the ManagedWindow definition and any referenced functions
(e.g., constructors or main()) so the example compiles and the code block is
properly terminated.
In `@docs/src/content/docs/ko/features/windows/frameless.mdx`:
- Around line 16-770: The code examples in this file have been translated into
Korean but must match the original English exactly; restore every code fence
content to the original English examples (e.g. Go snippets using
application.WebviewWindowOptions and NewWithOptions, the WindowControls struct
and its Minimise/Maximise/Close methods, JavaScript using
Window.Minimise/Window.Maximise/Window.Close and updateMaximiseButton, CSS using
--wails-draggable and --wails-resize, HTML titlebar examples, and the full
Go/HTML/CSS/JS full example blocks) so that all code blocks (everything inside
```go, ```css, ```html, ```javascript etc.) are identical to the English source.
In `@docs/src/content/docs/ko/features/windows/multiple.mdx`:
- Around line 604-606: The closing code delimiter and the horizontal rule are
concatenated as "}---" which breaks rendering; edit the document around the end
of the code block (the line containing "}---") so that the closing brace "}"
(end of the code block) and the horizontal rule "---" are on separate lines:
place "}" by itself to close the code block (or ensure the fenced code block
terminator is correct) and then add a blank line followed by "---" on its own
line before the following paragraph that begins "**질문 있으신가요?**".
In `@docs/src/content/docs/ko/feedback.mdx`:
- Line 19: Update the command example string "wails doctor" to "wails3 doctor"
in the feedback page content so that the v3 docs consistently reference the v3
CLI; locate the occurrence of the literal "wails doctor" in the file and replace
it with "wails3 doctor" (and apply the same change in the corresponding English
feedback page as noted).
In `@docs/src/content/docs/ko/getting-started/your-first-app.mdx`:
- Around line 232-233: The admonition start token ":::tip[Pro Tip]" is currently
appended to the previous sentence and won't render as an admonition; move the
token to its own line (separate paragraph) so the directive is recognized—i.e.,
ensure the line contains only ":::tip[Pro Tip]" followed by the admonition
content and closing token, adjusting the surrounding text so the sentence ends
before the admonition line.
- Around line 192-199: The fenced shell code block containing the commands
"wails3 package" and the "wails3 task linux:create:..." lines currently has
translated inline comments; revert those inline comments so the block content
exactly matches the English source (i.e., restore the original inline comments
like "# AppImage format", "# Debian package", "# Red Hat package", "# Arch Linux
package" or remove translated comments entirely), ensuring the fenced code block
text for the commands and comments is identical to the English source.
In `@docs/src/content/docs/ko/guides/architecture.mdx`:
- Around line 29-175: Several fenced Go code examples contain Korean
comments/labels that must be reverted to the original English text; update the
code blocks so comments and identifiers match the source-language docs exactly
(e.g., restore English for the service interface and implementation comments
around UserService, userService, NewUserService; the repository section
including UserRepository; the EventBus type and its Subscribe/Publish methods;
the App manual DI example with App, NewApp; the Wire example with InitializeApp;
and the AppState with SetUser/GetUser). Locate those fenced code blocks in the
MDX and replace the localized Korean comments/words with the original English
comments/labels while leaving all Go identifiers and code structure unchanged.
In `@docs/src/content/docs/ko/guides/build/building.mdx`:
- Around line 27-31: Revert the localized Korean text inside the fenced code
samples back to the original English so the code block bytes match the source;
specifically replace the Korean comments that read "아키텍처 지정" and "환경 변수 스타일도 사용
가능" with the original English headings/comments and ensure lines showing example
commands (e.g., "wails3 build GOOS=darwin GOARCH=arm64" and "GOOS=windows wails3
build") are left unchanged; also audit and revert the same translations in the
other affected code blocks referenced (lines 51-55, 79-87, 96-109) so all fenced
code blocks remain byte-equivalent to the English MDX source.
---
Minor comments:
In `@docs/src/content/docs/ko/community/links.md`:
- Line 21: The link text "[Github Issues]" uses incorrect capitalization; update
the markdown link label to "GitHub Issues" (i.e., change the link text in the
entry currently written as [Github
Issues](https://github.com/wailsapp/wails/issues) to [GitHub
Issues](https://github.com/wailsapp/wails/issues)) so the official "GitHub"
capitalization is used everywhere.
In `@docs/src/content/docs/ko/contributing/codebase-layout.mdx`:
- Line 78: Update the CLI command examples to use the v3 prefix by replacing any
occurrence of "wails init -t <framework>" with "wails3 init -t <framework>" in
the documentation; look for the exact string "wails init -t <framework>" (e.g.,
near the packager list item) and update it so all examples and instructions
consistently use "wails3 init -t <framework>".
In `@docs/src/content/docs/ko/contributing/index.mdx`:
- Line 78: Update the CLI example string in the "템플릿 시스템" entry: replace the
incorrect `wails init -t <framework>` command with the v3-prefixed `wails3 init
-t <framework>` so all Wails v3 docs consistently use the `wails3` prefix;
locate the sentence containing the `템플릿 시스템` table row and change the command
text accordingly.
In `@docs/src/content/docs/ko/contributing/standards.mdx`:
- Around line 439-443: The example build-tag line is malformed: replace the
single incorrect token "//go:build darwinpackage application" with two separate
build-tag lines so the Go build tags are valid; locate the occurrence of the
string "//go:build darwinpackage application" and split it into two lines such
as "//go:build darwin" and "//go:build application" (ensuring each build tag
appears on its own line in the example).
In `@docs/src/content/docs/ko/contributing/testing-ci.mdx`:
- Around line 3-16: The term "경동" is non-standard—replace all occurrences (e.g.,
the table row label "경동 감지" and the descriptive phrase "런타임 및 브리지의 데이터 경동 포착")
with a single consistent term such as "데이터 레이스 감지" (or alternatively "경쟁 상태 감지")
and update the adjacent examples (`go test -race`, `wails3 dev -race`) to match
the chosen wording so the heading and description remain consistent.
In `@docs/src/content/docs/ko/features/bindings/models.mdx`:
- Line 454: The markdown line "## 고급 패턴---" combines a level-2 heading and a
horizontal rule; split it into two lines by making the heading "## 고급 패턴" and
placing the horizontal rule on the following line as "---" so the heading and
divider render separately in models.mdx.
In `@docs/src/content/docs/ko/features/bindings/services.mdx`:
- Line 613: Remove the trailing markdown artifact " ---" from the sentence
containing "서비스는 공유됨---" so it reads "서비스는 공유됨"; locate and edit the paragraph
in docs/src/content/docs/ko/features/bindings/services.mdx where that exact
string appears and delete the dangling hyphens to prevent malformed rendering.
In `@docs/src/content/docs/ko/features/clipboard/basics.mdx`:
- Line 407: Remove the trailing markdown rule markers by editing the bullet line
that currently reads "**반환값 확인** - 실패를 우아하게 처리하세요---" and delete the trailing
'---' so the rendered bullet ends cleanly (e.g., "**반환값 확인** - 실패를 우아하게 처리하세요").
Ensure no extra markdown rule markers remain adjacent to the bullet text.
In `@docs/src/content/docs/ko/features/keyboard/shortcuts.mdx`:
- Around line 14-23: Update the prose to match the actual API name used in the
example: change references to `KeyBindings` to `KeyBinding` so the text
consistently refers to app.KeyBinding; ensure any explanatory sentence
mentioning the manager uses the exact identifier `KeyBinding` to avoid confusion
with `KeyBindings`.
In `@docs/src/content/docs/ko/features/windows/frameless.mdx`:
- Line 787: Remove the trailing residual markup by editing the bullet line that
reads "버튼에 no-drag를 잊지 마세요" and delete the ending '---' so the line becomes a
normal bullet text without the stray dashes; locate the exact string "버튼에
no-drag를 잊지 마세요---" and replace it with "버튼에 no-drag를 잊지 마세요".
In `@docs/src/content/docs/ko/features/windows/options.mdx`:
- Around line 220-224: The second bullet in the list under "사용 사례:" is missing a
leading "-" marker; update the list so each item uses the same markdown list
prefix (add "-" before "과도한 리소스 사용 방지") so the three items ("- 고정 크기 애플리케이션", "-
과도한 리소스 사용 방지", "- 디자인 제약 유지") are consistently rendered.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: dbb02f5b-bc9d-4c8f-bb3d-64a732085cd5
📒 Files selected for processing (103)
docs/.translation-cache/ko.jsondocs/src/content/docs/ko/community/links.mddocs/src/content/docs/ko/community/templates.mddocs/src/content/docs/ko/concepts/architecture.mdxdocs/src/content/docs/ko/concepts/bridge.mdxdocs/src/content/docs/ko/concepts/build-system.mdxdocs/src/content/docs/ko/concepts/lifecycle.mdxdocs/src/content/docs/ko/concepts/manager-api.mdxdocs/src/content/docs/ko/contributing.mdxdocs/src/content/docs/ko/contributing/architecture.mdxdocs/src/content/docs/ko/contributing/architecture/bindings.mdxdocs/src/content/docs/ko/contributing/asset-server.mdxdocs/src/content/docs/ko/contributing/binding-system.mdxdocs/src/content/docs/ko/contributing/build-packaging.mdxdocs/src/content/docs/ko/contributing/codebase-layout.mdxdocs/src/content/docs/ko/contributing/extending-wails.mdxdocs/src/content/docs/ko/contributing/getting-started.mdxdocs/src/content/docs/ko/contributing/index.mdxdocs/src/content/docs/ko/contributing/runtime-internals.mdxdocs/src/content/docs/ko/contributing/setup.mdxdocs/src/content/docs/ko/contributing/standards.mdxdocs/src/content/docs/ko/contributing/template-system.mdxdocs/src/content/docs/ko/contributing/testing-ci.mdxdocs/src/content/docs/ko/credits.mdxdocs/src/content/docs/ko/faq.mdxdocs/src/content/docs/ko/features/bindings/advanced.mdxdocs/src/content/docs/ko/features/bindings/best-practices.mdxdocs/src/content/docs/ko/features/bindings/enums.mdxdocs/src/content/docs/ko/features/bindings/methods.mdxdocs/src/content/docs/ko/features/bindings/models.mdxdocs/src/content/docs/ko/features/bindings/services.mdxdocs/src/content/docs/ko/features/browser/integration.mdxdocs/src/content/docs/ko/features/clipboard/basics.mdxdocs/src/content/docs/ko/features/dialogs/custom.mdxdocs/src/content/docs/ko/features/dialogs/file.mdxdocs/src/content/docs/ko/features/dialogs/message.mdxdocs/src/content/docs/ko/features/dialogs/overview.mdxdocs/src/content/docs/ko/features/drag-and-drop/files.mdxdocs/src/content/docs/ko/features/drag-and-drop/html.mdxdocs/src/content/docs/ko/features/environment/info.mdxdocs/src/content/docs/ko/features/events/system.mdxdocs/src/content/docs/ko/features/keyboard/shortcuts.mdxdocs/src/content/docs/ko/features/menus/application.mdxdocs/src/content/docs/ko/features/menus/context.mdxdocs/src/content/docs/ko/features/menus/reference.mdxdocs/src/content/docs/ko/features/menus/systray.mdxdocs/src/content/docs/ko/features/notifications/overview.mdxdocs/src/content/docs/ko/features/platform/dock.mdxdocs/src/content/docs/ko/features/screens/info.mdxdocs/src/content/docs/ko/features/windows/basics.mdxdocs/src/content/docs/ko/features/windows/events.mdxdocs/src/content/docs/ko/features/windows/frameless.mdxdocs/src/content/docs/ko/features/windows/multiple.mdxdocs/src/content/docs/ko/features/windows/options.mdxdocs/src/content/docs/ko/feedback.mdxdocs/src/content/docs/ko/getting-started/your-first-app.mdxdocs/src/content/docs/ko/guides/architecture.mdxdocs/src/content/docs/ko/guides/build/building.mdxdocs/src/content/docs/ko/guides/build/cross-platform.mdxdocs/src/content/docs/ko/guides/build/customization.mdxdocs/src/content/docs/ko/guides/build/linux.mdxdocs/src/content/docs/ko/guides/build/macos.mdxdocs/src/content/docs/ko/guides/build/signing.mdxdocs/src/content/docs/ko/guides/build/windows.mdxdocs/src/content/docs/ko/guides/cli.mdxdocs/src/content/docs/ko/guides/custom-templates.mdxdocs/src/content/docs/ko/guides/custom-transport.mdxdocs/src/content/docs/ko/guides/customising-windows.mdxdocs/src/content/docs/ko/guides/distribution/auto-updates.mdxdocs/src/content/docs/ko/guides/distribution/custom-protocols.mdxdocs/src/content/docs/ko/guides/e2e-testing.mdxdocs/src/content/docs/ko/guides/events-reference.mdxdocs/src/content/docs/ko/guides/file-associations.mdxdocs/src/content/docs/ko/guides/gin-routing.mdxdocs/src/content/docs/ko/guides/gin-services.mdxdocs/src/content/docs/ko/guides/installers.mdxdocs/src/content/docs/ko/guides/menus.mdxdocs/src/content/docs/ko/guides/panic-handling.mdxdocs/src/content/docs/ko/guides/performance.mdxdocs/src/content/docs/ko/guides/raw-messages.mdxdocs/src/content/docs/ko/guides/routing.mdxdocs/src/content/docs/ko/guides/security.mdxdocs/src/content/docs/ko/guides/server-build.mdxdocs/src/content/docs/ko/guides/single-instance.mdxdocs/src/content/docs/ko/guides/testing.mdxdocs/src/content/docs/ko/guides/windows-uac.mdxdocs/src/content/docs/ko/migration/v2-to-v3.mdxdocs/src/content/docs/ko/quick-start/first-app.mdxdocs/src/content/docs/ko/quick-start/installation.mdxdocs/src/content/docs/ko/reference/application.mdxdocs/src/content/docs/ko/reference/cli.mdxdocs/src/content/docs/ko/reference/dialogs.mdxdocs/src/content/docs/ko/reference/events.mdxdocs/src/content/docs/ko/reference/frontend-runtime.mdxdocs/src/content/docs/ko/reference/menu.mdxdocs/src/content/docs/ko/reference/overview.mdxdocs/src/content/docs/ko/reference/updater.mdxdocs/src/content/docs/ko/reference/window.mdxdocs/src/content/docs/ko/troubleshooting/mac-syso.mdxdocs/src/content/docs/ko/tutorials/01-creating-a-service.mdxdocs/src/content/docs/ko/tutorials/02-todo-vanilla.mdxdocs/src/content/docs/ko/tutorials/03-notes-vanilla.mdxdocs/src/content/docs/ko/tutorials/overview.mdx
Comment on lines
+285
to
+328
| ```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 레퍼런스](/ko/reference/overview)를 확인하세요. No newline at end of file |
Contributor
There was a problem hiding this comment.
Critical: lifecycle D2 diagram block is cut off.
The block terminates mid-node at Save: "Save State" {--- with missing closing braces/fence. This will break document parsing/rendering. Please restore the full diagram and close the fenced block before the final paragraph.
🤖 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/ko/concepts/architecture.mdx` around lines 285 - 328,
The D2 diagram block is truncated at the node "Save: \"Save State\" {---",
breaking parsing; restore the missing closing braces and the closing
triple-backtick fence so the diagram is complete (ensure every opened block such
as Start, Init, Create, Register, Setup, Run, Events, Messages, Render,
Shutdown, Cleanup, and Save has matching closing braces) and place the closing
``` fence immediately before the final paragraph that begins "**아키텍처에 대해 질문이
있으신가요?**" so the text after the diagram is outside the fenced diagram block.
Comment on lines
+389
to
+391
| Name: "Alice",--- | ||
|
|
||
| **브리지 관련 질문이 있으신가요?** [Discord](https://discord.gg/JDdSxwjhGf)에서 질문하거나 [바인딩 예제](https://github.com/wailsapp/wails/tree/master/v3/examples/binding)를 확인하세요. No newline at end of file |
Contributor
There was a problem hiding this comment.
Corrupted code block tail likely breaks MDX
Line 389 includes --- inside the snippet (Name: "Alice",---) and the block appears truncated immediately afterward. Please restore the full original fenced block and close it cleanly.
🤖 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/ko/concepts/bridge.mdx` around lines 389 - 391, The MDX
code block tail is corrupted by the stray '---' in the snippet containing `Name:
"Alice",---`; locate the snippet that includes that exact string and restore the
full original fenced code block content (remove the stray '---' artifact),
ensure the block is properly terminated with the matching fence (triple
backticks or proper MDX block delimiter), and verify the block's contents are
intact and not truncated (references: the snippet containing `Name:
"Alice",---`).
Comment on lines
+315
to
+320
| // 연결 닫기----------|--------------------------------| | ||
| | macOS | 앱이 실행 상태 유지(메뉴 막대 유지) | | ||
| | Windows | 앱 종료 | | ||
| | Linux | 앱 종료 | | ||
|
|
||
| macOS는 창이 없어도 메뉴 막대에 애플리케이션이 활성 상태로 남아 있는 네이티브 플랫폼 관례를 따릅니다. Windows와 Linux는 기본적으로 종료됩니다. |
Contributor
There was a problem hiding this comment.
Section contains merged markdown/code that breaks structure.
OnShutdown example is interrupted by table rows at Line 315 onward, and another paragraph is concatenated at Line 367 after code. This will break rendering and likely MDX parsing.
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/ko/concepts/lifecycle.mdx` around lines 315 - 320, The
OnShutdown example in the "OnShutdown" section has its fenced code block
interrupted by table rows and a concatenated paragraph; fix it by closing the
MDX/markdown code fence for the OnShutdown example before the table (and ensure
there is a blank line after the closing fence), move the platform table out of
the code block into normal markdown, and ensure the subsequent paragraph is
separated by a blank line from the table so the MDX parses correctly; locate the
broken example by searching for the "OnShutdown" header and the surrounding
fenced code block in the file.
| * 루트 `Taskfile.yml` 작업 파일은 두 가지 환경 변수를 주입합니다: | ||
| `APP_NAME` 및 `WAILS_VITE_PORT`. | ||
| * 각 템플릿별 Taskfile은 개발 서버를 실행하기 전에 이러한 변수를 내보냅니다. | ||
| * `assetserver_dev.go` 는 단순히 해당 대상为目标으로 프록시합니다. |
Contributor
There was a problem hiding this comment.
Remove Chinese character from Korean text.
Line 75 contains a Chinese character 为 that should be Korean:
-* `assetserver_dev.go` 는 단순히 해당 대상为目标으로 프록시합니다.
+* `assetserver_dev.go` 는 단순히 해당 대상으로 프록시합니다.The phrase 为目标 appears to be a machine translation artifact. The corrected Korean sentence reads more naturally without it, or should use the Korean equivalent 대상으로 (which is already present).
📝 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.
Suggested change
| * `assetserver_dev.go` 는 단순히 해당 대상为目标으로 프록시합니다. | |
| * `assetserver_dev.go` 는 단순히 해당 대상으로 프록시합니다. |
🤖 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/ko/contributing/asset-server.mdx` at line 75, Remove
the stray Chinese character '为' from the Korean sentence mentioning
`assetserver_dev.go` so the phrase reads naturally (e.g., "assetserver_dev.go 는
단순히 해당 대상으로 프록시합니다.")—edit the line in
docs/src/content/docs/ko/contributing/asset-server.mdx to delete the '为'
character or replace the machine-translated fragment with the correct Korean
equivalent `대상으로`.
Comment on lines
+331
to
+334
| ```bash | ||
| git push origin docs/improve-window-api-examples | ||
| ```PR에서 다음 내용을 명시하세요: | ||
| - 어떤 문서를 개선했는지 |
Contributor
There was a problem hiding this comment.
Repair broken code fence around PR submission section.
Line 333 starts with ```PR... on the same line, which breaks markdown fence structure and can corrupt rendering for the remainder of the section.
Suggested minimal fix
- ```PR에서 다음 내용을 명시하세요:
+ ```
+ 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/ko/contributing/getting-started.mdx` around lines 331 -
334, The markdown fence is broken because the sequence "```PR에서..." merges the
code fence and text; locate the PR submission section containing the malformed
fence (the line that begins with "```PR...") and split it so the triple
backticks are on their own line to open/close the code block and the PR
instruction text is plain text outside the fence; ensure you add a closing
triple backtick after the example command and that the PR instructions (e.g.,
"PR에서 다음 내용을 명시하세요:" and the list item "어떤 문서를 개선했는지") are rendered as normal
text following the fenced block.
Comment on lines
+310
to
+314
| ```----------|--------|--------|-------| | ||
| | **Windows** | ✅ | ✅ | 완전히 작동 - 아이콘이 알림 영역에 나타나거나 사라짐 | | ||
| | **macOS** | ✅ | ✅ | 메뉴 바 항목이 표시되거나 숨겨짐 | | ||
| | **Linux** | ✅ | ✅ | 데스크톱 환경에 따라 다름 | | ||
|
|
Contributor
There was a problem hiding this comment.
Fix corrupted markdown blocks around platform/troubleshooting sections.
There are merged table-separator fragments and trailing --- concatenated into list text, which will render incorrectly and can break surrounding section structure.
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/ko/features/menus/systray.mdx` around lines 310 - 314,
The markdown has a corrupted table/markdown fence near the
platform/troubleshooting sections: remove the stray/merged separator fragments
(e.g. the "```----------|--------|..." and concatenated '---' pieces), restore a
valid Markdown table header/separator row (use proper pipe-delimited header and
a matching "| --- | --- | --- | --- |" separator), ensure any triple-backtick
fences are balanced or removed, and fix the trailing '---' that got appended
into list text; apply the same cleanup to the other occurrence referenced (lines
~386-388) so the platform and troubleshooting sections render correctly.
Comment on lines
+339
to
+343
| ```go | ||
| func createDPIAwareWindow(screen *Screen) *application.WebviewWindow { | ||
| // 1.0 스케일 기준 기본 크기--- | ||
|
|
||
| **질문 있으신가요?** [Discord](https://discord.gg/JDdSxwjhGf)에서 질문하거나 [화면 예제](https://github.com/wailsapp/wails/tree/master/v3/examples)를 확인하세요. No newline at end of file |
Contributor
There was a problem hiding this comment.
Malformed fenced code block breaks this page
The go fence opened at Line 339 is not properly closed, and markdown prose is embedded inside it. This can break MDX parsing/rendering.
Proposed fix
```go
func createDPIAwareWindow(screen *Screen) *application.WebviewWindow {
- // 1.0 스케일 기준 기본 크기---
+ // ...
}
+```
-**질문 있으신가요?** [Discord](https://discord.gg/JDdSxwjhGf)에서 질문하거나 [화면 예제](https://github.com/wailsapp/wails/tree/master/v3/examples)를 확인하세요.
+**질문 있으신가요?** [Discord](https://discord.gg/JDdSxwjhGf)에서 질문하거나 [화면 예제](https://github.com/wailsapp/wails/tree/master/v3/examples)를 확인하세요.🤖 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/ko/features/screens/info.mdx` around lines 339 - 343,
The MDX page has an unclosed Go fenced code block starting at the function
createDPIAwareWindow which causes prose to be rendered inside the code fence;
fix by closing the```go fenced block after the function body (e.g., ensure the
block contains only the Go code for func createDPIAwareWindow(screen *Screen)
*application.WebviewWindow { ... } and add the closing ```), and move the
following Korean prose ("질문 있으신가요? ...") back outside the code fence so the
markdown/MDX parses correctly.
Comment on lines
+411
to
+417
| <TabItem label="macOS" icon="apple"> | ||
| **macOS 전용 기능:** | ||
|
|
||
| ```go | ||
| // Transparent title bar--- | ||
|
|
||
| **질문이 있으신가요?** [Discord](https://discord.gg/JDdSxwjhGf)에서 질문하거나 [창 예제](https://github.com/wailsapp/wails/tree/master/v3/examples)를 확인하세요. No newline at end of file |
Contributor
There was a problem hiding this comment.
MDX content is truncated and structurally broken at the end.
The macOS tab starts a Go fence at Line 414 and then abruptly terminates, with missing closing code fence and missing closing tab/container structure. This is a docs build/render blocker.
🤖 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/ko/features/windows/basics.mdx` around lines 411 - 417,
The macOS TabItem (label="macOS") in
docs/src/content/docs/ko/features/windows/basics.mdx opens a Go code fence but
the file ends abruptly, breaking MDX structure; fix it by closing the opened Go
fence (add the missing ```), then close the TabItem container (</TabItem>) and
any surrounding Tabs/TabGroup container that was opened earlier so the tab
structure is balanced; ensure the closing tokens are placed immediately after
the intended macOS code/example and that the TabItem label="macOS" block is
properly terminated.
| **플랫폼:** 전체 | ||
|
|
||
| ```go | ||
| BackgroundColour: application.RGBA{R: 0, G: 0, H: 0, A: 255}, |
Contributor
There was a problem hiding this comment.
Fix typo in RGBA struct field.
The RGBA struct uses R, G, B, A fields (Red, Green, Blue, Alpha), but line 421 incorrectly uses H instead of B:
-BackgroundColour: application.RGBA{R: 0, G: 0, H: 0, A: 255},
+BackgroundColour: application.RGBA{R: 0, G: 0, B: 0, A: 255},This would cause a compilation error.
📝 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.
Suggested change
| BackgroundColour: application.RGBA{R: 0, G: 0, H: 0, A: 255}, | |
| BackgroundColour: application.RGBA{R: 0, G: 0, B: 0, A: 255}, |
🤖 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/ko/features/windows/options.mdx` at line 421, In the
BackgroundColour initialization using application.RGBA (the struct with fields
R, G, B, A) replace the incorrect field name H with B so the struct literal uses
R, G, B, A; locate the BackgroundColour: application.RGBA{R: 0, G: 0, H: 0, A:
255} entry and change the H field to B to match the RGBA struct fields.
Comment on lines
+1000
to
+1002
| ```--- | ||
|
|
||
| **질문 있으신가요?** [Discord](https://discord.gg/JDdSxwjhGf)에서 문의하거나 [예제](https://github.com/wailsapp/wails/tree/master/v3/examples)를 확인하세요. No newline at end of file |
Contributor
There was a problem hiding this comment.
Fix malformed document closing.
Line 1000 has a malformed code fence marker. It should be just the closing --- for the MDX frontmatter section:
-```---
+---
**질문 있으신가요?** [Discord](https://discord.gg/JDdSxwjhGf)에서 문의하거나 [예제](https://github.com/wailsapp/wails/tree/master/v3/examples)를 확인하세요.The ```go part appears to be a copy-paste error.
🤖 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/ko/features/windows/options.mdx` around lines 1000 -
1002, Replace the malformed frontmatter/code-fence markers in the MDX: locate
the stray "```---" and any accidental "```go" lines in the document (near the
closing frontmatter around the block with "질문 있으신가요?") and change them so the
frontmatter is closed with a single line containing only "---"; remove the
extraneous backtick fences to ensure a proper MDX frontmatter close.
Collaborator
|
Reviewed the translations in this PR (ko — Korean). Spot-checked
No broken MDX syntax or structural issues found. LGTM — ready to merge. Note: Taliesin is an AI agent. CC @leaanthony |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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/dialogs/custom.mdx— Code block count mismatch (src=14, tgt=10), Import count mismatch (src=3, tgt=2)features/events/system.mdx— Code block count mismatch (src=30, tgt=23), Import count mismatch (src=8, tgt=6)features/menus/application.mdx— Code block count mismatch (src=19, tgt=18), Import count mismatch (src=3, tgt=2)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=16), 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)tutorials/01-creating-a-service.mdx— Code block count mismatch (src=15, tgt=16), Import count mismatch (src=3, tgt=6)Locales: ko
Files: 102 new translations
CC @leaanthony
Summary by CodeRabbit
Release Notes