Wayne wrote: >I doubt that a ton of effort is going to be spent on this issue >because most of us don't really use that feature often and I, and I'm >sure others, would rather see CTM Dev spend their time improving or >fixing other issues rather than HTML email.
That is a valid point. CTM should definitely work on the issues of greatest concern to its user base. I am curious how many other PM users find the HTML printing problems more than just a minor annoyance. I waste paper and ink with blank printouts, or printouts with more pages than needed. (Yes, I re-use the pages printed with only a header.) Sometimes I find (for example) directions I had printed not ready as I am going out the door. I can learn to live with the problem, but I am not happy. It would be OK to get an error notice or warning which says I have to go to my web browser to print HTML mail. Then at least I'd get what I expect. Also, I do not think it makes CTM look professional to have such an obvious bug. It certainly prevents me from recommending PowerMail to others, even if I keep using it. The problem is too quirky for new users to have to deal with. - Winston >>do you think users would accept this behavior from any other >>mainstream Mac program without complaining? What if Word could not print >>RTF files correctly, since they are not Word format files? > >Of course you picked the wrong file format for the wrong product. ;-) > >RTF is of course a MS creation and was one of the original Word formats >(and still is). > >However, I understand your point. I guess because I've lived with the >limitation for so long and because I tend to view the few HTML email I >want in a web browser, I don't consider this a huge issue. I agree it's >an issue, but not the four-alarm type. > >In all fairness, if you're receiving a lot of HTML and RTF mail, you >really shouldn't use PowerMail. It's an awesome email program, but it's >really designed for text. All the HTML efforts have been limited because >that's not what it was designed to be. > >You really have two options at this point. Either use the workaround of >viewing and printing in a web browser, or switch to another email >client. I doubt that a ton of effort is going to be spent on this issue >because most of us don't really use that feature often and I, and I'm >sure others, would rather see CTM Dev spend their time improving or >fixing other issues rather than HTML email. > >Wayne > >
