We should add a "Save As Encoding..." in editor. It should be hookup under File menu, it will bring up a dialogbox which have one text field for the title (cmanske ask for this), one list box to list all the customized charset, one cancel button and one ok button. After user select the charset, we should change the meta tag charset to that value and bring up a file picker to save the file into that charset.
Status: NEW → ASSIGNED
Target Milestone: --- → M16
Is cmanske signed up for front end work? ftang, is this on the PRD as a must do for beta2? How much work needed to to this?
Whiteboard: [NEED INFO]
No, WE are signed up to do the work. cmanske already review it and I have check them in this afternoon. Mark it fix.
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED
ftang, you can verify this one..I don't see it in 5/12 build.
I wrote the specs for this and so will take this one.
QA Contact: ftang → momoi
** Checked with 5/13/2000 Win32 build ** 1. File: Save as Charset menu --> now exists. (There is a question about the wording. Will file another bug.) 2. Dialog box with 1 text field and 1 charset list box --> they exist. 3. 1 Cancel and 1 OK buttons --> they exist 4. User types in the subject and chooses charset, then press OK --> brings up the Windows file picker dialog. 5. The document meta-charset is correctly reflected and data seem to be correct on some encodings I looked at. So for Windows, this feature has been implemented correctly. There might be some bugs in finer points but if they do, they should be filed as separate bugs.
The featurea as described above for Windows are also working for Linux build (5/16/2000). I'll hand this over to ji for Mac verification. Thanks, ji! Once Mac is done, please mark this feature bug verified.
QA Contact: momoi → ji
Checked 2000051909 Mac build. The feature described above is working on Mac too. Marked as verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.