On 6/13/22 2:55 PM, Hendrik Leppkes wrote:
This seems unrelated to this patch, which is about removing the MAX_PATH limit. The code previously converted UTF-8 to ANSI, and still does so now, just without the MAX_PATH limit. Further improvements tangential to this topic can, and should, be applied independently, and not hold up this patch in discussion-hell for longer than necessary.
Agreed. As is stands, if a user finds that they need to open files that use non-ANSI characters in their filenames, they can always go into their Language settings and turn on UTF-8 for worldwide language support, which was just as true before the MAX_PATH-related patches. Honestly, Microsoft just needs to stop delaying it and make UTF-8 the default, and then we won't have this problem anymore.
_______________________________________________ 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".
