Timeline for What protocol do Teletypes use?
Current License: CC BY-SA 4.0
49 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 18, 2020 at 8:29 | history | edited | CommunityBot |
Commonmark migration
|
|
| Mar 2, 2020 at 6:25 | comment | added | Lars Brinkhoff | Do you have any comment on the use of ↑ and ← instead of ^ and _? | |
| Feb 19, 2019 at 5:24 | history | edited | Jamie Hanrahan | CC BY-SA 4.0 |
added 131 characters in body
|
| Feb 19, 2019 at 2:35 | comment | added | Jamie Hanrahan |
Hmm... That would depend on which typewriter you were talking about. IBM's typewriters did already have 2 shifting to @ before ASCII was designed. But most (maybe all?) manual typewriters, and even some electrics, did not.
|
|
| Feb 19, 2019 at 2:30 | history | edited | Jamie Hanrahan | CC BY-SA 4.0 |
added 1310 characters in body
|
| Feb 18, 2019 at 23:10 | comment | added | supercat |
@JamieHanrahan: Right. My point was that the ASCII arrangement was "typewriter paired" at the time the code points were placed. Had IBM's revised keyboard layout preceded ASCII, I would expect that ' and " would differ by 16, as would 2 and @. Not sure about how 6-7-8-9-0 would have been handled, since shift-zero would seem to be suggestive of the "space" character.
|
|
| Feb 18, 2019 at 23:03 | comment | added | Jamie Hanrahan |
@supercat Yes. That aspect of ASCII was designed for the 2-shifts-to-" layout that was already a standard for manual typewriters. It made keyboard encoders simpler. IBM moved the ' and " to the same key on their electric typewriters because they wanted those "lightweight" characters to hit the paper with lighter force, and grouping them on the same key made that easier to implement. DEC and others (and of course IBM) followed that arrangement, now called "typewriter-paired", which made the keyboards marginally more complex.
|
|
| Feb 18, 2019 at 17:17 | comment | added | supercat |
The arrangement of ASCII codes was designed to separate things that should appear as shifted and unshifted versions of the same key, 16 codes apart. The codes for 2 and " were chosen because typewriters of the era used shift-2 for ". The notion that shift-2 should yield @ didn't come until later.
|
|
| Feb 18, 2019 at 2:29 | history | edited | Jamie Hanrahan | CC BY-SA 4.0 |
added pic of an asr32, plus a bit of info about the figs and ltrs keys
|
| S Nov 18, 2018 at 16:43 | history | suggested | chicks | CC BY-SA 4.0 |
kbd formatting and tweaked Markdown for heading
|
| Nov 18, 2018 at 16:06 | review | Suggested edits | |||
| S Nov 18, 2018 at 16:43 | |||||
| Nov 6, 2018 at 16:59 | history | edited | Jamie Hanrahan | CC BY-SA 4.0 |
added 187 characters in body
|
| Nov 6, 2018 at 16:49 | history | edited | Jamie Hanrahan | CC BY-SA 4.0 |
added a lengthy aside about origin of "marking" and "spacing" terms wrt Morse telegraphy
|
| Nov 4, 2018 at 3:07 | history | edited | Jamie Hanrahan | CC BY-SA 4.0 |
added 554 characters in body
|
| Nov 2, 2018 at 23:02 | history | edited | Jamie Hanrahan | CC BY-SA 4.0 |
minor tweaks
|
| Sep 26, 2018 at 14:31 | history | edited | Jamie Hanrahan | CC BY-SA 4.0 |
minor tweaks
|
| Nov 29, 2017 at 19:40 | history | edited | Jamie Hanrahan | CC BY-SA 3.0 |
minor tweaks
|
| Oct 18, 2017 at 19:07 | vote | accept | wizzwizz4♦ | ||
| Oct 10, 2017 at 10:35 | history | edited | Jamie Hanrahan | CC BY-SA 3.0 |
minor tweaks
|
| Oct 2, 2017 at 9:03 | history | edited | Jamie Hanrahan | CC BY-SA 3.0 |
minor tweaks
|
| Sep 26, 2017 at 20:28 | history | edited | Jamie Hanrahan | CC BY-SA 3.0 |
minor tweaks
|
| Sep 3, 2017 at 8:11 | history | edited | Jamie Hanrahan | CC BY-SA 3.0 |
added 212 characters in body
|
| Aug 11, 2017 at 10:34 | history | edited | Jamie Hanrahan | CC BY-SA 3.0 |
added 1611 characters in body
|
| Aug 11, 2017 at 10:27 | history | edited | Jamie Hanrahan | CC BY-SA 3.0 |
added 1611 characters in body
|
| Aug 11, 2017 at 6:32 | comment | added | Jamie Hanrahan | @JdeBP The ASR33 did also: xon and xoff would tell the other end's paper tape reader to start and stop. And that is where we got xon/xoff "inband" flow control. I don't believe any of the pre-ASCII machines did anything like that - after all there were no codes in the codeset for any such purpose. | |
| Aug 11, 2017 at 5:42 | comment | added | JdeBP |
You forgot one aspect of protocol: control sequences. The Model 37 respected several control sequences. You might be amazed to find that softwares in common usage today (e.g. less, ul, ncal and suchlike on Unix and Linux systems) still employ those same control sequences and have not even advanced to ECMA-48:1976. Have an improved manual page for ul.
|
|
| Aug 10, 2017 at 21:00 | comment | added | KlaymenDK | I hope you do technical writing. That was excellent! | |
| Aug 10, 2017 at 20:32 | comment | added | Wayne Conrad | Not fair! You made this answer even more awesome since I voted it up, but I can't vote it up a second time. | |
| Aug 10, 2017 at 18:18 | history | edited | Jamie Hanrahan | CC BY-SA 3.0 |
added 391 characters in body
|
| Aug 10, 2017 at 16:44 | history | edited | Jamie Hanrahan | CC BY-SA 3.0 |
added 1020 characters in body
|
| Aug 10, 2017 at 16:18 | comment | added | Jamie Hanrahan | @MartinBonner But that's today. It's actually been a couple of decades since it became absurdly cheap to include a ROM in the keyboard, so a "bit paired" layout is no longer important for cost savings. The HP 2640 series terminals had bit-paired keyboards, as did some of the really inexpensive (for the time) kbds used on some of the early micros. DEC went to "typewriter-paired" by the time of the VT-52 and LA36, or maybe earlier. | |
| Aug 10, 2017 at 15:59 | comment | added | William | @RickBrant - That is an absurd level of detail. Nicely done! | |
| Aug 10, 2017 at 12:27 | comment | added | fishinear | Agree with @MartinBonner. The shifted digits are highly country dependent. Here is Sweden they are: !"#€%&/()= | |
| Aug 10, 2017 at 12:23 | comment | added | Martin Bonner supports Monica | One additional point: UK keyboards (today) have shift-2 as " - but the shifted digits are: !"£$%^&*() whereas they would need to be !"#$%&'()<space> for bit pairing. | |
| Aug 10, 2017 at 11:50 | comment | added | Jamie Hanrahan | @JeremyP Seems like you didn't read my answer very thoroughly. Nor was the question specific to the 33 and later. | |
| Aug 10, 2017 at 9:27 | comment | added | JeremyP | @RickBrant It's not the Baudot code. Teletype model 33 and later used ASCII | |
| Aug 10, 2017 at 7:31 | comment | added | Jamie Hanrahan | @William-Rem Is that better? Anything else? | |
| Aug 10, 2017 at 7:30 | history | edited | Jamie Hanrahan | CC BY-SA 3.0 |
added 948 characters in body
|
| Aug 10, 2017 at 2:41 | history | edited | Jamie Hanrahan | CC BY-SA 3.0 |
added 735 characters in body
|
| Aug 9, 2017 at 22:23 | history | edited | Jamie Hanrahan | CC BY-SA 3.0 |
added 250 characters in body
|
| Aug 9, 2017 at 22:10 | history | edited | Jamie Hanrahan | CC BY-SA 3.0 |
added 6590 characters in body
|
| Aug 9, 2017 at 19:22 | comment | added | Jamie Hanrahan | Oh, there are things to say beyond "it's the Baudot code". | |
| Aug 9, 2017 at 19:05 | comment | added | Jamie Hanrahan | @William-Rem ok. Later today. | |
| Aug 9, 2017 at 18:33 | comment | added | user2357112 | @William-Rem: What do you mean? That's the protocol. Most of this answer is describing the protocol. Are you looking for a name or something? (The character encoding is some variant of the Baudot code.) | |
| Aug 9, 2017 at 17:57 | comment | added | William | This is a great response in terms of detail, but fails to answer the basic question: what protocol do teletypewriters use? If you could update it to include something about the protocol or encoding used, it would be significantly improved. | |
| Aug 9, 2017 at 1:00 | history | edited | Jamie Hanrahan | CC BY-SA 3.0 |
added 550 characters in body
|
| Aug 8, 2017 at 23:18 | history | edited | Jamie Hanrahan | CC BY-SA 3.0 |
added 1249 characters in body
|
| Aug 8, 2017 at 23:11 | history | edited | Jamie Hanrahan | CC BY-SA 3.0 |
added 1249 characters in body
|
| Aug 8, 2017 at 23:00 | history | answered | Jamie Hanrahan | CC BY-SA 3.0 |