Composer - Lose my ASCII characters when saving
First up, this is probably an exceptionally stupid question and for that I apologise. I'm new to Seamonkey Composer however and I just can't understand why I'm having trouble adding say © in HTML source view and getting it to STAY when I hit 'Save'. When I do save the document, it reverts in the HTML Source to the copyright symbol. Where's the sense in that? The whole point of manually editing the HTML Source code is that *I* want to dictate what the code should be? Am I missing a setting in preferences or something or will this always be a problem with using Seamonkey to edit HTML? :-( Zoe ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Composer - Lose my ASCII characters when saving
TheFunnySide wrote: First up, this is probably an exceptionally stupid question and for that I apologise. I'm new to Seamonkey Composer however and I just can't understand why I'm having trouble adding say© in HTML source view and getting it to STAY when I hit 'Save'. When I do save the document, it reverts in the HTML Source to the copyright symbol. Where's the sense in that? The whole point of manually editing the HTML Source code is that *I* want to dictate what the code should be? Am I missing a setting in preferences or something or will this always be a problem with using Seamonkey to edit HTML? :-( Zoe Zoe, You are not missing anything unless you don't have that character in your font bank. In place of trying to hand code the character in Composer, place the cursor in the document where you want it to appear, then look in the Insert Character list at the top of the edit screen. Select the Copyright symbol, if you cannot find it you probably don't have that character in your fonts on your system. Another solution is to hand code the numeric code ® into your dcument. Composer had had a bad habit of removing coding it doesn't like or understand. If you want to edit the document use an text editor like TextPad, it doesn't care what you write and will not alter your coding. Michael G ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Composer - Lose my ASCII characters when saving
TheFunnySide schrieb: First up, this is probably an exceptionally stupid question and for that I apologise. I'm new to Seamonkey Composer however and I just can't understand why I'm having trouble adding say© in HTML source view and getting it to STAY when I hit 'Save'. When I do save the document, it reverts in the HTML Source to the copyright symbol. Where's the sense in that? The whole point of manually editing the HTML Source code is that *I* want to dictate what the code should be? Am I missing a setting in preferences or something or will this always be a problem with using Seamonkey to edit HTML? :-( Zoe I just tried, and for me (SM2.2, MacOS X10.6, German locale) it works: - I enter "©" in the source view. - Upon saving, it automatically switches to normal view. Here it shows "©". - Going back to source view, it's still "©". I tried this repeatedly, still works. BTW - if I type "©" in normal/tag view, I get "©" in source view, as you would expect. In Preferences -> Composer there is an option to retain source formatting upon saving. It's off for me, but I remember sometimes being annoyed by that function (rare user of composer, not really the last years for own writing - just for editing). Maybe this might help you. (For arcane reasons, since I have it off - but might be worth the attempt.) Otherwise I checked about:config for search string: "editor". I got only defaults except paths/... and 1 option which is related to "" insertion on "". So, I'd expect this to be the same for you? Just speculating - could this be "font encoding" related? My version chooses "charset=ISO-8859-1" as default. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Composer - Lose my ASCII characters when saving
TheFunnySide wrote: First up, this is probably an exceptionally stupid question and for that I apologise. I'm new to Seamonkey Composer however and I just can't understand why I'm having trouble adding say© in HTML source view and getting it to STAY when I hit 'Save'. When I do save the document, it reverts in the HTML Source to the copyright symbol. Where's the sense in that? The whole point of manually editing the HTML Source code is that *I* want to dictate what the code should be? Am I missing a setting in preferences or something or will this always be a problem with using Seamonkey to edit HTML? :-( Are you sure what you're seeing? Being new to the tool, you may be getting confused by the view changing to NORMAL when you do a save. Also, the relevant modes are NORMAL, PREVIEW (why is that here?), SOURCE, and HTML TAGS. So I'm assuming you mean SOURCE when you say HTML mode. If you could try this it would clarify: - in SOURCE mode create a small document with the "©" in the document - save it in a file - open it with the browser - select View->DocumentSource for the View menu - tell us what you see. I think you are changing view modes somehow, but I want to be sure the problem is what you think it is. -- Bill Davidsen We are not out of the woods yet, but we know the direction and have taken the first step. The steps are many, but finite in number, and if we persevere we will reach our destination. -me, 2010 ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Composer - Lose my ASCII characters when saving
Hi Michael, Thanks so much for the quick response. I did try the numeric code and the Insert character approach but am encountering the same problem :- ( The only way around it seems to be to use a text editor as you say, which is a real shame as my aim was to enable a colleague with no coding knowledge to handle the editing of an HTML email, using Composer's WYSIWYG editor. Ho hum, I guess I'll have to look for an alternative. Thanks again for your reply though, really appreciate it. Zoe ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Composer - Lose my ASCII characters when saving
Hi Phillip, Thanks very much for your reply. That's weird, I'm using exactly the same version of Sea Monkey and OS X - I wonder what it is about my set- up that is causing this problem? What happens my end is: - I enter "©" in the source view. - Upon saving, it automatically switches to normal view. Here it shows "©". - Going back to source view, it also shows © When the page is viewed in a browser/email client it shows a capital A with a grave accent before the © I have tried switching on the option to 'retain source formatting' but that doesn't seem to have any effect. As for the Charset, I've tried switching the encoding to UTF-8 but have the same issue with SeaMonkey changing the code back to © and therefore the rendering in the browser and email client. About:config - was all the same as you too - so I'm puzzled. Thanks so much for taking the time to reply though - it's all so frustrating, apart from this niggly problem I was loving SeaMonkey. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Composer - Lose my ASCII characters when saving
Hi Phillip, Thanks very much for your reply. That's weird, I'm using exactly the same version of Sea Monkey and OS X - I wonder what it is about my set- up that is causing this problem? What happens my end is: - I enter "©" in the source view. - Upon saving, it automatically switches to normal view. Here it shows "©". - Going back to source view, it also shows © When the page is viewed in a browser/email client it shows a capital A with a grave accent before the © I have tried switching on the option to 'retain source formatting' but that doesn't seem to have any effect. As for the Charset, I've tried switching the encoding to UTF-8 but have the same issue with SeaMonkey changing the code back to © and therefore the rendering in the browser and email client. About:config - was all the same as you too - so I'm puzzled. Thanks so much for taking the time to reply though - it's all so frustrating, apart from this niggly problem I was loving SeaMonkey. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Composer - Lose my ASCII characters when saving
TheFunnySide wrote: - I enter "©" in the source view. - Upon saving, it automatically switches to normal view. Here it shows "©". - Going back to source view, it also shows © For me, Seamonkey 2.2 Composer under Windows/XP manifests exactly the opposite behaviour. If I enter © in source view, it shews as © in other modes and reverts to shewing as © in source view. If I enter © in source view, it mutates to © after cycling through another view and then back to source view. Philip Taylor ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Composer - Lose my ASCII characters when saving
TheFunnySide wrote: Hi Phillip, Thanks very much for your reply. That's weird, I'm using exactly the same version of Sea Monkey and OS X - I wonder what it is about my set- up that is causing this problem? What happens my end is: - I enter "©" in the source view. - Upon saving, it automatically switches to normal view. Here it shows "©". - Going back to source view, it also shows © That last one is bizarre. There is no way you should see the character unless something is doing HTML interpretation. If you can use command line a little, you can use the "less" command to view the file, hopefully this happens in a small test file as well. When the page is viewed in a browser/email client it shows a capital A with a grave accent before the © I suspect that you are using some 16bit character set, and the data you see as two characters is intended to be viewed as one. Yes, I'm guessing on that, take it as a thought provoking idea, not an explanation. I have tried switching on the option to 'retain source formatting' but that doesn't seem to have any effect. As for the Charset, I've tried switching the encoding to UTF-8 but have the same issue with SeaMonkey changing the code back to © and therefore the rendering in the browser and email client. It's possible that if you're using certain character sets on a Mac that there is some seldom used code you may be testing for us. I'll ask my Mac user friends to test if they have Seamonkey installed. This is with 2.2? About:config - was all the same as you too - so I'm puzzled. Thanks so much for taking the time to reply though - it's all so frustrating, apart from this niggly problem I was loving SeaMonkey. -- Bill Davidsen We are not out of the woods yet, but we know the direction and have taken the first step. The steps are many, but finite in number, and if we persevere we will reach our destination. -me, 2010 ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
