> -----Original Message----- > From: ffmpeg-devel <ffmpeg-devel-boun...@ffmpeg.org> On Behalf Of nil- > admir...@mailo.com > Sent: Monday, April 25, 2022 11:04 AM > To: ffmpeg-devel@ffmpeg.org > Subject: Re: [FFmpeg-devel] [PATCH v11 1/6] > libavutil/wchar_filename.h: Add whcartoutf8, wchartoansi and > utf8toansi > > > You normally don't load libraries from such longs paths. > > And? 80% of FFmpeg functionality is normally not used.
Again, you have deleted my asking for an example scenario and which library would need to be loaded from a long path. > > But file IO is a fundamental feature where a common and predictable > > behavior is crucial. > > You're talking as if the manifest change somehow broke or > fundamentally altered > file IO, which it clearly did not. For the longpaths attribute, you could surely argue that it's "just" that you don't know whether it will work or not. But forcing a different code page for a process _IS_ a fundamental alteration. I'm restoring the line of your own question which you have deleted: > > > > Is it a big deal to change a registry and reboot? My response to that was: > > Yes it is. Especially when you don't know that it's needed or > whether > > it's needed or when it is needed. > > Also it requires administrative permissions which not everybody has. > > Further it's a serious change to OS behavior and you cannot expect > that > > all users are educated enough for being able to make this decision > > and be confident that it won't have any unexpected side effects. > > What does all of that have to do with these patches? Really? I answer your question and then you delete your question and ask what my answer would have to do with the patchset? sw _______________________________________________ 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".