On 6/24/2021 12:44 PM, Nicolas George wrote:
James Almer (12021-06-24):
Are we ok that file with a \n in their name will not be supported?
Yes, since it's used to delimit files in the list.
I know, it is the reason I asked. So, I say it negatively:
I am not ok that this prevents valid filenames from being used, even if
they are very exotic.
Can the \n in filenames be escaped, either with backslash or quotes,
like with other special characters? If so, then they should be supported
that way already.
At least on Windows a backslash is not allowed on file names (Alongside many
other such characters), but apostrophes are, and they effectively need to be
escaped. Thanks for catching it.
I'll add a mention in the doxy about the need to escape certain characters.
On Unix, backslashes are allowed. So are newlines. They need to be
supported.
The former is supported, of course. And i assume so should the latter.
Regards,
_______________________________________________
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".
_______________________________________________
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".
