1347888 - Remove nsIConverterOutputStream

Status: NEW

(Core :: Internationalization, enhancement, P3)

Description

[Henri Sivonen (:hsivonen)]

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

Comment 1

[Henri Sivonen (:hsivonen)]

s/nsIScriptableUnicodeConverter/nsIConverterOutputStream/

Comment 2

[:aceman]

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

Comment 3

[Jorg K (CEST = GMT+2)]

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=

Comment 4

[Henri Sivonen (:hsivonen)]

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