Open Bug 1347888 Opened 8 years ago Updated 2 years ago

Remove nsIConverterOutputStream

Categories

(Core :: Internationalization, enhancement, P3)

Product:
Core
Component:
Internationalization
Type:
enhancement

Tracking

()

Project Flags:
Performance Impact none

People

(Reporter: hsivonen, Unassigned)

References

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

Details

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
s/nsIScriptableUnicodeConverter/nsIConverterOutputStream/
Blocks: post-57-api-changes
No longer depends on: post-57-api-changes
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&regexp=false&path=
Depends on: 1353285
(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-]
Priority: -- → P3
Performance Impact: --- → -
Whiteboard: [qf-]
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.