Heh, if clients randomly change character sets than I guess there are a very large number of possible values.
Given that RFC2047 came out in 1996 it's reasonable that people use non-ascii characters in titles given that the means to do it in a compatible way has been around for 17 years. Luke On Thu, Mar 21, 2013 at 12:04 PM, Mark A. Hershberger <m...@everybody.org>wrote: > On 03/21/2013 11:45 AM, Luke Welling WMF wrote: > > On the email title sidetrack, it should not create a 4th way. > > The pedant in me says there are at least two more ways -- different > capitalization for "UTF-8". But your subject line shows another way. > > My client displays all of the subjects the same. > > Jasper, > Mine: =?utf-8?q?Gerrit_Wars=E2=84=A2=3A_a_strategy-guide?= > Yours: =?windows-1252?q?Gerrit_Wars=99=3A_a_strategy-guide?= > MZ's: Gerrit =?UTF-8?B?V2Fyc+KEog==?=: a strategy-guide > Ori: Gerrit =?utf-8?Q?Wars=E2=84=A2=3A_?=a strategy-guide > > Maybe mailman doesn't understand when the encoding doesn't start at the > first character since those are the ones that don't display correctly. > > -- > http://hexmode.com/ > > [We are] immortal ... because [we have] a soul, a spirit capable of > compassion and sacrifice and endurance. > -- William Faulker, Nobel Prize acceptance speech > > _______________________________________________ > Wikitech-l mailing list > Wikitech-l@lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikitech-l _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
