<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18812">
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2 face=Arial>I work alot with RADAR protocols</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>It is amazing how one manufacturer will interpret a
spec</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV> </DIV>
<DIV>----------------------------------------------------------<BR>Andrew Rich
<BR>Amateur Radio Callsign VK4TEC<BR>email: <A
href="mailto:vk4tec@tech-software.net">vk4tec@tech-software.net</A><BR>web: <A
href="http://www.tech-software.net">www.tech-software.net</A></DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="FONT: 10pt arial; BACKGROUND: #e4e4e4; font-color: black"><B>From:</B>
<A title=jmaslak-aprs@antelope.net
href="mailto:jmaslak-aprs@antelope.net">Joel Maslak (N7XUC)</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=aprssig@tapr.org
href="mailto:aprssig@tapr.org">TAPR APRS Mailing List</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Sunday, August 16, 2009 12:42
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [aprssig] spaces in object
names</DIV>
<DIV><BR></DIV>On Sat, Aug 15, 2009 at 4:43 AM, Tapio Sokura <SPAN
dir=ltr><<A href="mailto:oh2kku@iki.fi">oh2kku@iki.fi</A>></SPAN>
wrote:<BR>
<DIV class=gmail_quote>
<DIV> </DIV>
<BLOCKQUOTE
style="BORDER-LEFT: rgb(204,204,204) 1px solid; MARGIN: 0pt 0pt 0pt 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>I can't resist dipping my spoon into the
broth:<BR></BLOCKQUOTE>
<DIV><BR>Me either...<BR><BR> </DIV>
<BLOCKQUOTE
style="BORDER-LEFT: rgb(204,204,204) 1px solid; MARGIN: 0pt 0pt 0pt 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>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.</BLOCKQUOTE>
<DIV><BR><BR>Agreed. I'd also remind everyone of the basic network
programming tenet: "Be conservative in what you send, liberal with what you
accept."<BR><BR>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?<BR></DIV></DIV>
<P>
<HR>
<P></P>_______________________________________________<BR>aprssig mailing
list<BR>aprssig@tapr.org<BR>https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig<BR>
<P>
<HR>
<P></P><BR>No virus found in this incoming message.<BR>Checked by AVG -
www.avg.com <BR>Version: 8.5.392 / Virus Database: 270.13.58/2305 - Release
Date: 08/15/09 18:10:00<BR></BLOCKQUOTE></BODY></HTML>