lightnovel0
403985208d
The Vocabulary screen advertises that entries are passed to "both ASR hotword and post-processing model context", and that contract holds for Volcengine ASR (which receives them as hotwords) and the Polish LLM (which receives them as a system-prompt block). Whisper-compatible providers (whisper / siliconflow / zhipu / groq) were the gap: their client never set the OpenAI `prompt` field, so the dictionary had no effect on the STT stage at all. That gap shows up as inconsistent transliteration of registered proper nouns. A user who registers "梁山泊" still gets "両山泊" / "良山泊" / "りょうざんぱく" from Whisper, and the Polish LLM cannot always recover once the script choice has already drifted. This change: - Adds an optional `prompt: Option<String>` to `WhisperBatchASR` and attaches it as a `prompt` multipart field when non-blank. Empty/blank prompts are skipped defensively so they cannot trigger provider-specific 4xx responses. - Adds `build_prompt_from_phrases`, a pure helper that joins enabled vocabulary phrases with `, ` and a trailing period, capped at 240 characters (Whisper's published limit is 244 tokens; CJK is worst-case ~1 token/char, so 240 chars is the safe cap). Over-budget entries are skipped individually rather than truncating mid-list, which preserves registration order and lets short later entries still ride along when one earlier entry is unusually long. - Wires `enabled_phrases(inner)` through the helper at the existing Whisper-compatible branch in `coordinator.rs`, mirroring how the Volcengine branch already builds its hotword list. Existing call sites unchanged in behavior when the dictionary is empty (`None` prompt → no `prompt` field on the request). No new dependencies. Tests in `asr::whisper::tests` cover: empty / all-blank input returns None; single and multi phrase joining; per-entry trimming; mid-list blanks are skipped without breaking the join; an over-long single entry is dropped while shorter entries that follow it are kept; the resulting string never exceeds the budget; truncation prefers earlier entries.
OpenLess All-Platform
This is the current cross-platform OpenLess workspace.
App Directory
The runnable Tauri app lives in app/. The macOS build links a vendored C ASR engine (antirez/qwen-asr) tracked as a git submodule under app/src-tauri/vendor/qwen-asr/, so initialize submodules on first clone.
# First clone only — pull in vendored submodules
git submodule update --init --recursive
cd app
npm ci
npm run tauri dev
macOS Build
Use the project build script instead of calling tauri build directly:
cd app
INSTALL=0 ./scripts/build-mac.sh
Generated macOS artifacts:
app/src-tauri/target/release/bundle/macos/OpenLess.appapp/src-tauri/target/release/bundle/dmg/OpenLess_1.1.0_aarch64.dmg
For local install during development:
cd app
./scripts/build-mac.sh
Windows Build
The runnable Tauri app is still app/. Windows contributors should run a
preflight before building so missing MSVC, Windows SDK, or MinGW tools fail
with actionable messages.
cd app
powershell -ExecutionPolicy Bypass -File .\scripts\windows-preflight.ps1
MSVC Route
Use this route when Visual Studio Build Tools and the Windows SDK are installed.
Open a Developer PowerShell, or call vcvars64.bat, then run:
cd app
npm ci
npm run tauri -- build
Required Visual Studio Installer components:
Microsoft.VisualStudio.Workload.VCTools- MSVC v143 x64/x86 build tools
- Windows 10/11 SDK that provides
kernel32.lib
If link.exe or kernel32.lib is missing, rerun:
powershell -ExecutionPolicy Bypass -File .\scripts\windows-preflight.ps1 -Toolchain msvc
GNU / MinGW Route
Use this route when MSVC/Windows SDK is unavailable. The app now lives under
the no-space openless-all directory to avoid GNU/MinGW path quoting issues
while generating import libraries. Use the helper script to keep the GNU build
environment and target setup consistent.
cd app
scoop install rustup mingw
rustup toolchain install stable-x86_64-pc-windows-gnu
rustup target add x86_64-pc-windows-gnu
powershell -ExecutionPolicy Bypass -File .\scripts\windows-preflight.ps1 -Toolchain gnu
powershell -ExecutionPolicy Bypass -File .\scripts\windows-build-gnu.ps1
Generated GNU artifacts:
%TEMP%\openless-windows-gnu\src-tauri\target\x86_64-pc-windows-gnu\release\openless.exe%TEMP%\openless-windows-gnu\src-tauri\target\x86_64-pc-windows-gnu\release\bundle\msi\OpenLess_*_x64_en-US.msi%TEMP%\openless-windows-gnu\src-tauri\target\x86_64-pc-windows-gnu\release\bundle\nsis\OpenLess_*_x64-setup.exe
Hotkey Injection Gate
Use this gate before/after Windows hotkey changes when a physical keyboard
regression is unavailable. It injects a dev/test-only hotkey click through the
coordinator handle_pressed / handle_released path, asserts the log contains
[coord] hotkey pressed, and cancels the dry-run session automatically.
cd app
npm run check:hotkey-injection
Windows Runtime Notes
- Windows does not need the macOS Accessibility permission. Use Settings -> Permissions -> Global hotkey to inspect listener status.
- Microphone permission is checked by opening a short-lived input stream, so a device-format query alone is not treated as permission granted.
- Text insertion through
Ctrl+Vis treated as copy fallback unless the app can confirm insertion.
Release Signing
Tagged releases (v*-tauri) must be Developer ID signed and notarized so users can download and open the macOS app without manually removing quarantine attributes.
Required GitHub secrets:
APPLE_CERTIFICATEAPPLE_CERTIFICATE_PASSWORDAPPLE_IDAPPLE_PASSWORDAPPLE_TEAM_ID
Optional:
APPLE_PROVIDER_SHORT_NAMEKEYCHAIN_PASSWORD
Manual workflow runs can still produce ad-hoc signed test builds, but tagged macOS releases fail if signing/notarization secrets are missing.
Ignored Local Output
The following are intentionally local-only:
app/node_modules/app/dist/app/src-tauri/target/app/src-tauri/gen/.DS_Store