@@ -83,32 +83,36 @@ There are also two fingerprinting CLIs, ``telnetlib3-fingerprint`` and
8383Encoding
8484~~~~~~~~
8585
86- The default encoding is the system locale, usually UTF-8, and, without negotiation of BINARY
87- transmission, all Telnet protocol text *should * be limited to ASCII text, by strict compliance of
88- Telnet. Further, the encoding used *should * be negotiated by CHARSET.
86+ The default encoding of telnetlib3-client and server is set by the `locale
87+ <https://man7.org/linux/man-pages/man1/locale.1.html> `_.
8988
90- When these conditions are true, telnetlib3-server and telnetlib3-client allow connections of any
91- encoding supporting by the python language, and additionally specially `` ATASCII `` and `` PETSCII ``
92- encodings. Any server capable of negotiating CHARSET or LANG through NEW_ENVIRON is also presumed
93- to support BINARY .
89+ Without negotiation of BINARY transmission, all Telnet protocol text * should * be limited to ASCII
90+ text, by strict compliance of Telnet. Further, the encoding used * should * be negotiated by CHARSET
91+ :rfc: ` 2066 ` or by `` LANG `` using `` NEW_ENVIRON `` :rfc: ` 1572 `. Otherwise, a compliant telnet client
92+ should be limited to ASCII .
9493
95- From a February 2026 `census of MUDs <https://muds.modem.xyz >`_ and `BBSs servers
94+ When these conditions are true, telnetlib3-server and telnetlib3-client allow *automatic
95+ negotiation * of any encoding in either direction supported by the python language, or any
96+ custom ``ATASCII ``, ``PETSCII ``, and ``big5bbs `` provided with telnetlib3.
97+
98+ **However **, from a February 2026 `census of MUDs <https://muds.modem.xyz >`_ and `BBSs servers
9699<https://bbs.modem.xyz> `_:
97100
98- - 2.8% of MUDs support bi-directional CHARSET
99- - 0.5% of BBSs support bi-directional CHARSET.
100- - 18.4% of BBSs support BINARY.
101- - 3.2% of MUDs support BINARY.
101+ - 2.8% of MUDs and 0.5% of BBSs support bi-directional CHARSET
102+ - 18.4% of BBSs and 3.2% of MUDs support BINARY.
102103
103- For this reason, it is often required to specify the encoding, eg.!
104+ This means that connecting to *large majority * of BBSs or MUDs that transmit non-ascii, it will
105+ require *manually specifying an encoding *, eg.::
104106
105107 telnetlib3-client --encoding=cp437 20forbeers.com 1337
106108
109+ telnetlib3-client --encoding=big5bbs bbs.ccns.ncku.edu.tw 3456
110+
107111Raw Mode
108112~~~~~~~~
109113
110- Some telnet servers, especially BBS systems or those designed for serial transmission but are
111- connected to a TCP socket without any telnet negotiation may require "raw" mode argument::
114+ Some telnet servers, especially "retro" BBS systems or those designed for serial transmission but
115+ are connected to a TCP socket without any telnet negotiation may require the "raw" mode argument::
112116
113117 telnetlib3-client --raw-mode area52.tk 5200 --encoding=atascii
114118
0 commit comments