Followup to: <[EMAIL PROTECTED]>
By author: Bruno Haible <[EMAIL PROTECTED]>
In newsgroup: linux.utf8
>
> Alexander Voropay writes:
>
> > Another problem is 0xFF codepoint (not for Linux console, but for
> > some software and Telnet protocol).
>
> Where do you see a problem with telnet and 0xFF? In telnet from Linux
> to Linux or Solaris I can, after having set the options "inbinary" and
> "outbinary", enter and output the 0xFF character. Can you point out a
> place in the telnet protocol specification which mishandles 0xFF?
>
The protocol doesn't (it should be transmitted as 0xFF 0xFF), but some
braindamaged implementations of it do (because they transmit 0xFF
instead of 0xFF 0xFF, resulting in the character after the 0xFF being
interpreted as a command by the other, correctly implemented, side.)
Such implementations are occationally referred as "7.99 bit clean".
-hpa
--
<[EMAIL PROTECTED]> at work, <[EMAIL PROTECTED]> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
