That's all very well, but...
> a) The "callsign" ISN'T an aircraft registration code. You need only
> look at the MP to see that. Some people use an aircraft-rego-like code
> (like me, zk-jrs), but others don't. Some use their name. When was the
> last time you saw "Joe Bloggs" as a callsig
On 30/03/10 21:17, Pete Morgan wrote:
>
> When is the last time an aircraft landed at EGLL with the callsign $%%% ?
> And what "language" do ATC use to communicate...?
>
> what I'm suggesting is that should not be allowed, ie
> fgfs --callsign=$%%% should throw an error on startup.
>
>
That's a
James Sleeman wrote:
> On 30/03/10 14:47, Pete Morgan wrote:
>
>> I'm playing with an MP map, and have bumped into some issues with
>> callsign's containing strange characters (can mess with json encoding).
>>
>>
> I'd suggest the MPMap should be fixed so that user data doesn't create
On Tue, Mar 30, 2010 at 12:47 PM, Pete Morgan wrote:
> I'm playing with an MP map, and have bumped into some issues with
> callsign's containing strange characters (can mess with json encoding).
>
> Should the callsign not be restricted to the characters "-" and 0-9,
> a-z, A-Z ?
>
> recent notabl
On 30/03/10 14:47, Pete Morgan wrote:
> I'm playing with an MP map, and have bumped into some issues with
> callsign's containing strange characters (can mess with json encoding).
>
I'd suggest the MPMap should be fixed so that user data doesn't create
an issue for it, I can't see why arbitrar
I'm playing with an MP map, and have bumped into some issues with
callsign's containing strange characters (can mess with json encoding).
Should the callsign not be restricted to the characters "-" and 0-9,
a-z, A-Z ?
recent notable examples online
$bling%
$%^
kind regards
pete
-
6 matches
Mail list logo
