Re: 2.26.1 mail password

2014-07-04 Thread cyberzen
Le 04/07/2014 01:44, NoOp a écrit : I've found this addon to be quite handy for easily checking, modifying, adding passwords: https://addons.mozilla.org/en-US/seamonkey/addon/saved-password-editor/ Not available for SeaMonkey 2.26.1? unfortunately -- cyberzen

Re: 2.26.1 mail password

2014-07-04 Thread Trane Francks
On 7/4/14 4:36 PM +0900, cyberzen wrote: Le 04/07/2014 01:44, NoOp a écrit : I've found this addon to be quite handy for easily checking, modifying, adding passwords: https://addons.mozilla.org/en-US/seamonkey/addon/saved-password-editor/ Not available for SeaMonkey 2.26.1? unfortunately

Re: Visual annoyances after updating to SM 2.26.1

2014-07-04 Thread Daniel
On 04/07/14 15:26, Barry Edwin Gilmour wrote: David E. Ross wrote on 07/04/2014 12:53 PM: On 7/3/2014 7:52 PM, Barry Edwin Gilmour wrote: EE wrote on 07/04/2014 07:42 AM: David E. Ross wrote: On 7/3/2014 1:12 AM, Daniel wrote: On 02/07/14 22:50, Daniel wrote: Searching for userChrome.css

Re: Visual annoyances after updating to SM 2.26.1

2014-07-04 Thread Daniel
On 04/07/14 01:56, Hartmut Figge wrote: Apologies to those who do not use Linux. Daniel: Well!! I'm not seeing any green anywhere, so I must have screwed it up!! Time to try a different/lower level in the directory chain. Several possible reasons for that. From your UA i am assuming you are

Re: Visual annoyances after updating to SM 2.26.1

2014-07-04 Thread Hartmut Figge
Daniel: On 04/07/14 01:56, Hartmut Figge wrote: Several possible reasons for that. From your UA i am assuming you are using Linux. Hartmut, I Dual boot Win7 and Linux and use the one set of profile files which, as Linux can see Windows files but Windows cannot see Linux files, I have my

Re: Visual annoyances after updating to SM 2.26.1

2014-07-04 Thread Ed Mullen
Barry Edwin Gilmour pounded out : EE wrote on 07/04/2014 07:42 AM: David E. Ross wrote: On 7/3/2014 1:12 AM, Daniel wrote: On 02/07/14 22:50, Daniel wrote: Searching for userChrome.css as I type. Well!! I'm not seeing any green anywhere, so I must have screwed it up!! Time to try a

Re: Visual annoyances after updating to SM 2.26.1

2014-07-04 Thread Ed Mullen
Daniel pounded out : On 04/07/14 15:26, Barry Edwin Gilmour wrote: David E. Ross wrote on 07/04/2014 12:53 PM: On 7/3/2014 7:52 PM, Barry Edwin Gilmour wrote: EE wrote on 07/04/2014 07:42 AM: David E. Ross wrote: On 7/3/2014 1:12 AM, Daniel wrote: On 02/07/14 22:50, Daniel wrote:

Re: Visual annoyances after updating to SM 2.26.1

2014-07-04 Thread David E. Ross
On 7/3/2014 10:26 PM, Barry Edwin Gilmour wrote: David E. Ross wrote on 07/04/2014 12:53 PM: On 7/3/2014 7:52 PM, Barry Edwin Gilmour wrote: To expand on Hartmut's answer yesterday, they are no longer in the profile folder, but kept in the application-folder's omni.ja java archive folder (For

Re: 2.26.1 mail password

2014-07-04 Thread Ed Mullen
cyberzen pounded out : Le 04/07/2014 01:44, NoOp a écrit : I've found this addon to be quite handy for easily checking, modifying, adding passwords: https://addons.mozilla.org/en-US/seamonkey/addon/saved-password-editor/ Not available for SeaMonkey 2.26.1? unfortunately I'm using the

Re: Visual annoyances after updating to SM 2.26.1

2014-07-04 Thread Ed Mullen
David E. Ross pounded out : On 7/3/2014 10:26 PM, Barry Edwin Gilmour wrote: David E. Ross wrote on 07/04/2014 12:53 PM: On 7/3/2014 7:52 PM, Barry Edwin Gilmour wrote: To expand on Hartmut's answer yesterday, they are no longer in the profile folder, but kept in the application-folder's

Re: Visual annoyances after updating to SM 2.26.1

2014-07-04 Thread Hartmut Figge
David E. Ross: Why were userChrome.css, userContent.css, userChrome-example.css, and userContent-example.css hidden in omni.ja? userChrome.css and userContent.css are created by the user. They do not exist by default. How could they be hidden? ;) But for the example files your question is

Re: 2.26.1 mail password

2014-07-04 Thread NoOp
On 07/04/2014 12:36 AM, cyberzen wrote: Le 04/07/2014 01:44, NoOp a écrit : I've found this addon to be quite handy for easily checking, modifying, adding passwords: https://addons.mozilla.org/en-US/seamonkey/addon/saved-password-editor/ Not available for SeaMonkey 2.26.1? unfortunately

Re: Visual annoyances after updating to SM 2.26.1

2014-07-04 Thread David E. Ross
On 7/4/2014 7:24 AM, Ed Mullen wrote: Daniel pounded out : On 04/07/14 15:26, Barry Edwin Gilmour wrote: David E. Ross wrote on 07/04/2014 12:53 PM: On 7/3/2014 7:52 PM, Barry Edwin Gilmour wrote: EE wrote on 07/04/2014 07:42 AM: David E. Ross wrote: On 7/3/2014 1:12 AM, Daniel wrote: On

Re: Visual annoyances after updating to SM 2.26.1

2014-07-04 Thread EE
Hartmut Figge wrote: Barry Edwin Gilmour: [userChrome-example.css userContent-example.css] To expand on Hartmut's answer yesterday, they are no longer in the profile folder, but kept in the application-folder's omni.ja java archive folder (For Linux, that's at /seamonkey/omni.ja

Re: Visual annoyances after updating to SM 2.26.1

2014-07-04 Thread EE
David E. Ross wrote: On 7/3/2014 7:52 PM, Barry Edwin Gilmour wrote: EE wrote on 07/04/2014 07:42 AM: David E. Ross wrote: On 7/3/2014 1:12 AM, Daniel wrote: On 02/07/14 22:50, Daniel wrote: Searching for userChrome.css as I type. Well!! I'm not seeing any green anywhere, so I must have

Re: Visual annoyances after updating to SM 2.26.1

2014-07-04 Thread EE
Daniel wrote: On 04/07/14 15:26, Barry Edwin Gilmour wrote: David E. Ross wrote on 07/04/2014 12:53 PM: On 7/3/2014 7:52 PM, Barry Edwin Gilmour wrote: EE wrote on 07/04/2014 07:42 AM: David E. Ross wrote: On 7/3/2014 1:12 AM, Daniel wrote: On 02/07/14 22:50, Daniel wrote: Searching for

Re: Visual annoyances after updating to SM 2.26.1

2014-07-04 Thread EE
David E. Ross wrote: On 7/3/2014 10:26 PM, Barry Edwin Gilmour wrote: David E. Ross wrote on 07/04/2014 12:53 PM: On 7/3/2014 7:52 PM, Barry Edwin Gilmour wrote: To expand on Hartmut's answer yesterday, they are no longer in the profile folder, but kept in the application-folder's omni.ja

[no subject]

2014-07-04 Thread 8437890616
Title: New Page 1 Fuck you Sent from my Cricket mobile device Fuck you ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey

Re: Visual annoyances after updating to SM 2.26.1

2014-07-04 Thread Hartmut Figge
EE: Did you put a namespace line at the beginning of the file? It is necessary for userChrome.css, but not for userContent.css. @namespace url(http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul;); Necessary, hm. The example file claims it is required. On the other hand, i have

Fwd: Character encoding since v.2.26

2014-07-04 Thread Francois LE COAT
Hi, Francois LE COAT writes : I've used successively Mosaic, Netscape, Mozilla then SeaMonkey for exactly 20 years on the Usenet today. I never had to complain, since SeaMonkey 2.26 appeared ... Well, the character encoding is working or not, you never can tell ... Sometimes accents in

Re: Fwd: Character encoding since v.2.26

2014-07-04 Thread Paul B. Gallagher
Francois LE COAT wrote: Hi, Francois LE COAT writes : I've used successively Mosaic, Netscape, Mozilla then SeaMonkey for exactly 20 years on the Usenet today. I never had to complain, since SeaMonkey 2.26 appeared ... Well, the character encoding is working or not, you never can tell

Re: Fwd: Character encoding since v.2.26

2014-07-04 Thread Francois LE COAT
Hi, Thanks for your answer. Paul B. Gallagher writes : Francois LE COAT wrote: I've used successively Mosaic, Netscape, Mozilla then SeaMonkey for exactly 20 years on the Usenet today. I never had to complain, since SeaMonkey 2.26 appeared ... Well, the character encoding is working or not,

Re: Fwd: Character encoding since v.2.26

2014-07-04 Thread Hartmut Figge
Francois LE COAT: The problem with UTF-8 encoding happens when you talk in French forums. Because I register to some newsgroups on the Usenet, I frequently have the problem with users adopting the UTF-8 character encoding, and using accentuation. Of course it is not a problem here. Every accent

Re: Fwd: Character encoding since v.2.26

2014-07-04 Thread Francois LE COAT
Hi, Hartmut Figge writes : Francois LE COAT: The problem with UTF-8 encoding happens when you talk in French forums. Because I register to some newsgroups on the Usenet, I frequently have the problem with users adopting the UTF-8 character encoding, and using accentuation. Of course it is not

Re: Fwd: Character encoding since v.2.26

2014-07-04 Thread Dennis
Hartmut Figge wrote: Francois LE COAT: The problem with UTF-8 encoding happens when you talk in French forums. Because I register to some newsgroups on the Usenet, I frequently have the problem with users adopting the UTF-8 character encoding, and using accentuation. Of course it is not a

Re: Fwd: Character encoding since v.2.26

2014-07-04 Thread Hartmut Figge
Francois LE COAT: You wrote I will write some chars with accents ... And 3 separated characters I can't read following. You should have seen http://www.triffids.de/pub/screenshot/sm140705.png That's a problem I often have since I installed SeaMonkey 2.26. I often have to guess what is the other

Re: Fwd: Character encoding since v.2.26

2014-07-04 Thread Dennis
Francois LE COAT wrote: Hi, Hartmut Figge writes : Francois LE COAT: The problem with UTF-8 encoding happens when you talk in French forums. Because I register to some newsgroups on the Usenet, I frequently have the problem with users adopting the UTF-8 character encoding, and using

Re: Fwd: Character encoding since v.2.26

2014-07-04 Thread Hartmut Figge
Dennis: I know nothing about character sets or character encoding but in your first line I see the character e three times with a different accent over each one. Message source says: Content-Type: text/plain; charset=UTF-8 So I assume it is working on this end. You are assuming right. Now we

Re: Fwd: Character encoding since v.2.26

2014-07-04 Thread Hartmut Figge
Dennis: Hartmut's three characters are not readable. They were readable in his original post and in my reply to his post. AT least for me anyway. I think you have found it. Francois replied to utf-8 with iso-8859-15, but did not convert the utf-8 chars to iso-8859-15. If you select his message

Re: Fwd: Character encoding since v.2.26

2014-07-04 Thread Francois LE COAT
Hi, Hartmut Figge writes: Francois LE COAT: You wrote I will write some chars with accents ... And 3 separated characters I can't read following. You should have seen http://www.triffids.de/pub/screenshot/sm140705.png That's not what I'm reading. There's 3 series of 2 unreadable

Re: Fwd: Character encoding since v.2.26

2014-07-04 Thread Hartmut Figge
Francois LE COAT: Hartmut Figge writes: You should have seen http://www.triffids.de/pub/screenshot/sm140705.png That's not what I'm reading. There's 3 series of 2 unreadable characters. Depends. See my reply to Dennis. 53b72ffa.6050...@hfigge.myfqdn.de Here's the box in current state

Re: Fwd: Character encoding since v.2.26

2014-07-04 Thread Francois LE COAT
Hi, Hartmut Figge writes: Hrm. I have to guess from my half forgotten knowledge of Latin. *g* Occidental should correspond to Western. You should have selected Unicode. Assuming Unicode means also Unicode in French. :) That's right. I can select Unicode in French in this box. But that

Re: Fwd: Character encoding since v.2.26

2014-07-04 Thread Hartmut Figge
Francois LE COAT: Well, but it is not easy reading messages, and select View-Character Encoding-Unicode for every message ? Only to test my message with the three chars and your reply to it. For a test the effort is bearable. ;) You suggested me to select Unicode, that is a synonymous variant

Re: Fwd: Character encoding since v.2.26

2014-07-04 Thread Trane Francks
On 7/5/14 7:36 AM +0900, Hartmut Figge wrote: Francois LE COAT: You wrote I will write some chars with accents ... And 3 separated characters I can't read following. You should have seen http://www.triffids.de/pub/screenshot/sm140705.png That's a problem I often have since I installed

Re: Fwd: Character encoding since v.2.26

2014-07-04 Thread Trane Francks
On 7/5/14 9:36 AM +0900, Francois LE COAT wrote: Hi, Hartmut Figge writes: Hrm. I have to guess from my half forgotten knowledge of Latin. *g* Occidental should correspond to Western. You should have selected Unicode. Assuming Unicode means also Unicode in French. :) That's right. I can

Re: Fwd: Character encoding since v.2.26

2014-07-04 Thread Hartmut Figge
Trane Francks: The thing is that it's ideal to use UTF-8 all the time anyway these days. There is very little reason to use other encodings. Mhm, no. I disagree. There is still a reason for using a minimal charset. 'Minimal' in a historical, not technical sense. If someone replies to utf-8 with

Re: Visual annoyances after updating to SM 2.26.1

2014-07-04 Thread Philip Chee
On 04/07/2014 22:22, Ed Mullen wrote: You can download the original files here: http://edmullen.net/test/userChrome-example.css http://edmullen.net/test/userContent-example.css They remain in my profile from before 2.20 and are dated 7/1/2010.