On 11/11/2013 01:33 PM, Joshua Cranmer 🐧 wrote:
By far the easiest solution would be leaving the code in m-c but
#ifdefing it out of Firefox builds. Is there a compelling reason not
to do so? If there is no compelling reason against #ifdefing it out in
m-c, what's the right variable to #ifdef on (needs to work in
moz.build and the preprecessor)?
Actually, I believe you need to keep the x-imap4-modified-utf7
converters in B2G, if you don't want to break Gaia Email's tests. They
use the fakeservers as well, which specifically use this charset.
This is minor/easy breakage for us to fix. I wouldn't keep the code
around for that reason.
(Character-set-wise, all the Gaia e-mail app wants is for
TextEncoder/TextDecoder to conform to the spec.)
Andrew
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
