Order Tray | Contact Us | Home | SIG Lists

[linux] Re: Take a Stand

John Koster w9ddd at tapr.org
Wed Oct 13 03:30:54 UTC 2004


I was kind of wondering about that myself.  5 bits will give you 32
combinations.  26 letters plus 0-9 would be 36 code required.  What are we
missing Darryl?  And then what are the two extra odd bits for?

John Koster, W9DDD
<w9ddd at tapr.org>


On Tue, 12 Oct 2004, Martin Ewing wrote:

>
> --- Darryl Smith <Darryl at radio-active.net.au> wrote:
>
> > Now, callsigns are up to 7 alpha-numeric characters,
> > meaning 37 bits.
>
> Am I supposed to understand how you encode callsigns
> with 5.28 bits per character?  Because I don't!
> Myself, I'd prefer 8 bits per character, to make it
> easy to manipulate & print, etc. Why not allow more
> characters for foreign/portable/etc.?
>
> I don't suppose callsigns are going to Unicode (16
> bits) any time soon.  Maybe ASCII (8 bits) is
> acceptable, or even 'BCD' (6 bits).
>
> Inquiring minds...
> 73 - Martin, AA6E
>
>
> _______________________________________________
> linux mailing list
> linux at lists.tapr.org
> https://lists.tapr.org/cgi-bin/mailman/listinfo/linux
>





More information about the linux mailing list