We should remove nsIScriptableUnicodeConverter and have chrome scripts use the same facilities as Web scripts (TextDecoder/TextEncoder) instead of maintaining a parallel XPCOM universe of things. Possible replacement: 1) TextEncoder 2) Wrap result in nsIArrayBufferInputStream 3) NetUtil.asyncCopy to nsIOutputStream
This is used in calendar, mail and mailnews. Do the proposed replacement have the feature of the "converter" for converting characters between charsets?
Looks like there is a little confusion here. This bug is about nsIConverterOutputStream. nsIScriptableUnicodeConverter is covered in bug 1347877 and it offers the conversions. nsIConverterOutputStream seems to be used with UTF-8 on all the call sites I've looked at: http://searchfox.org/comm-central/search?q=nsIConverterOutputStream&case=false®exp=false&path=
(In reply to :aceman from comment #2) > This is used in calendar, mail and mailnews. > Do the proposed replacement have the feature of the "converter" for > converting characters between charsets? Filed bug 1353285.
You need to log in before you can comment on or make changes to this bug.