Win32 (2000-05-11-08 M16) Linux (2000-05-11-08 M16) 1. Launch Messenger using Task|Mail 2. In the Address card, check "Send email as Plain Text" 3. In the Preference|Formatting, check "convert Message into Plain text" 4. Compose a message that contains the following type of text and send it to myself. This message contain plain text and (Plain text) bolded text (bolded text) italic text (italic text) and underscored text (underscored text) 5. View the message Actual result: In the message content, Conversion characters are displayed in the Message pane. (Note the same is displayed in the source page, which is expected) This message contain plain text and *bolded text* (Show bolded) * */italic text/* * _and underscored text_ Expected result: Should display the plain text like this: This message contain plain text and bolded text, italic text and underscored text This occurs on Linux and Win32 Can not test Mac because of bug 38555
ccing pmock since he wrote/has a similar bug #39096.
Changing qa assigned from lchiang to email@example.com. Fenella, (Here are my thoughts on this matter so please don't flame me) I believe this bug is invalid because from the started scenario, you do not specify what your current viewing and display mail preference are set to. Under the Viewing Message and Composing message preference, you have the preferences seting for "Add HTML Styles to structured phrases. For example text contained astrisks as bold" Both preference are enabled by default. With this preference enabled under composing, we will add "plain text tags" to the mail message. For explaination, read bug 16800 and bug 16507 on this feature. When a message that contains "plain text tags" is viewed in seamonkey, it will interpret the tag and display bold text, underline text, and/or italic text when it encounters "plain text tags" surrounding the text. In my bug 39096, I notice I could not disable the composing message preference. This view message preference does work; allowing you to not to display bold, italic or underline. (I'm don't know all the specifics of this feature ... but I'm trying to get a grasp...._
QA Contact: lchiang → pmock
Well, the confusion on my part deepens. According to Ben Bucksch,bug 39096 is invalid because he said "pmock, as pointed out before, there's no way to add HTML style to plain text msgs, so we certainly never do this. This pref is only applicable for sending HTML msgs. In this case and if enabled, I try to recognize *plain text tags* in the HTML content and add HTML styles to them. This is basically an alternative way to mark the text and then format it bold in the HTML editor (of course with the difference, that there are stars in the first case). If not clear, please ask. Also see <http://www.bucksch.org/1/projects/mozilla/16507>. INVALID." Maybe this bug is not invalid. I need to go over bug 16507 more closely.
Peter, I did have the default in the preference, which is the "Add HTML Styles to structured phrase" was checked. I will not feel offended if you or the developer feels this is an invalid and mark it invalid since I am not very expert in this area. But as a user, I don't expect to see the * and the / in my mail when I convert it from HTML to plain text. However, it is OK to see them in the page source though.
Thanks Fenella for your feedback. I guess, I confused what should happens when we convert from HTML->Plain Text or HTML->Plain Text&HTML? In 4.x and 4.0x, we didn't have the feature to Improve HTML to Plain text conversion (bug 16800).
Status: NEW → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → INVALID
From today 5/18 Mail issue meeting, it was decided that bug 39702 is valid. The user pref "mail.send_struct" aka "Convert structured phrases to HTML styles on Send..." is not working correctly. It suppose to turn on/off the conversion from HTML to Plain text where rich text is converted to plain text tags. Example: bold text gets converted to plain text surrounded by astericks. By default the user pref is enabled, so the scenario that is described in this bug report is correct behavior. If Fenella set the user pref to off then it should not have added the plain text tags (astericks, underscores, and slashes). In short, the user preference "mail.send_struct" broken which is bug 39702 (formerly bug 39096). I think we can mark this bug as invalid based on the given scenario results is correct and keep bug 39702 open to fix the user pref. Ack! Jeff, I'm marking this bug as invalid, please re-open if you disagree. /Peter
Verified as invalid.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.