-
Notifications
You must be signed in to change notification settings - Fork 260
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Decode MIME headers for better readability in web interface. #42
base: stable
Are you sure you want to change the base?
Conversation
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]:
Best regards, Ruslan. |
…outgoing messages.
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. |
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:
Ordinary users generally don't scan through full email headers to find I don't think this warrants a config option or user preference. I |
Not optimal in my opinion, but better than nothing. |
Why did you close this request without the commit being merged? |
After a month, nothing happened. |
On 12/13/2012 05:06 AM, Petr wrote:
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 Looking at your latest patch more closely, my main concern is that it |
This allows us to remove the ugly code in ShowLink and make it ugly in here instead. This means that Formats which say __RefersTo__ or __HasMember__ will now say "ticket #42: Ticket Subject" rather than the current state of the world where that renders as "ticket #42" which is not helpful. The code in rt.pm's AsString is ugly because it assumes that you might use this on some non-RT::Ticket object. That never really happens, but all of this code pretends it might happen so I kept up the illusion.
It looks really odd that we say 'ticket' but every other link type is ucfirsted. However, we rely on that hardcoded lowercase 'ticket' (hardcoded in ObjectType) in HREF and other link building code.
Hi,
this change "Subject: =?UTF-8?B?UMWZa....." to readable version.
Cheers
Petr