Skip to content

fix: support non-ASCII filenames in open-file script - #785

Open
YorkWaugh wants to merge 1 commit into
Samillion:mainfrom
YorkWaugh:main
Open

fix: support non-ASCII filenames in open-file script#785
YorkWaugh wants to merge 1 commit into
Samillion:mainfrom
YorkWaugh:main

Conversation

@YorkWaugh

Copy link
Copy Markdown

Fixes an issue where the open-file dialog fails to load files containing non-ASCII characters. This is resolved by explicitly setting the PowerShell console output encoding to UTF-8 before executing the dialog commands, ensuring compatibility with mpv's UTF-8 expectation.

Fixes #780

Fixes an issue where the open-file dialog fails to load files containing non-ASCII characters. This is resolved by explicitly setting the PowerShell console output encoding to UTF-8 before executing the dialog commands, ensuring compatibility with mpv's UTF-8 expectation.

Fixes Samillion#780
Copilot AI lite review requested due to automatic review settings August 19, 2026 16:21

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This pull request addresses a Windows-specific mpv integration bug where open-file.lua fails to open paths containing non-ASCII characters by ensuring PowerShell emits UTF-8 text so mpv can correctly interpret selected filenames.

Changes:

  • Prefixes PowerShell -Command content with a statement that sets [Console]::OutputEncoding to UTF-8.
  • Routes the existing dialog PowerShell script through the new UTF-8-prefixed command string.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

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.

file-open can't deal with non-ascii

2 participants