On Fri, 23 Jan 2009 at 21:55, Oleg Broytmann wrote: > On Fri, Jan 23, 2009 at 10:15:18AM -0800, Brett Cannon wrote: >> If I remember correctly something along Martin's comment about 7-bit >> clean is needed, but some servers don't follow the standard, so I >> swapped it to Latin-1. But that was so long ago I don't remember where >> I gleaned the details from in the RFC. If I misread the RFC and it is >> UTF-8 then all the better to make more of the world move over to >> Unicode. > > I don't know any server that encode file names in any way. All servers > I know just pass filenames as is, 8-bit; some that implement stricter > RFC-959 mangle chr(255), but that's all. One can encounter a server that > stores files in a number of different encodings. Given that a Unix OS can't know what encoding a filename is in (*), I can't see that one could practically implement a Unix FTP server in any other way. --RDM (*) remember the earlier extensive discussion of this when the issue of listdir() ignoring non-encodable filesnames came up?
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4