Oleg Broytmann wrote: > On Fri, Jan 23, 2009 at 02:35:01PM -0500, rdmurray at bitdance.com wrote: >> 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. > > Can you believe there is a well-known program that solved the issue?! It > is Apache web server! One can configure different directories and different > file types to have different encodings. I often do that. One (sysadmin) can > even allow users to do the configuration themselves via .htaccess local files. > I am pretty sure FTP servers could borrow some ideas from Apache in this > area. But they don't. Pity. :( > AFAIK, Apache is in the same boat as ftp servers. You're thinking of the encoding inside of the files. The problem is with the file names themselves. -Toshio -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: OpenPGP digital signature URL: <http://mail.python.org/pipermail/python-dev/attachments/20090123/0e384ec9/attachment-0001.pgp>
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