Comment 47 for bug 222635

(In reply to comment #42)
> I am concerned that just setting the control channel's content charset isn't
> enough. There is code in ftp that deals with filepaths, conversion from
> filepaths to VMS paths, and other suspect code. Did you review this to see if
> anything needs to change?

Current code uses ISO-8859-1 for all FTP channel. So even if current is VMS style, it is no problem to convert from ISO-8859-1 to UTF-8. (7bit character map is same. So "[", "]", "/" and "." is same mapping. And, if problem occurs with FEAT - UTF8 enable, it is broken characters as UTF8.)

And, I don't think that VMS style server supports new feature such as RFC2640.

Also, I will create new patch for changing metadata.