{ "numMessagesInTopic": 9, "nextInTime": 2033, "senderId": "_30wBl9oHLjkyOSwtSSP153CvSek5i9GykqK80_y2U5t1aCrpGQm0ROcdqwB7P7ZcYoCexXCb3f5JOix3BJqoCpsq9_V", "systemMessage": false, "subject": "Re: Manuals", "from": ""Doug" <doug-gray@...>", "authorName": "Doug", "msgSnippet": "I dont think the manual is terrible, But If radio shack wants to increase sales on there scanner at year end the could have typo (transposed letters) counting", "msgId": 2032, "profile": "dougjgray", "topicId": 2001, "spamInfo": { "reason": "12", "isSpam": false }, "replyTo": "LIST", "userId": 225865790, "messageBody": "
--- In Pro-97@yahoogroups.com, Clark <c.rennie1@v...> wrote:
\n>
\n> I don't understand why so many people complain that a manual
\n> is "poorly written" when the main purpose of any manual is to
\nexplain the
\n> operation
\n> of that particular scanner model and not to explain all the
\nintricacies of
\n> scanning.
\n> Trunking is complex and is a whole different operation.
\n>
\n> So many people expect that by purchasing a trunking scanner, it
\nwill be
\n> easy to track a trunk system, and the entire
\n> theory of all of the different type of systems should be explained
\nin the
\n> manual.
\n>
\n> Also many people jump around in reading the manual and then say
\nthe manual
\n> doesn't cover a certain
\n> operation, when it does.
\n>
\n> Clark
\n>
\n>
\n>
\n> [Non-text portions of this message have been removed]
\n>