Re: [Mailman-Users] Re: personalization features (was Re: Archive URL in postings (2.1b3))
I just realized it wouldn't need another configuration variable, but just to expand the personalization variable to be 3-way. So now you can set it to "No", "Yes", or "Full Personalization" with the latter meaning to also munge the To header. Seems like a reasonable compromise for MM2.1.
Sounds great. Calling the options "Off", "Body only", and "Body and headers" might be a little clearer for list admins not familiar with the feature set.
-j.
"JS" == Jay Sekora <jay@ccs.neu.edu> writes:
>> I just realized it wouldn't need another configuration
>> variable, but just to expand the personalization variable to be
>> 3-way. So now you can set it to "No", "Yes", or "Full
>> Personalization" with the latter meaning to also munge the To
>> header. Seems like a reasonable compromise for MM2.1.
JS> Sounds great. Calling the options "Off", "Body only", and
JS> "Body and headers" might be a little clearer for list admins
JS> not familiar with the feature set.How about "No", "Yes", and "Yes, with Headers"?
-Barry
- "Barry A. Warsaw" <barry@python.org> [2002-11-06 13:30:33 -0500]:
How about "No", "Yes", and "Yes, with Headers"?
OK, now we're getting into subtleties of UI design which I'm really not qualified to comment on, but hey, I've never let that stop me before... :p
Personally, "Yes" is the setting that I would expect to denote the fullest setting, if it appeared at all. However, I wouldn't really expect it to appear. If I were going to do it, I would use "None", "Body Only", and "Full".
--
John Buttery (Web page temporarily unavailable)
participants (3)
-
barry＠python.org -
Jay Sekora -
John Buttery