In 1.1 we're introducing a system of gradual restrictions in what characters are allowed in filenames: permissive, ntfs, and restrictive. Poca will try them in order of increasing restrictiveness, based purely on what the filesystem will accept.
However, in some scenarios, the filesystem may be accepting of anything but the files are intended to be shared through less permissive protocols, e.g. CIFS, http, etc.
It would therefore be convient to introduce a setting that would allow the user to manually determine the level to start at. If the setting was ntfs, poca would skip attempting to write a file with the permissive setting, e.g. including a colon in the name, and go straight to an attempt that has weeded out characters forbidden on an NTFS filesystem.
In 1.1 we're introducing a system of gradual restrictions in what characters are allowed in filenames:
permissive
,ntfs
, andrestrictive
. Poca will try them in order of increasing restrictiveness, based purely on what the filesystem will accept.However, in some scenarios, the filesystem may be accepting of anything but the files are intended to be shared through less permissive protocols, e.g. CIFS, http, etc.
It would therefore be convient to introduce a setting that would allow the user to manually determine the level to start at. If the setting was
ntfs
, poca would skip attempting to write a file with thepermissive
setting, e.g. including a colon in the name, and go straight to an attempt that has weeded out characters forbidden on an NTFS filesystem.