Received-SPF: neutral (google.com: 193.82.116.20 is neither permitted nor denied by best guess record for domain of owner-rsgb_lf_group@blacksheep.org)
Message-ID: <20070107225140.xhrxt9nhl50kscwg@webmail.versatel.de>
Date: Sun,  7 Jan 2007 22:51:40 +0100
From: uwe-jannsen@versanet.de
To: rsgb_lf_group@blacksheep.org
References: <E1H2rvT-0004dE-TA@www9.emo.freenet-rz.de>
	<20070106011110.2iu4h2bvhswggk4c@webmail.versatel.de>
	<459F6843.10505@freenet.de>
In-Reply-To: <459F6843.10505@freenet.de>
MIME-Version: 1.0
Content-Disposition: inline
User-Agent: Internet Messaging Program (IMP) H3 (4.0.3)
Subject: Re: LF: Re: more castle
Content-Type: text/plain;
	charset=ISO-8859-1;
	format="flowed"
Content-Transfer-Encoding: 7bit
Sender: owner-rsgb_lf_group@blacksheep.org
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org
Status: O

Zitat von Wolf DL4YHF <dl4yhf@freenet.de>:

> Hi Uwe,
>
> Thanks for the observation ...
>
>
>> seems there grows a problem: I cant see any gap btwn the letters
>> C and Q, D and K, K and 4, 4 and U.  but btwn Q and D es U and K
>> the gaps are O.K. so you will find out how to implement the gaps
>> btwn the other letters as well.
>>
> Ok, no problem to add a short gap between *all* letters, and a larger 
> gap between *words*.
> But the result would be very similar to DFCW; while CASTLE doesn't 
> need these spaces in most occasions (where you recognize the begin of 
> a new letter because the first "dash" or "dot" is closest to the 
> reference). For example, having no gap between "C" and "Q" (etc) is 
> no problem - it just saves precious time in the TA business ;-). 
> Anyway for the sake of readability I will add the short gap between 
> *any* combination of letters now to keep things simple.
>
Wolf,
Castle guru Murray/ZL1BPU himself made this concession.
73
Uwe/dj8wx