summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJames Ross-Gowan <rossy@jrg.systems>2020-08-06 19:52:17 +1000
committerJan Ekström <jeebjp@gmail.com>2020-08-08 15:00:25 +0300
commitbb231889fdd2ee0f519bdb1c756b61ceefd5584b (patch)
tree9a645d8391f5893bf9c67401ef308394fe1b6120
parentcdd8ba7224a75582c5bcec4906d305f2341400ad (diff)
downloadmpv-bb231889fdd2ee0f519bdb1c756b61ceefd5584b.tar.bz2
mpv-bb231889fdd2ee0f519bdb1c756b61ceefd5584b.tar.xz
win32: request the UTF-8 code page for Windows APIs
This sets the activeCodePage property in the manifest, which forces the ANSI code page to be UTF-8 in Windows 10 1903 and up. It shouldn't make a difference for mpv itself, since mpv already uses the wide-char APIs for most functions, however some of mpv's dependencies, such as Lua, rely on the ANSI codepage. Hence this change enables support for Unicode file names in Lua's I/O library. Thanks @avih for finding this property. See: https://docs.microsoft.com/en-us/windows/uwp/design/globalizing/use-utf8-code-page
-rw-r--r--osdep/mpv.exe.manifest1
1 files changed, 1 insertions, 0 deletions
diff --git a/osdep/mpv.exe.manifest b/osdep/mpv.exe.manifest
index accc2eddc8..32dd80b3f8 100644
--- a/osdep/mpv.exe.manifest
+++ b/osdep/mpv.exe.manifest
@@ -11,6 +11,7 @@
<windowsSettings>
<dpiAware xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">True/PM</dpiAware>
<dpiAwareness xmlns="http://schemas.microsoft.com/SMI/2016/WindowsSettings">PerMonitorV2,PerMonitor</dpiAwareness>
+ <activeCodePage xmlns="http://schemas.microsoft.com/SMI/2019/WindowsSettings">UTF-8</activeCodePage>
</windowsSettings>
</application>
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v2">