Re: Guessing the encoding of a test file... [OT]

2020-03-20 Thread doc hawk via use-livecode


On Mar 20, 2020, at 4:04 PM, Mark Wieder via use-livecode 
 wrote:
> 
> Even Morse code got a new character recently.

But does livecode support that character?

:)
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Guessing the encoding of a test file... [OT]

2020-03-20 Thread Mark Wieder via use-livecode

On 3/20/20 1:47 PM, doc hawk via use-livecode wrote:


They created a *new* five bit, shifted code, rather than just using Baudot


Even Morse code got a new character recently.

--
 Mark Wieder
 ahsoftw...@gmail.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


RE: Guessing the encoding of a test file... [OT]

2020-03-20 Thread Ralph DiMola via use-livecode
It was essentially Baudot on the way in(some special char diffs) then
shifted to numeric on the way out. As I remember the shifted numeric was not
any of the existing Baudot variants. Alpha Stock symbols in and numeric
stock quotes out. If I remember correctly the first 2 chars selected a head
on a magnetic drum and then waited for the last chars match on that head.
Every user just had a new card plugged in. Reponses time was not user
dependent. 1 user or 1k users. A query just had to wait for rotational
latency.


Ralph DiMola
IT Director
Evergreen Information Services
rdim...@evergreeninfo.net


-Original Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf
Of doc hawk via use-livecode
Sent: Friday, March 20, 2020 4:48 PM
To: How to use LiveCode
Cc: doc hawk
Subject: Re: Guessing the encoding of a test file... [OT]


On Mar 20, 2020, at 12:51 PM, Ralph DiMola via use-livecode
 wrote:
> 
> Just for a laugh... one of the more esoteric codings I used in the quasi
modern error (besides EBCDIC) was the 5 bit Quotron stock ticker system in
the mid 90s. It used different codes for requesting/receiving quotes because
2^5 is only 32 possible characters. Alpha in/numeric out.

They created a *new* five bit, shifted code, rather than just using
Baudot


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Guessing the encoding of a test file... [OT]

2020-03-20 Thread Paul Dupuis via use-livecode

On 3/20/2020 4:47 PM, doc hawk via use-livecode wrote:

On Mar 20, 2020, at 12:51 PM, Ralph DiMola via use-livecode 
 wrote:

Just for a laugh... one of the more esoteric codings I used in the quasi modern 
error (besides EBCDIC) was the 5 bit Quotron stock ticker system in the mid 
90s. It used different codes for requesting/receiving quotes because 2^5 is 
only 32 possible characters. Alpha in/numeric out.

They created a *new* five bit, shifted code, rather than just using Baudot




From a guessEncoding perspective, you just scan the bytes and if all 
byte values are in the 0-31 range, you have a 5-bit code.


Then it get harder to determine whether it is Quotron or Baudot...


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Guessing the encoding of a test file... [OT]

2020-03-20 Thread doc hawk via use-livecode


On Mar 20, 2020, at 12:51 PM, Ralph DiMola via use-livecode 
 wrote:
> 
> Just for a laugh... one of the more esoteric codings I used in the quasi 
> modern error (besides EBCDIC) was the 5 bit Quotron stock ticker system in 
> the mid 90s. It used different codes for requesting/receiving quotes because 
> 2^5 is only 32 possible characters. Alpha in/numeric out.

They created a *new* five bit, shifted code, rather than just using Baudot


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


RE: Guessing the encoding of a test file... [OT]

2020-03-20 Thread Ralph DiMola via use-livecode
Just for a laugh... one of the more esoteric codings I used in the quasi modern 
error (besides EBCDIC) was the 5 bit Quotron stock ticker system in the mid 
90s. It used different codes for requesting/receiving quotes because 2^5 is 
only 32 possible characters. Alpha in/numeric out.
 
Ralph DiMola
IT Director
Evergreen Information Services
rdim...@evergreeninfo.net

-Original Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of 
doc hawk via use-livecode
Sent: Friday, March 20, 2020 2:13 PM
To: How to use LiveCode
Cc: doc hawk
Subject: Re: Guessing the encoding of a test file...


On Mar 20, 2020, at 11:09 AM, Paul Dupuis via use-livecode 
 wrote:
> 
> Okay, now you going for the low blow :-)\

What part of “lawyer” wasn’t clear? B b

:_)


> Next, you'll be suggesting I need to check for EBCDIC encodings!

That will be a start, but it’s not done until you include Baudot.

Morse, however, is optional . . .
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode