Opened 14 years ago
Last modified 3 years ago
#5566 new Feature request
Settings / Transfers / Enable Invalid Character Filtering enhancement
| Reported by: | Luis Gonzalez | Owned by: | |
|---|---|---|---|
| Priority: | normal | Component: | FileZilla Client |
| Keywords: | Enable Invalid Character Filtering | Cc: | Luis@… |
| Component version: | Operating system type: | Windows | |
| Operating system version: | Windows 7 Pro 64bit |
Description
I have been trying to upload some directories and files to my yahoo small business ( YSB ) account but every time YSB gets a directory or filename with a space in it, it refuses it and the upload fails with a "Critical file transfer error" - "553-Names must contain only ASCII letters (a-z,A-Z), digits (0-9), underscore, dot and dash." They don't like spaces in filenames :-(
First - I think we need to be able to have the invalid characters feature apply to Uploads, not only downloads.
Second - It would be nice to be able to specify which characters to replace instead of having them hardcoded to \/:*?"<>|
That way we could add a space and have it be converted to an underscore during the upload. Or at least expand the hardcoded invalid characters by adding a space.
I would also like to see user-selectable characters to filter. At the very least, it would be very helpful to be able to select WHICH operating system compatibility mode for filenames one would like to use - I was recently transferring files with FileZilla Client from a GNU/Linux system to an NTFS disk, and the program had no way to filter invalid characters for the destination - the only option in Settings is to filter invalid characters from the LOCAL Operating System, which isn't a good benchmark for a cross-platform data transfer tool, in my opinion.
Proposal:
In Settings -> Transfers (where the limited form of this wonderful feature currently exists), add a drop-down menu to select *which* OS's invalid character set you'd like to filter. Entries could be:
If "Custom" is selected, a form field just below is shown (or un-grayed-out/made editable), and the user can input whichever characters they would like, which also are reflected in "The following character(s) will be replaced" line that exists already (and would dynamically change with the user's drop-down and custom field selections). The OP of this ticket, for instance, could easily type a space character in the Custom field.
Thank you very kindly for a great piece of software, your work is deeply appreciated.