OLmatter d06c69f132 fix(ps1): add UTF-8 BOM to all .ps1 to fix PS 5.1 ParserError on CN Windows ...

PS 5.1 on Chinese Windows reads non-BOM files as the system ANSI codepage
(GBK), so UTF-8 Chinese bytes corrupt parsing and surface as
'Missing expression after comma' at param blocks. Adding EF BB BF BOM forces
PS 5.1 to interpret as UTF-8. Affects one_click_start.ps1 (the .cmd entry),
bootstrap_windows.ps1, start_backend.ps1, setup_backend.ps1,
start-backend-pipeline-gui.ps1, and the release scripts.

2026-06-23 03:07:52 +08:00

..

monitor

Fix backend browser capture compatibility

2026-05-26 22:31:25 +08:00

release

fix(ps1): add UTF-8 BOM to all .ps1 to fix PS 5.1 ParserError on CN Windows

2026-06-23 03:07:52 +08:00

tools

feat(macos): add backend setup and launch support

2026-06-20 14:27:31 +08:00

userscripts

revert(userscript): 回退到 v8.19 (e07ec9e)

2026-06-15 23:43:30 +08:00

bootstrap_windows.ps1

fix(ps1): add UTF-8 BOM to all .ps1 to fix PS 5.1 ParserError on CN Windows

2026-06-23 03:07:52 +08:00

one_click_start.ps1

fix(ps1): add UTF-8 BOM to all .ps1 to fix PS 5.1 ParserError on CN Windows

2026-06-23 03:07:52 +08:00

setup_backend_macos.sh

feat(macos): add backend setup and launch support

2026-06-20 14:27:31 +08:00

setup_backend.ps1

fix(ps1): add UTF-8 BOM to all .ps1 to fix PS 5.1 ParserError on CN Windows

2026-06-23 03:07:52 +08:00

setup_backend.py

PR A: Pipeline Backend, YOLO to OCR multi-process, CPU auto-allocation (#10)

2026-06-15 20:57:57 +08:00

start_backend.ps1

fix(ps1): add UTF-8 BOM to all .ps1 to fix PS 5.1 ParserError on CN Windows

2026-06-23 03:07:52 +08:00