Re: Fwd: Character encoding since v.2.26 [SOLVED]

Dennis wrote: > Francois LE COAT wrote: >> Hi, >> >> WaltS48 write: >>> Francois LE COAT wrote: Hartmut Figge writes: > Francois LE COAT: >> I've set : >> "mailnews.force_charset_override;false" without better results. > > Works here. Hm. That works finally !

Re: Fwd: Character encoding since v.2.26 [SOLVED]

Francois LE COAT wrote: > Hi, > > WaltS48 write: >> Francois LE COAT wrote: >>> Hartmut Figge writes: Francois LE COAT: > I've set : > "mailnews.force_charset_override;false" without better results. Works here. Hm. >>> >>> That works finally ! >>> The only thing is that I ha

Re: Fwd: Character encoding since v.2.26 [SOLVED]

Francois LE COAT wrote, On 06/07/2014 00:25: Hi, Paul B. Gallagher writes: Of course, I can't say what the French localized version might do. Maybe the problem only occurs with French localization of SeaMonkey. The problem with the accentuation only occurred since version 2.26. I got French

Re: Fwd: Character encoding since v.2.26 [SOLVED]

Hi, Paul B. Gallagher writes: Of course, I can't say what the French localized version might do. Maybe the problem only occurs with French localization of SeaMonkey. The problem with the accentuation only occurred since version 2.26. I got French localized version from

Re: Fwd: Character encoding since v.2.26 [SOLVED]

Francois LE COAT wrote: Hi, WaltS48 write: Francois LE COAT wrote: Hartmut Figge writes: Francois LE COAT: I've set : "mailnews.force_charset_override;false" without better results. Works here. Hm. That works finally ! The only thing is that I have to restart SeaMonkey after the setting.

Re: Fwd: Character encoding since v.2.26 [SOLVED]

Hi, WaltS48 write: Francois LE COAT wrote: Hartmut Figge writes: Francois LE COAT: I've set : "mailnews.force_charset_override;false" without better results. Works here. Hm. That works finally ! The only thing is that I have to restart SeaMonkey after the setting. When I view a UTF-8 mes

Re: Fwd: Character encoding since v.2.26

Francois LE COAT: >Hartmut Figge writes: >> The problem is your profile, not your SM. > >Please notice that I use SeaMonkey 2.26, with two different machines, >a Vaio and Macintosh, with two different OSes, Kubuntu 14.04 and >OS X 10.6.8, and two different profiles, and there's the same problem >w

Re: Fwd: Character encoding since v.2.26

On 07/05/2014 11:47 AM, Francois LE COAT wrote: Hi, Hartmut Figge writes: Francois LE COAT: I've set : "mailnews.force_charset_override;false" without better results. Works here. Hm. That works finally ! The only thing is that I have to restart SeaMonkey after the setting. When I view a U

Re: Fwd: Character encoding since v.2.26

Hi, Hartmut Figge writes: Francois LE COAT: I've set : "mailnews.force_charset_override;false" without better results. Works here. Hm. That works finally ! The only thing is that I have to restart SeaMonkey after the setting. When I view a UTF-8 message, it is now correctly displayed, as i

Re: Fwd: Character encoding since v.2.26

Francois LE COAT wrote: Hi, Hartmut Figge writes: Francois LE COAT: I've set : "mailnews.force_charset_override;false" without better results. Works here. Hm. I also downloaded and installed SeaMonkey 2.26 from the following site

Re: Fwd: Character encoding since v.2.26

Francois LE COAT wrote: Hi, Hartmut Figge writes: Let us look into about:config with the filter charset. Near the end is a pref which looks promising. mailnews.force_charset_override. It is set to false here. If it is set to true on your machine, we should have found the culprit. I've set : "

Re: Fwd: Character encoding since v.2.26

Hi, Hartmut Figge writes: Francois LE COAT: I've set : "mailnews.force_charset_override;false" without better results. Works here. Hm. I also downloaded and installed SeaMonkey 2.26 from the following site

Re: Fwd: Character encoding since v.2.26

Francois LE COAT: >I've set : >"mailnews.force_charset_override;false" without better results. Works here. Hm. >I also downloaded and installed SeaMonkey 2.26 from the following site > > > >

Re: Fwd: Character encoding since v.2.26

Hi, Hartmut Figge writes: Let us look into about:config with the filter charset. Near the end is a pref which looks promising. mailnews.force_charset_override. It is set to false here. If it is set to true on your machine, we should have found the culprit. I've set : "mailnews.force_charset_ov

Re: Fwd: Character encoding since v.2.26

Ray_Net: >I have "Western" and i am happy with that. Your accentuated characters >are ok. So i am not obliged to switch to unicode. It is advisable to use the same font for Western and Unicode. And the same size. :) Hartmut ___ support-seamonkey maili

Re: Fwd: Character encoding since v.2.26

Op 7/5/2014 om 2:36 AM schreef 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 rig

Re: Fwd: Character encoding since v.2.26

Hartmut Figge wrote, On 05/07/2014 01:35: 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.

Re: Fwd: Character encoding since v.2.26

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 wit

Re: Fwd: Character encoding since v.2.26

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 selec

Re: Fwd: Character encoding since v.2.26

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 Sea

Re: Fwd: Character encoding since v.2.26

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 vari

Re: Fwd: Character encoding since v.2.26

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 doesn'

Re: Fwd: Character encoding since v.2.26

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

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 character

Re: Fwd: Character encoding since v.2.26

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

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

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, >>>

Re: Fwd: Character encoding since v.2.26

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

Re: Fwd: Character encoding since v.2.26

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 i

Re: Fwd: Character encoding since v.2.26

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 a

Re: Fwd: Character encoding since v.2.26

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 >acce

Re: Fwd: Character encoding since v.2.26

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, yo

Re: Fwd: Character encoding since v.2.26

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 tel

Fwd: Character encoding since v.2.26

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