fix(ps1): strip all non-ASCII Unicode from PowerShell scripts

Windows PowerShell 5.1 reads .ps1 files without BOM as Windows-1251 by
default. Em-dashes (-) and other Unicode chars in string literals get
mangled into invalid bytes (e.g. "session - no" becomes garbage that
breaks the parser with "Unexpected token" errors.

Replaced em-dash, en-dash, smart quotes, ellipsis, NBSP and arrows with
their ASCII equivalents across all 12 .ps1 scripts (install/update/
uninstall for claude/gemini/codex/qwen).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This commit is contained in:
delta-cloud-208e
2026-04-21 10:53:15 +00:00
parent cb088c4e9a
commit 3381797148
12 changed files with 1653 additions and 1653 deletions

View File

@@ -1,4 +1,4 @@
# Claude Code Windows Updater
# Claude Code - Windows Updater
# Usage: powershell -ExecutionPolicy Bypass -File claude\uclaude_update.ps1
#
# Updates Claude Code via npm registry + re-applies config patches.