Re: Future of cctalk/cctech - text encoding
On 6/24/2020 12:06 PM, jim stephens via cctalk wrote: On 6/24/2020 10:02 AM, Curious Marc via cctalk wrote: But I would strongly suggest that we limit it to using characters from the Baudot set. If not they don’t print right on my 1930 Teletype. I can peruse the list on my Teletype ASR-32(s). Can archive the list with the 5 level paper tape (at least till the three rolls of tape run out). Well if you can trim the posts,and remove sigs,I bet you can don't need to buy more rolls until the next 5 years. Are there still places that sell paper tape and paper rolls? Ben.
Re: Future of cctalk/cctech - text encoding
On 6/24/2020 10:02 AM, Curious Marc via cctalk wrote: But I would strongly suggest that we limit it to using characters from the Baudot set. If not they don’t print right on my 1930 Teletype. I can peruse the list on my Teletype ASR-32(s). Can archive the list with the 5 level paper tape (at least till the three rolls of tape run out).
Re: Future of cctalk/cctech - text encoding
Someone whose name might be Marc might have written: Peter Coghlan wrote: Does anyone use ASCII anymore? >>> >>> I read and write my email with Emacs running in a terminal emulator. >>> I rarely need anything beoynd codepoint 126. >> >> I vote we move the list to an Exchange server behind a SSL VPN and mandate >> the use of Outlook, then force all messages to be in quoted-printable >> encoding. This way nobody “wins” and everyone is equally miserable. >> It’s only fair. > C'mon, quoted-printable is usually fairly readable. How about base-64? Or if this is regarded as too modern or too universal, how about uuencoding? > > +1 on the Exchange server. You might even be able to have more than 2 people > connected to it at the same time without crashing, if you put enough admins > on the problem. > You can't use an Exchange server. I believe Exchange servers silently discard messages whose message-id it has previously seen. This would solve (actually hide) the duplicated messages problem and we can't have that! > > But I would strongly suggest that we limit it to using characters from the > Baudot set. If not they don’t print right on my 1930 Teletype. > > Also Darwin recently wrote a paper about us, and revoked his theory of > evolution. > > Unlike the God-awfull Yahoo Groups, Groups.io works OK for the other lists > I follow. Meaning it’s functional and tolerable, and only moderately > infuriating. But it is certainly not as clean and efficient as this list > by a good margin. It would be good if we could preserve this. > > Maybe evolve to the use of pictures or attachments, just to prove Darwin > wrong? Limited to ASCII art only pictures, of course. > Hang on, what about those who prefer their art in upper case EBCDIC only? Regards, Peter Coghlan > > Marc
Re: Future of cctalk/cctech - text encoding
>>> Peter Coghlan wrote: >>> Does anyone use ASCII anymore? >> >> I read and write my email with Emacs running in a terminal emulator. >> I rarely need anything beoynd codepoint 126. > > I vote we move the list to an Exchange server behind a SSL VPN and mandate > the use of Outlook, then force all messages to be in quoted-printable > encoding. This way nobody “wins” and everyone is equally miserable. It’s only > fair. +1 on the Exchange server. You might even be able to have more than 2 people connected to it at the same time without crashing, if you put enough admins on the problem. But I would strongly suggest that we limit it to using characters from the Baudot set. If not they don’t print right on my 1930 Teletype. Also Darwin recently wrote a paper about us, and revoked his theory of evolution. Unlike the God-awfull Yahoo Groups, Groups.io works OK for the other lists I follow. Meaning it’s functional and tolerable, and only moderately infuriating. But it is certainly not as clean and efficient as this list by a good margin. It would be good if we could preserve this. Maybe evolve to the use of pictures or attachments, just to prove Darwin wrong? Limited to ASCII art only pictures, of course. Marc
Re: Future of cctalk/cctech - text encoding
On 6/18/20 7:34 AM, Daniel Seagraves via cctalk wrote: I vote we move the list to an Exchange server behind a SSL VPN and mandate the use of Outlook, then force all messages to be in quoted-printable encoding. I see your quoted-printable and raise you TNEF. This way nobody “wins” and everyone is equally miserable. It’s only fair. Are you listening to "The Trees" from Rush? -- Grant. . . . unix || die
Re: Future of cctalk/cctech - text encoding
> On Jun 18, 2020, at 4:03 AM, Lars Brinkhoff via cctalk > wrote: > > Peter Coghlan wrote: >> Does anyone use ASCII anymore? > > I read and write my email with Emacs running in a terminal emulator. > I rarely need anything beoynd codepoint 126. I vote we move the list to an Exchange server behind a SSL VPN and mandate the use of Outlook, then force all messages to be in quoted-printable encoding. This way nobody “wins” and everyone is equally miserable. It’s only fair.
Re: Future of cctalk/cctech - text encoding
Peter Coghlan wrote: > Does anyone use ASCII anymore? I read and write my email with Emacs running in a terminal emulator. I rarely need anything beoynd codepoint 126. I hear MIT-MC is a popular host for mailing lists. Remind me, is ARPANET still up and running?
Re: Future of cctalk/cctech - text encoding
Christian Corti wrote: On Wed, 17 Jun 2020, ben wrote: > Does this mailing list have people using EBCDIC for example? Yes, if for example I use Kermit on the IBM 5110 and connect to a UNIX host. ;-) But in this case, my Kermit is doing the translation between ASCII and EBCDIC. Does anyone use ASCII anymore? Most of the emails I get now are marked as utf-8 with the occasional iso-8859-1. Regards, Peter Coghlan. Christian
Re: Future of cctalk/cctech - text encoding
On Wed, 17 Jun 2020, ben wrote: Does this mailing list have people using EBCDIC for example? Yes, if for example I use Kermit on the IBM 5110 and connect to a UNIX host. ;-) But in this case, my Kermit is doing the translation between ASCII and EBCDIC. Christian
Re: Future of cctalk/cctech - text encoding
Although I am using a larger drive, I would prefer that we not have any messages that wouldn't be possible to fit on an 8" SSSD disk. On Wed, 17 Jun 2020, ben via cctalk wrote: Does that include the TAG LINE? I am happy just to have ASCII text, and trimmed messages. Does this mailing list have people using EBCDIC for example? What would be useful is a way to transfer things like paper tape or punch card deck. What I would like to see, is an available FILES web location, where people could put their "please ID this" pictures, and other worthwhile files. But, links, NOT content, sent out in the email! If there is enough cheap space, maybe even stuff like the GWBASIC stuff. Q: is the original Microsoft BASIC paper tape released from copyright, yet? Once the plain text rule is lifted, we are likely to also no longer get ANY trimming of messages, and every post will include everything that ever came before. All the way back to THIS.
Re: Future of cctalk/cctech - text encoding
On 6/17/2020 2:35 PM, Fred Cisin via cctalk wrote: Although I am using a larger drive, I would prefer that we not have any messages that wouldn't be possible to fit on an 8" SSSD disk. Does that include the TAG LINE? I am happy just to have ASCII text, and trimmed messages. Does this mailing list have people using EBCDIC for example? What would be useful is a way to transfer things like paper tape or punch card deck. Ben.
