[aprssig] Re: [CA APRS] Re: Puzzled
AE5PL Lists HamLists at ametx.comTue Sep 21 23:34:44 UTC 2004
- Previous message: [aprssig] Re: [CA APRS] Re: Puzzled
- Next message: [aprssig] Re: [CA APRS] Re: Puzzled
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Some applications are not intolerant of those characters because of the packet mangling that has occurred over the years. Nowhere in the specification, to my knowledge, does it say that these are case intolerant. They are not case insensitive in NMEA strings. I believe UI-View, APRS+SA, javAPRS, and others sanity check these characters; so no, making them lower case is not backwards compatible. 73, Pete Loveall AE5PL mailto:pete at ae5pl.net > -----Original Message----- > From: Bob Bruninga > Posted At: Tuesday, September 21, 2004 6:22 PM > Subject: [aprssig] Re: [CA APRS] Re: Puzzled > > > My guess is the lowercase 'n' in the position. Should be uppercase. > > APRS programs are supposed to be tolerant of both cases for > the N/S byte. Hence a few years ago it was prposed that the > > This was proposed for APRS a year or so ago and some APRS > programs have implemented it since all programs are supposed > to be indifferent to case in that byte anway. Thus it should > be fully backwards compatible. > > But maybe we have found somne applications that are not > intolerant to that byte?
- Previous message: [aprssig] Re: [CA APRS] Re: Puzzled
- Next message: [aprssig] Re: [CA APRS] Re: Puzzled
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the aprssig mailing list
