Skip to content

Fix setup-dev.ps1 failing on Windows PowerShell 5.1#51

Open
Wyatt Bartel (wybartel) wants to merge 1 commit intoLightricks:mainfrom
wybartel:fix/setup-dev-win-encoding
Open

Fix setup-dev.ps1 failing on Windows PowerShell 5.1#51
Wyatt Bartel (wybartel) wants to merge 1 commit intoLightricks:mainfrom
wybartel:fix/setup-dev-win-encoding

Conversation

@wybartel
Copy link

@wybartel Wyatt Bartel (wybartel) commented Mar 10, 2026

Windows PowerShell 5.1 reads UTF-8 files without a BOM using the system ANSI code page (CP1252). Several Unicode characters in the script (em-dashes, box-drawing chars, checkmarks) contain bytes that are interpreted as string delimiters in CP1252, causing a parser error. This PR replaces all non-ASCII characters with ASCII equivalents for ease of compatibility long term

image

…rs (box-drawing, checkmarks, em-dash) caused a parser error when PowerShell 5.1 read the UTF-8 file without BOM using the system ANSI code page. Replace all non-ASCII decorative characters with ASCII equivalents.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant