CAPS.TXT IMPLEMENTATION NOTES
                          Last updated 2024-01-20

Clients should be prepared for values within caps.txt to be the empty
string (having no characters between the equals sign and the newline). One
caps.txt file has empty values.

Servers should not include any whitespace around their keys, values, or
comments. 100% of caps.txt files have no such whitespace.

Servers should use capital letters for the TRUE and FALSE boolean values.
100% of caps.txt files use capital letters for boolean values.

                        Keys in alphabetical order:

DefaultEncoding (non-Floodgap):
Clients should treat DefaultEncoding as an alias of ServerDefaultEncoding.
1% of caps.txt files have a DefaultEncoding key.

PathIdentity:
Clients should treat an empty value of PathIdentity as meaning there is no
PathIdentity. This is not the same as the default value; Floodgap specifies
the default value of PathIdentity is . (the period character). One caps.txt
file has an empty PathIdentity value.

PathParent:
Clients should treat an empty value of PathParent as meaning there is no
PathParent. This is not the same as the default value; Floodgap specifies
the default value of PathParent is .. (two period characters). One caps.txt
file has an empty PathParent value.

ServerDefaultEncoding (non-Floodgap):
Clients should treat the value of ServerDefaultEncoding as a case-
insensitive character set name. They should use the specified character set
when interpreting text files (type 0) and menus (type 1, 7) from the same
server. 65% of caps.txt files have a ServerDefaultEncoding key.
A list of character set names is available at IANA's "Character Sets"
registry.

ServerTLSPort:
Clients should treat a ServerTLSPort value of 0 as equivalent to an
unspecified value. 63% of caps.txt files use ServerTLSPost=0 to indicate
there is no TLS port.