Remove nsIConverterOutputStream

NEW
Unassigned

Status

()

Core
Internationalization
P3
normal
a year ago
10 months ago

People

(Reporter: hsivonen, Unassigned)

Tracking

(Depends on: 1 bug, Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [qf-])

(Reporter)

Description

a year 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
(Reporter)

Comment 1

a year ago
s/nsIScriptableUnicodeConverter/nsIConverterOutputStream/

Updated

a year ago
Blocks: 1347507
No longer depends on: 1347507

Comment 2

a year ago
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

a year 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=
(Reporter)

Updated

a year ago
Depends on: 1353285
(Reporter)

Comment 4

a year 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.
Whiteboard: [qf]
Whiteboard: [qf] → [qf-]

Updated

10 months ago
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.