Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

martin

Anonymous wrote:

Sounds great! I notice this is now implemented but apparently for downloads only, the substituted charcters are not replace on upload yet? Thanks very much for WinSCP.

Not yet.
Guest

Sounds great! I notice this is now implemented but apparently for downloads only, the substituted charcters are not replace on upload yet? Thanks very much for WinSCP.
martin

Re: offending chars in path/filenames

What about replacing the offending character with %XX, where XX is ASCII code in hexa and restoring original character on upload?
Guest

Re: offending chars in path/filenames

I'll consider that. However you are the first one asking for this, so it has low priority, sorry


:-)

I stand for silent masses <g>


It does not handle that. The later file will overwrite the older one.


Actually, if there were 'make unique' option (like GetRight etc.) I might not need the replacement chars to be of my own choice. But, overriting a file due to char replacement is not really acceptable because you will never know what has been overwritten.
martin

Re: offending chars in path/filenames

a2z wrote:

Could you let us specify our own replacement characters.

I'll consider that. However you are the first one asking for this, so it has low priority, sorry :-(

And, one more thing: if a filename/path collision arose
due to char replacement; how does WinSCP handle that?

It does not handle that. The later file will overwrite the older one.
a2z

Re: offending chars in path/filenames

True. I have read the docs.

But, WinSCP replaces them what WinSCP considers best.

Could you let us specify our own replacement characters.

And, one more thing: if a filename/path collision arose
due to char replacement; how does WinSCP handle that?
martin

Re: offending chars in path/filenames

WinSCP automatically (by default) replaces such characters with underscore. See documentation.
a2z

offending chars in path/filenames

Hi Martin,

I have a couple of million mail files in a Linux box and I want to copy these files to a Windows box.

The trouble is, these filenames contain chars that are forbidden in Windows --such as ':' etc.

How do I automagically substitute a char (of my choice) for those offending chars during the copy operation?

Thank you for WinSCP -- a life saver.