This causes char-based filesystem and other API calls to accept and produce UTF-8 strings instead of locale-dependent legacy code page strings, when running on Win10 or newer.
By and large, ffmpeg uses the wide-character equivalents of these APIs, so this shouldn't have any effect on most usage. --- fftools/fftools.manifest | 1 + 1 file changed, 1 insertion(+) diff --git a/fftools/fftools.manifest b/fftools/fftools.manifest index f2708ecb13..eaef6cacf1 100644 --- a/fftools/fftools.manifest +++ b/fftools/fftools.manifest @@ -4,6 +4,7 @@ <asmv3:windowsSettings> <dpiAware xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">true</dpiAware> <dpiAwareness xmlns="http://schemas.microsoft.com/SMI/2016/WindowsSettings">PerMonitorV2</dpiAwareness> + <activeCodePage xmlns="http://schemas.microsoft.com/SMI/2019/WindowsSettings">UTF-8</activeCodePage> </asmv3:windowsSettings> </asmv3:application> </assembly> -- 2.39.1 _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".