This is separated from bug 15017 which is an existing META charset tag is replaced by charset menu selection. However, when you creating new html document in composer and changed charset menu, the html does not put the META charset. Steps of reproduce 1. Open Composer by selecting menu Tasks|Composer 2. Select "character set" menu and change it to Japanese (ISO-2022-JP) 3. Type some Japanese text 4. Select menu File|Save The html document you save does not have META charset. Tested 11-02-08 Win32, Mac, and Linux build.

Accepting, set to M12.

This problem will be resolved if we create META when we create or open a document. If we allow an option of no META charset (as 4.x), we need to set a tag only when that option is not selected. Basically, editor to follow browser's method to determine the charset of the document (spec is not yet available). There are three possibilities. 1) Creation of a blank document - Use the default (in pref). 2) Edit Page - Inherit the charset which was determined by browser 3) Open document - Use the same algorithm as browser to determine the charset (e.g. HTTP charset, META charset, Auto detection...).

Added depends, 7849 - Editor charset encoding menu needs UE implementation.

We need UE spec for editor charset menu first. Moving to M14 for now.

Added [BETA] in summary.

Change OS to ALL

Fix checked in. Also made it undoable.

I tested this in 2000021408 Win32 build. When I changed Character set menu to Japanese (EUC-JP) and do not turn on IME, also type ASCII characters in composer, the META sometimes does not reflect with the character set menu.

> However, when you creating new html document in composer and changed charset > menu, the html does not put the META charset. This is what I fixed (create META charset responding to the charset menu). Selecting a default charset for a new document is another problem. I think Kathy is working on that (not sure if there is a bug for that). Marking this as FIXED and cc to brade.

I verified this in 2000021509 Win32, Mac, and 2000021510 Mozilla Linux build. I found the special case. I filed new bug 27920.