rt
rt copied to clipboard
bestpractical
Decode MIME headers for better readability in web interface.
Hi,
this change "Subject: =?UTF-8?B?UMWZa....." to readable version.
Cheers Petr
I'm not sure we actually want this behaviour. It is often useful to see exactly what RT sent out, and munging that on display means you then need to go poking through the database.
On Thu, Nov 8, 2012 at 10:14 PM, Thomas Sibley [email protected]:
I'm not sure we actually want this behaviour. It is often useful to see exactly what RT sent out, and munging that on display means you then need to go poking through the database.
Good variant is to put a tag around with decoded value in title attribute so decoded value can be seen on mouse over.
— Reply to this email directly or view it on GitHubhttps://github.com/bestpractical/rt/pull/42#issuecomment-10198556.
Best regards, Ruslan.
It would be nice that ordinary user can read subject and sender of outgoing messages. Especialy in non-ascii countries. Admins can change preferences to show raw headers.
http://git.io/oY9CCw
I like @ruz idea. You can see the decoded and encoded version without switching a config option.
On 11/09/2012 06:27 AM, Petr wrote:
It would be nice that ordinary user can read subject and sender of outgoing messages. Especialy in non-ascii countries. Admins can change preferences to show raw headers.
Ordinary users generally don't scan through full email headers to find the Subject and recipients/sender.
I don't think this warrants a config option or user preference. I prefer @ruz's suggestion.
On 12/13/2012 05:06 AM, Petr wrote:
After a month, nothing happened.
We're a busy team. Not everything gets dealt with within a month. :)
I agree that it would be useful to have some sort of decoding of headers, and I think the tooltip solution is a good compromise. It requires someone with a little bit of time to do some testing, but otherwise it should be a shoo-in for the RT 4.2 series (master branch currently).
Looking at your latest patch more closely, my main concern is that it runs decode("MIME-Headers", ...) over the entire header block, rather than on individual headers.