> Presumably, the original manifest idea, parsed down to only using it to > force FFmpeg into UTF-8, would be sufficient for this, right?
UTF-8 in manifest was rejected as too far-reaching, and then longs paths were reimplemented with \\?\ prefixes, so now there is no manifest at all. > The Windows API does have a SetConsoleCP function. It does not change process code page. > C3) Use avs_get_version, but if it's not a new enough version, just fall > back to the logic that exists now Done in https://ffmpeg.org/pipermail/ffmpeg-devel/2022-June/297494.html. _______________________________________________ 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".