On Wednesday, 5 July 2017 8:18:26 PM, Hendrik Leppkes wrote:
They are, but some people have non-unicode filenames on their systems
and thats the only way to access them.
- Hendrik
Are you sure? Windows' syscalls use UCS-2/UTF-16, so every filename should
be
representable with wide characters. Functions like MoveFileExA just convert
their arguments to UTF-16 using MultiByteToWideChar or an equivalent
function
and delegate to the wide-character variant. If libav wants to avoid linking
directly to MoveFileExA, but has to deal with filenames encoded in the ANSI
codepage, calling MultiByteToWideChar(CP_ACP) on each argument and calling
MoveFileExW should be equivalent.
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
