API change to consider: SetDocumentCharacterSet

CLOSED WONTFIX

Status

()

defect
P3
normal
CLOSED WONTFIX
20 years ago
3 years ago

People

(Reporter: Brade, Assigned: Brade)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

in nsIEditor.h, we have a method "SetDocumentCharacterSet"
I assume that all this method would do is change the meta tags (without any
actual data conversion).  One of the international requirements has been to allow
users to do both:
 * change the character set without changing data (such as when encountering
mislabeled data)
 * change the character set and convert the data to the new character set (such
as wanting to change from MacRoman to Latin-1)

I think we should either change this api to take a flag on whether to convert the
data or add another method.
CC'ing tague who is working on Editor charset issues.
i'm not sure if changing the api is necessary to support the two user scenarios
outlined above. brade's user scenarios are very valid, but i think the new
charset menu UE might eliminate the problem.

historically, this has been a problem because we have overloaded the meaning of
the charset menu and how it is used -- for seamonkey we are spliting up the
charset menu functionality into two menus a view as/interpret as charset menu and
a save as/converter to charset menu.

i wouldn't worry about this too much until i get some of the new menu
infrastructure into place.  this is an m11 task - if we need to add/revise the
api we can do it then.
Assignee: buster → brade
kathy, you make the call on this with tague's help.  thanks.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → WONTFIX
given Kat's new spec, I agree that this is probably not needed (if the spec is
implemented).  Resolved as WONTFIX.  I'll also verify myself since I filed the
bug.
Status: RESOLVED → CLOSED
You need to log in before you can comment on or make changes to this bug.