[aprssig] spaces in object names

[Andrew Rich (Home)]

I work alot with RADAR protocols

It is amazing how one manufacturer will interpret a spec


----------------------------------------------------------
Andrew Rich 
Amateur Radio Callsign VK4TEC
email: vk4tec at tech-software.net
web: www.tech-software.net
  ----- Original Message ----- 
  From: Joel Maslak (N7XUC) 
  To: TAPR APRS Mailing List 
  Sent: Sunday, August 16, 2009 12:42 PM
  Subject: Re: [aprssig] spaces in object names


  On Sat, Aug 15, 2009 at 4:43 AM, Tapio Sokura <oh2kku at iki.fi> wrote:


    I can't resist dipping my spoon into the broth:


  Me either...

   
    Some people here seem to be hung on the definition of printable and non-printable. There's an easy fix to that: explicitly define what byte values are acceptable in the spec.


  Agreed.  I'd also remind everyone of the basic network programming tenet: "Be conservative in what you send, liberal with what you accept."

  I am absolutely against removing leading spaces or collapsing spaces in objects received by a station.  I think modifying the original sender's object names is a very dangerous thing to do indeed.  As for software allowing these things to be sent, that I don't care about either way - so long as we don't modify what gets sent.  Remember MIC-E translation?



------------------------------------------------------------------------------


  _______________________________________________
  aprssig mailing list
  aprssig at tapr.org
  https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig



------------------------------------------------------------------------------



  No virus found in this incoming message.
  Checked by AVG - www.avg.com 
  Version: 8.5.392 / Virus Database: 270.13.58/2305 - Release Date: 08/15/09 18:10:00
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20090816/6264735a/attachment.html>