On Fri, Nov 8, 2013 at 7:26 AM, Joshua Cranmer 🐧 <pidgeo...@gmail.com> wrote: > On 11/7/2013 5:42 AM, Henri Sivonen wrote: >> >> Do Thunderbird developers want to keep decoders that are going away >> from Firefox? These include: > > I don't think any Thunderbird developer is well-informed on the issue of > charsets in email. The only non-web charset I know we need is the IMAP > modified UTF-7 charset (and this is only for conversion of mailbox names in > the IMAP protocol, not for body charsets). Owing to the nature of the > release cycle, any negative impact on the removal of other charsets are > unlikely to be discovered until the next ESR is released (TB 31, unless > someone changes the release structure before then). I'm hoping to be able to > use the same charsets that the encoding standard uses, but I do not know the > impact of that decision.
I suggest we add telemetry for the decoders and don't remove the decoders until the telemetry code has been through a Thunderbird release: https://bugzilla.mozilla.org/show_bug.cgi?id=935453 Before then, it might be worthwhile to #ifdef them out of Firefox builds, though. Do we have a variable that can be used in moz.build files and in #ifdef to filter m-c-resident code depending on whether it is being built as part of an m-c-only build or as a part of a comm-central build? As for the encoders and decoders that are duplicates of Windows-125x decoders, I suggest getting rid of those sooner even if Thunderbird and aliasing the old names the way Encoding Standard does it. -- Henri Sivonen hsivo...@hsivonen.fi http://hsivonen.fi/ _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
