User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; GTB7.3; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; .NET4.0C; .NET4.0E; msn OptimizedIE8;FRBE) Steps to reproduce: Thunderbird version 11, does not save a file signature.HTML In version 10 it is OK Thunderbird en version 11, ne permet pas de sauvegarder une signature en fichier.HTML Alors que en version 10 c'est OK

Does it works in safe-mode ? Anything in Tools -> Error console when this happens ? could you try to described how you do and what you do to have it nor working something like : 1) I do this 2) and then that etc ...

(In reply to Ludovic Hirlimann [:Usul] from comment #1) > Est-ce cela fonctionne en mode sans échec? Quelque chose dans Outils - > Console d'erreur> lorsque cela se produit? pourriez-vous essayer de vous > décrit comment faire et ce que vous faites de l'avoir, ni de travailler à > quelque chose comme: 1) Je le fais 2) et alors que, etc ... I do know the language English!It is for this that I do not perfectly filled boxes required. I use Thunderbird 11.0.1 for messages. I desire to do a file in HTML format to add a personal signature. When I do "Save as" and then "file" I know not save in HTML format Thank you for your response. Pascal.Margo@Skynet.be Je ne connait pas la langue anglaise!!c'est pour cela que je ne remplis pas parfaitement les cases demandees. J'utilise Thunderbird 11.0.1 pour les messages. Je desire faire un fichier au format HTML pour ajouter une signature personnelle. Quand je fais "enregistrer comme" et ensuite "fichier" je ne sais pas enregistrer en format HTML Merci de votre reponse. pascal.margo@skynet.be

salut, il me semble que tu as déjà trouvé la response sur http://www.geckozone.org/forum/viewtopic.php?f=4&t=104227&p=685067&hilit=signature+html#p685067 non ? je ne comprend toujours pas ce que tu veux, même après avoir lu la discussions sur le forum de geckozone.

I think Pascal is trying to save HTML composition directly from composition window, and for cases of bug 414299, Format:Auto-Detect ignores a lot of HTML tags and considers the msg to be plaintext. As a result, and very confusing, there can be HTML tags in the composition, but we don't offer direct saving of draft as HTML (missing entries in file types list of "save as..."-dialogue), only saving as Text, as described in bug 414299, comment 111. The workaround is to save the draft from main 3pane instead, where for exactly same msg, save as HTML will be enabled. Not very intuitive, and violating ux-consistency.

Per comment 5, this is a bug which should be confirmed, after adding better steps or writing up new report for more clarity.

Confirming per comment 5: STR for this bug (from Bug 414299 Comment 111): Format:Auto-Detect also prevents users from saving their HTML compositions in HTML format *directly from composition window*, for all cases of this bug where auto-detect does dataloss conversion to text/plain (<tt>, <pre>, and many other tags listed in comment 108, including their style attributes). STR: 1 Compose msg with TB default settings 2 add <tt>, <pre>, or any tags of bug 414299 comment 108 with or without style attributes; alternatively, use Bug 414299 testcase 2 from attachment 633907 [details], as depicted in screenshot attachment 633908 [details]. 3 File > Save (from composition window) 4 File > Save as > File (from composition window) 5 select saved draft msg in main 3pane mail win, then File > Save as > File Actual result after 4: Dialogue: "Save TEXT as..." available file types for saving: Text files | All files File type "HTML files" is missing - but there is a lot of HTML in user's composition... So the result is probably useless plaintext garbage as depicted in screenshot attachment 633910 [details]. after 5: Dialogue: "Save Message as..." file types for saving: Mail files | HTML files | Text files | All files Expected result after 4: Dialogue: "Save message as..." file types for saving: Mail files | HTML files | Text files | All files default type: Mail files The difference between 4 and 5 is clearly violating ux-consistency: There is no good reason why saving saved draft behaves so different from saving current composition. If there's a single HTML tag in composition, we need to offer save as HTML, too.

Removing myslef on all the bugs I'm cced on. Please NI me if you need something on MailNews Core bugs from me.