![]() latin1 '' # 8-bit with nonprintable 128-159, we assume latin1Ĥ) locale_search. Thus a width of 2 means UTF-8 (or some other multibyte encoding, which is not likely for me), a width of 3 means latin-N (with no way to know N), and 4 means some single-byte encoding with printable characters in the range 128–159. ![]() ![]() widthof -1 displays a 4-byte string which represents 2 characters in UTF-8, and in which only 3 bytes are printable latin-N characters. In my shell startup, I set LC_CTYPE in this way, using a script widthof which I posted in Get the display width of a string of characters. But if for you the only two likely possibilities are UTF-8 and one legacy encoding, that works well. This won't help you in all cases, for example it can't distinguish between single-byte encodings. SyncTERM BBS terminal: A program that supports SSHv2, RLogin. stws alows SyncTERM (BBS terminal program) to be accessible through a standard Web browser in a full screen mode. Display a byte string that has a different width in different encodings, and find out by how much it makes the cursor move. This command helps telnet protocol to achievecommunication with a remote device and. If you have some idea of which character encodings are likely, you may be able to determine the encoding via heuristics. I think it would be great if we started a Macintosh BBS ring to support each. When I dial the same BBS using minicom, everything comes through fine. When syncterm connects to the same BBS using telnet instead of a dial-up modem then everything comes through fine. (Other environment variables may convey the locale settings, see What should I set my locale to and what are the implications of doing so? for details.) Old version of syncterm for mac osx Old version of syncterm download. When syncterm connects to a BBS using a dial-up modem, none of the received bytes are displayed. Unfortunately, in practice, checking LC_CTYPE is not always reliable: it may be unset or wrong. (Listed as TelnetS under Connection Type) bear in mind nightly builds are meant for testing and might be. Join 49 other subscribers Tags 5.If the terminal emulator is well-designed and configured appropriately, it will ensure that the value of the environment variable LC_CTYPE is set to a value that is consistent with its encoding. Full ANSI-BBS support Full CGTerm Commodore 64 PETSCII support Full Atari 8-bit ATASCII support DoorWay support Support for IBM low and high ASCII including. SyncTERM nightly builds also support Telnet/SSL. Good list of Atari BBS’s (Hosted by SFHQ): Lon Seidman – Retro Review – BBS Systems:.Alistair Ross – Back To The BBS Documentary Part 3:.Alistair Ross – Back To The BBS Documentary Part 2:.In Terminal.app (and probably iTerm2 as well), this just prints a question mark. Alistair Ross – Back To The BBS Documentary Part 1: In SyncTERM, which uses the IBM Extended ASCII character encoding, you would use an octal escape sequence like 261.Note it shows if there are unread messages:Įxtras! Check out the ATASCII movies, but set your baud rate below 1200 to view them if you want to be able to read them: A random starship or space station appears:Ĭhanging message boards. Most Atari boards ask for a keystroke to identify if they support ATASCII graphics or not:Ĭhecking for e-mail (in the early 80’s!):Įxcellent color ANSI login screen.
0 Comments
Leave a Reply. |