[FFmpeg-devel] [PATCH v11 1/6] libavutil/wchar_filename.h: Add whcartoutf8, wchartoansi and utf8toansi

[nil-admirari at mailo.com]

> This patchset does not provide reliable behavior.

Actually it does.

> This way, you won't be able to use long paths with ffmpeg within the next 5-8 years at minimum,

Long paths can be used since August, 2 2016. Some ~6 years have already passed.

> because even in the latest versions of Windows 11, this is not enabled by 
> default in the operating system.

FFmpeg isn't bundled by default either. And not everyone has rights to download and run
arbitrary software on their machines.

> What is the value of adding a capability where it will be a lottery
> game whether it will work or not on each system?

Windows 10 > 1607 + registry key = it works. Otherwise it doesn't. There is no lottery.