d/freebsd-nq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Reword the description of the UTF8 option (-8) so I can swear

Browse Source 
to myself that I understand it.

Bump document date.
This commit is contained in:
Yaroslav Tykhiy 2007-04-19 17:30:19 +00:00
parent 0d4e0cc591
commit 1fd42e91ee
1 changed files with 13 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
libexec/ftpd/ftpd.8
View File

@ -32,7 +32,7 @@
.\" @(#)ftpd.8 8.2 (Berkeley) 4/19/94
.\" $FreeBSD$
.\"
.Dd January 21, 2006
.Dd April 19, 2007
.Dt FTPD 8
.Os
.Sh NAME
@ -79,20 +79,19 @@ is specified, accept connections via
.Dv AF_INET6
socket.
.It Fl 8
The server is running in transparent UTF-8 mode.
That is, it just encourages RFC\ 2640 compliant clients to send
paths encoded in UTF-8 in their commands.
In particular, the names of files uploaded by such clients will
have UTF-8 encoding.
The clients will also assume that server replies and existing file
names have UTF-8 encoding, too.
The names of files preloaded to the server should meet this expectation
for the clients to present the correct file names to their users.
Own messages of
.Nm
are always encoded in ASCII, which in fact is a subset of UTF-8.
Enable transparent UTF-8 mode.
RFC\ 2640 compliant clients will be told that the character encoding
used by the server is UTF-8, which is the only effect of the option.
.Pp
Note that this option does not make the server do any encoding conversion.
This option does not enable any encoding conversion for server file names;
it implies instead that the names of files on the server are encoded
in UTF-8.
As for files uploaded via FTP, it is the duty of the RFC\ 2640 compliant
client to convert their names from the client's local encoding to UTF-8.
FTP command names and own
.Nm
messages are always encoded in ASCII, which is a subset of UTF-8.
Hence no need for server-side conversion at all.
.It Fl A
Allow only anonymous ftp access.
.It Fl a