Re: Future of cctalk/cctech - text encoding

2020-06-25 Thread ben via cctalk
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). 

Re: Future of cctalk/cctech - text encoding

2020-06-24 Thread jim stephens via cctalk
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

Re: Future of cctalk/cctech - text encoding

2020-06-24 Thread Peter Coghlan via cctalk
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

Re: Future of cctalk/cctech - text encoding

2020-06-24 Thread Curious Marc via cctalk
>>> 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

Re: Future of cctalk/cctech - text encoding

2020-06-20 Thread Grant Taylor via cctalk
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

Re: Future of cctalk/cctech - text encoding

2020-06-18 Thread Daniel Seagraves via cctalk
> 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

Re: Future of cctalk/cctech - text encoding

2020-06-18 Thread Lars Brinkhoff via cctalk
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

2020-06-18 Thread Peter Coghlan via cctalk
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

Re: Future of cctalk/cctech - text encoding

2020-06-18 Thread Christian Corti via cctalk
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

2020-06-17 Thread Fred Cisin via cctalk
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

Re: Future of cctalk/cctech - text encoding

2020-06-17 Thread ben via cctalk
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