<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
Bob,
<div><br>
</div>
<div>So if I submit a proposal for symbol assignments to you and update the UI-View icon files to match and send them to Steve for posting, would that at least get things rolling?
<div></div>
<div><br>
</div>
<div>Andrew, KA2DDO</div>
</div>
<br>
<br>
-------- Original message --------<br>
From: Robert Bruninga <bruninga@usna.edu> <br>
Date:08/28/2014 11:04 (GMT-05:00) <br>
To: TAPR APRS Mailing List <aprssig@tapr.org> <br>
Cc: <br>
Subject: Re: [aprssig] New icon images <br>
<br>
<div class="BodyFragment">
<div class="PlainText">Actually, the symbol space has been opened up form the original 100 or so<br>
to thousands (by judicious use of "overlay" characters on a basic set of<br>
symbols. This is backwards compatible. Those with older systems see the<br>
base symbol with the overlay character, those with newser systems "can"<br>
see any new specially drawn symbols that matches that unique combination<br>
of base symbol and overlay. See some of the examples on<br>
<a href="http://aprs.org/symbols.html">http://aprs.org/symbols.html</a><br>
<br>
Follow the link to symbols-new.txt and you will see several of these<br>
expansions. As many as a dozen different symbol definitions for some of<br>
the basic symbols.<br>
<br>
The PROBLEM is that now it takes a massive effort by software developers<br>
to render actual images to match these new definitions. And to keep<br>
current, which is a daunting task. But at least the "symbol space" is<br>
available to contain these thousands of new possibilities. In other<br>
words, I accommodated it in the spec and simply passed the buck to the<br>
code writers...<br>
<br>
Bob, WB4APR<br>
<br>
<br>
-----Original Message-----<br>
From: aprssig-bounces@tapr.org [<a href="mailto:aprssig-bounces@tapr.org">mailto:aprssig-bounces@tapr.org</a>] On Behalf<br>
Of Steve Dimse<br>
Sent: Thursday, August 28, 2014 9:08 AM<br>
To: TAPR APRS Mailing List<br>
Subject: Re: [aprssig] New icon images<br>
<br>
<br>
On Aug 28, 2014, at 5:57 AM, Andrew P. <andrewemt@hotmail.com> wrote:<br>
<br>
> Uh, isn't that why Kenwood makes firmware upgrades available on their<br>
website?<br>
><br>
The original Kenwoods have to be opened and programming cable soldered<br>
onto the circuit board to update the firmware. The circuit board was a<br>
design that Kenwood had developed but never released for the Japanese<br>
market. It was obsolete even before it was released in the late 90s! After<br>
its release there were so many bugs Kenwood had to issue one, but it was a<br>
headache, you either had to send it to them or go to one of the few<br>
hamfests to which they sent techs, in which case they could flash it while<br>
you waited. I'm sure they are not going to do that again!<br>
<br>
> In any case, what is the mechanism for proposing symbol code assignments<br>
for these meanings, and which meanings are important enough to get added?<br>
><br>
The APRS Working Group, which these days is down to Bob. I suspect he does<br>
not want to open the floodgates as there have been many, many proposals<br>
over the years of individuals that wanted a symbol, and of course there<br>
are only a few unassigned. Unless it is something with widespread ham<br>
appeal I suspect he isn't going to act.<br>
<br>
I think a backward compatible extended symbol space is your best bet, then<br>
everyone can add all the symbols they want.<br>
<br>
Steve K4HG<br>
_______________________________________________<br>
aprssig mailing list<br>
aprssig@tapr.org<br>
<a href="http://www.tapr.org/mailman/listinfo/aprssig">http://www.tapr.org/mailman/listinfo/aprssig</a><br>
_______________________________________________<br>
aprssig mailing list<br>
aprssig@tapr.org<br>
<a href="http://www.tapr.org/mailman/listinfo/aprssig">http://www.tapr.org/mailman/listinfo/aprssig</a><br>
</div>
</div>
</body>
</html>