At the very bottom of the Message Display preferences contains the following text: Use the following character coding as the default for viewing messages: and that's it. It looks like it goes along with the Character Coding preference in the Composition preference. Jennifer, the preferences spec is out of date on this one. Let me know where it should be moved to or simply removed. Please reassign this bug to me when we know what we want to do with this text.

Is it being cropped?

Looks fine to me too.

In order to triage this bug I reviewed current Pref Spec and checked implementation on Netscape 7.01. I see that Sean raised the issue with a bit of overlapping showing 'Character Coding' in 'Message Display' and in 'Composition' - both under Mail&Newsgroups Pref. Our Spec http://www.mozilla.org/mailnews/specs/prefs/Preferences.html#MnN does not show 'Languages' area in 'Message Display'. Neither 'Character Coding' in 'Composition'. Jennifer, your call here. May be just Spec?

Plan is to eventually clean up prefs and move the language related items to their own panel: http://www.mozilla.org/mailnews/specs/prefs/Preferences.html#Display http://www.mozilla.org/mailnews/specs/prefs/Preferences.html#Lang Until prefs are updated, is the cropping still visible in the current implementation?

MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614

MASS-CHANGE: This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago. Because of this, we're resolving the bug as EXPIRED. If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component. Query tag for this change: EXPIRED-20100420