Henri Sivonen (:hsivonen) (away from Bugzilla until 2023-09-11) Reporter
	Description • 7 years ago

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

	Henri Sivonen (:hsivonen) (away from Bugzilla until 2023-09-11) Reporter
	Comment 1 • 7 years ago

s/nsIScriptableUnicodeConverter/nsIConverterOutputStream/

	:aceman
	Comment 2 • 7 years ago

This is used in calendar, mail and mailnews.
Do the proposed replacement have the feature of the "converter" for converting characters between charsets?

	Jorg K (CEST = GMT+2)
	Comment 3 • 7 years ago

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&regexp=false&path=

	Henri Sivonen (:hsivonen) (away from Bugzilla until 2023-09-11) Reporter
	Comment 4 • 7 years ago

(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.