Open Bug 1347887 Opened 8 years ago Updated 2 years ago

Remove nsIConverterInputStream

Categories

(Core :: Internationalization, enhancement, P5)

Product:
Core
Component:
Internationalization
Type:
enhancement

Tracking

()

Project Flags:
Performance Impact none

People

(Reporter: hsivonen, Unassigned)

References

(Depends on 2 open bugs, 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.
s/nsIScriptableUnicodeConverter/nsIConverterInputStream/
Blocks: post-57-api-changes
No longer depends on: post-57-api-changes
This is still used in calendar, mail and mailnews. Can you please describe what the replacement is?
Priority: -- → P5
(In reply to :aceman from comment #2) > This is still used in calendar, mail and mailnews. > Can you please describe what the replacement is? Filed bug 1353285. (Covers only encode to UTF-8. Please don't do output in legacy encodings.)
(In reply to Henri Sivonen (:hsivonen) from comment #3) > (In reply to :aceman from comment #2) > > This is still used in calendar, mail and mailnews. > > Can you please describe what the replacement is? > > Filed bug 1353285. (Covers only encode to UTF-8. Please don't do output in > legacy encodings.) Oops. This bug is for *input*. TextDecoder works for non-UTF-8 on input, so the same patterns that m-c adopts in bug 1353285 for UTF-8 only could be copied and pasted into c-c and extended for non-UTF-8.
Whiteboard: [qf]
Whiteboard: [qf] → [qf-]
Performance Impact: --- → -
Whiteboard: [qf-]
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.