## Link to GitHub Issue or related Pull Request, if one exists n/a ## Description of change Fixes broken Japanese text when Windows `Use Unicode UTF-8 for worldwide language support` setting is enabled. This setting changes the system ACP to UTF-8 (65001), causing legacy Shift-JIS lead-byte checks to fail. Windows 11: requests the legacy process code page through the manifest. Windows 10: detects ACP 65001 (UTF-8), warns the user via deferred log, and applies compatibility hook (only for popn pika model for now) Windows 7 and below - UTF-8 option doesn't exist. ## Testing
32 lines
1.4 KiB
XML
32 lines
1.4 KiB
XML
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
|
|
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0" xmlns:asmv3="urn:schemas-microsoft-com:asm.v3">
|
|
<assemblyIdentity version="1.0.0.0" processorArchitecture="*" name="spice.exe" type="win32"/>
|
|
<description>SpiceTools</description>
|
|
<asmv3:application>
|
|
<asmv3:windowsSettings xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">
|
|
<dpiAwareness xmlns="http://schemas.microsoft.com/SMI/2016/WindowsSettings">PerMonitorV2</dpiAwareness>
|
|
<dpiAware>true</dpiAware>
|
|
<activeCodePage xmlns="http://schemas.microsoft.com/SMI/2019/WindowsSettings">Legacy</activeCodePage>
|
|
</asmv3:windowsSettings>
|
|
</asmv3:application>
|
|
<dependency>
|
|
<dependentAssembly>
|
|
<assemblyIdentity
|
|
type="win32"
|
|
name="Microsoft.Windows.Common-Controls"
|
|
version="6.0.0.0"
|
|
processorArchitecture="*"
|
|
publicKeyToken="6595b64144ccf1df"
|
|
language="*"
|
|
/>
|
|
</dependentAssembly>
|
|
</dependency>
|
|
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v2">
|
|
<security>
|
|
<requestedPrivileges>
|
|
<requestedExecutionLevel level="asInvoker" uiAccess="false"/>
|
|
</requestedPrivileges>
|
|
</security>
|
|
</trustInfo>
|
|
</assembly>
|