一键在 Manus 中运行任何 Skill

localization

星标0

分支0

更新时间2026年7月11日 01:22

Add or change user-visible text in ClamAV UI — Lang.cs keys, English+Ukrainian translations, ApplyLanguage re-texting. Use whenever any UI label, button, log line, tray balloon, status message, or dialog string is added or edited.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

alexbeatnik

alexbeatnik/ClamAV-WindowsUI

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Adding / changing user-visible strings

Every user-visible string goes through Lang.T("key") — never hardcode text in the UI, logs, tray balloons, or dialogs.

Steps

Add the key in src/Lang.cs inside the static constructor, grouped with related keys (the file is organized by feature area — find the nearest comment banner):
```
A("settings.schedule", "Scheduled quick scan:", "Плановий швидкий скан:");
```
A(key, english, ukrainian) — both languages, always. English is the default; Ukrainian is the alternative. Missing Ukrainian silently falls back to English, which is a bug, not a feature.
Persistent controls (created once in BuildUi/Build*Page and kept alive) must also be re-texted in ApplyLanguage() in src/MainForm.Ui.cs — otherwise the language switch leaves them stale. Selector buttons with ●/○ markers have their own Update*Buttons() helper that ApplyLanguage() calls (see UpdatePerfButtons, UpdateSchedButtons).
Dialogs and MessageBoxes need nothing extra — they are built fresh each time they open and pick up the current language automatically.

Gotchas

Format placeholders ({0}, {1:0}…) must match the string.Format call site in both translations — tests/LangTests.cs has a test that cross-checks placeholders between En and Uk; it will fail the build if they diverge.
Log lines that end paragraphs carry their own \r\n inside the string — match the neighbors.
ToolStripMenuItem treats & as a mnemonic marker: when reusing a string in a menu, escape it (Lang.T(...).Replace("&", "&&")).
Key naming convention: area.name — btn.*, settings.*, status.*, log.*, tray.*, hero.*, msg.*, sstat.*/sval.* (settings STATUS block), col.* (list columns), title.*, err.*.
Sources are UTF-8 (/codepage:65001); Ukrainian literals are normal — don't escape them.

同仓库更多 Skills

同仓库

release

alexbeatnik/ClamAV-WindowsUI

Version bumps and releases of ClamAV UI — AssemblyInfo.cs, the release.yml workflow, vX.Y.Z branch flow, and the self-update constraints a release must respect. Use when bumping the version, preparing a release, or changing anything about update/release plumbing.

2026-07-180

screenshots

alexbeatnik/ClamAV-WindowsUI

Retake the four README screenshots (dashboard, logs, quarantine, settings) by driving the running ClamAV UI app through UI Automation. Use when asked for new/updated README screenshots or to capture the app's pages.

2026-07-180

verify

alexbeatnik/ClamAV-WindowsUI

Launch and manually verify ClamAV UI after a change — single-instance/tray behavior, what to click through, and the Windows Defender/EICAR gotcha. Use after building when a change needs to be seen working in the real app.

2026-07-110

settings-key

alexbeatnik/ClamAV-WindowsUI

Add a persisted option to ClamAV UI — a settings.ini key with LoadSettings/SaveSettings wiring, migration for old settings files, and a control on the Settings page (absolute-positioned card layout). Use when adding a toggle, selector, or any state that must survive restarts.

2026-07-110

testing

alexbeatnik/ClamAV-WindowsUI

Add or run unit tests for ClamAV UI — the zero-dependency runner in tests/TestFramework.cs, making logic testable via internal static helpers, TempDir usage. Use when writing tests, making code testable, or investigating test failures.

2026-07-110

name	localization
description	Add or change user-visible text in ClamAV UI — Lang.cs keys, English+Ukrainian translations, ApplyLanguage re-texting. Use whenever any UI label, button, log line, tray balloon, status message, or dialog string is added or edited.

Adding / changing user-visible strings

Every user-visible string goes through Lang.T("key") — never hardcode text in the UI, logs, tray balloons, or dialogs.

Steps

Add the key in src/Lang.cs inside the static constructor, grouped with related keys (the file is organized by feature area — find the nearest comment banner):
```
A("settings.schedule", "Scheduled quick scan:", "Плановий швидкий скан:");
```
A(key, english, ukrainian) — both languages, always. English is the default; Ukrainian is the alternative. Missing Ukrainian silently falls back to English, which is a bug, not a feature.
Persistent controls (created once in BuildUi/Build*Page and kept alive) must also be re-texted in ApplyLanguage() in src/MainForm.Ui.cs — otherwise the language switch leaves them stale. Selector buttons with ●/○ markers have their own Update*Buttons() helper that ApplyLanguage() calls (see UpdatePerfButtons, UpdateSchedButtons).
Dialogs and MessageBoxes need nothing extra — they are built fresh each time they open and pick up the current language automatically.

Gotchas

Format placeholders ({0}, {1:0}…) must match the string.Format call site in both translations — tests/LangTests.cs has a test that cross-checks placeholders between En and Uk; it will fail the build if they diverge.
Log lines that end paragraphs carry their own \r\n inside the string — match the neighbors.
ToolStripMenuItem treats & as a mnemonic marker: when reusing a string in a menu, escape it (Lang.T(...).Replace("&", "&&")).
Key naming convention: area.name — btn.*, settings.*, status.*, log.*, tray.*, hero.*, msg.*, sstat.*/sval.* (settings STATUS block), col.* (list columns), title.*, err.*.
Sources are UTF-8 (/codepage:65001); Ukrainian literals are normal — don't escape them.