[Tickets #9475] Re: printing messages

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/9475
------------------------------------------------------------------------------
  Ticket             | 9475
  Updated By         | rsalmon at mbpgroup.com
  Résumé             | printing messages
  Queue              | IMP
  Version            | Git master
  Type               | Enhancement
  État               | Feedback
  Priorité           | 1. Low
  Milestone          |
  Patch              |
  Propriétaire       |
+New Attachment     | print.zip
------------------------------------------------------------------------------


rsalmon at mbpgroup.com (2011-01-06 04:20) wrote:

> To expand on this - give me an example of a message where there is  
> more than one inline part that needs to be printed?  In almost every  
> case, there is *ONE* part of the message that needs to be printed.   
> So in almost every case, clicking print for a part is exactly what  
> is intended.
I didn't have in mind multi part messages. I'll come back to you on  
this one later on.

What an end user will expect, is it to be able to print (at least) a  
simple message (only one part). And not just the body of the message  
but the header as well: info like From, To, Date.

The attached example is a single part only message (sent to the dev  
list) and will illustrate what we expect (I hope).

git-DIMP : using git DIMP, I doubled clicked on the message and use  
the print function of the browser (in my case FF).
old-DIMP: using an older version and the provided print function.
yahoo: I redirected the message and used the provided print function.
gmail: I redirected the message and used the provided print function.

To me, the better looking output is old-DIMP.pdf. It has what anyone  
can expect the header and the body of the message.

The git-DIMP output doesn't print the full message. We can see as well  
buttons like Reply, Forward, Delete...