Nick Sarnie (12022-11-24): > The current URI handling only removes the file: prefix, but we also need to > consider the case of percent encoding. > Percent encoding can happen with non-ASCII characters in the path.
NAK, this is a huge compatibility break.
But this fix is necessary, you are right.
What needs to happen to handle this correctly:
- Introduce a “fs:” protocol as a synonym to file:.
- Change “file:” (but not “fs:”!) to detect if the rest of the path
looks like a real file URL or a raw file path.
- If it looks like a real file URL, de-percent-escape it.
- If it looks like a raw file path, treat it the legacy way after
printing a warning.
- In a few years, remove the heuristics and always handle “file:” in the
standards-compliant way.
I believe we can ignore incomplete / relative file:// URLs in the
transition period. The triple / would be a very reliable way of
identification.
Regards,
--
Nicolas George
signature.asc
Description: PGP signature
_______________________________________________ ffmpeg-devel mailing list [email protected] https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email [email protected] with subject "unsubscribe".
