Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: "David D. Hagood" <wowbagger@sktc.net>
To: Ralf Baechle DL5RB <ralf@linux-mips.org>
Cc: linux-hams@vger.kernel.org
Subject: Re: callsign limit
Date: Thu, 01 Jun 2006 07:04:02 -0500	[thread overview]
Message-ID: <447ED7B2.3070701@sktc.net> (raw)
In-Reply-To: <20060601014047.GB27504@linux-mips.org>

Ralf Baechle DL5RB wrote:
> One of my crazier ideas to deal with the issue of the longer callsigns
> was using a hash value instead.  The probability of colissions is low but
> how to do the reverse mapping from hash to callsign ...
> 
>   Ralf
>

Since a callsign is always from the set [A-Z0-9] (36 chars, 5.2 bits of 
data per character for a naive encoding) could you not simple encode the 
callsign of an otherwise too-long call as 6 bits per character packed 
into the octets, with a specific leading character to indicate 
compression (e.g. '?') - yielding about 8 chars/call.


  reply	other threads:[~2006-06-01 12:04 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-31  9:27 callsign limit stephen
2006-05-31  9:37 ` Hamish Moffatt
2006-05-31 11:03   ` Chuck Hast
2006-05-31 11:19     ` Hamish Moffatt
2006-06-01  1:40       ` Ralf Baechle DL5RB
2006-06-01 12:04         ` David D. Hagood [this message]
2006-06-01 13:25           ` Ralf Baechle DL5RB
2006-06-01 14:31           ` Curt, WE7U
2006-06-01 15:08             ` Ralf Baechle DL5RB
2006-06-01 15:15               ` Curt, WE7U
2006-06-01 18:52                 ` Ralf Baechle DL5RB
2006-06-01 19:33                   ` Thomas Sailer
2006-06-02  2:51               ` Kevin Dawson
2006-06-02  3:47                 ` Hamish Moffatt
2006-05-31 13:05     ` Geoff Blake
2006-06-01 10:34   ` stephen
2006-06-01 10:54     ` Chuck Hast
2006-06-01 13:47       ` Hamish Moffatt
2006-06-01 14:00         ` Geoff Blake
2006-05-31 13:02 ` Matti Aarnio
2006-05-31 13:12   ` Thomas Sailer
2006-05-31 14:02     ` Matti Aarnio
  -- strict thread matches above, loose matches on Subject: below --
2006-05-31 12:12 IT3 Stuart Blake Tener
2006-05-31 12:41 ` Chuck Hast
2006-05-31 13:15 ` Robert Steinhäußer
2006-05-31 14:57   ` Bob Nielsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=447ED7B2.3070701@sktc.net \
    --to=wowbagger@sktc.net \
    --cc=linux-hams@vger.kernel.org \
    --cc=ralf@linux-mips.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox