Re: 2.26.1 mail password

[cmcadams]

question wrote:

Seamonkey asks for mail password when I try to send an e-mail even tho pass word
manager has it .
  This is using smtp.att.yahoo.com and my sbcglobal account


Same version if I use gmail server with gmail account e-mail.. password is not 
asked for


This all started with the ugrade to 2.26.1prior to that all was fine .


Same here, but I still get through by clicking 'Retry' as many times as 
necessary.

I assumed this was just SBC/Yahoo being annoying (yet again!)
___
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

[Daniel]

On 05/07/14 02:15, David E. Ross wrote:

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 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 different/lower level in the directory chain.


Try searching for userChrome-example.css.  That file should always be
created when installing SeaMonkey.  If you find it but not
userChrome.css, just copy userChrome-example.css into the same
directory
and rename it as userChrome.css.


Those example files are not present in the recent versions of
SeaMonkey.  They were not present when I started using SeaMonkey at
version 2.20.


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
(/defaults/profile/chrome/userChrome-example.css and /seamonkey/omni.ja
(/defaults/profile/chrome/userContent-example.css). HTH


How, then, is someone supposed to extract userChrome.css and
userContent.css (or userChrome-example.css and userContent-example.css
to use as templates to create the others) from omni.ja and place them
into the chrome directory of a profile?


Sorry about that. I use an archive application to copy out of the Java
archive folder.
Copying the attached style sheets into the user's profile chrome
directory, and editing in your text editor is the way to go. HTH.


As I noted, above, Barry, I've moved an old version of userChrome.css
into the appropriate location and had no effect, so I don't think your
files will help, but thanks for trying.



Daniel, the "example" files won't do a thing:  They are just examples
with no active code in them.

In CSS files lines are made comments by preceding them with "/*" (no
quotes) and ending them with "*/"

If you look at the files' content you'll that EVERYTHING is commented out.



Until they were hidden in omni.ja, the "example" files were intended for
use as templates to create the actual userChrome.css and
userContent.css.  A number of times, users were advised in this same
newsgroup to copy the "example" files, paste them back into the chrome
directory, rename them to eliminate the "example", and then edit the new
files for some purpose.


Yeap, that *is* what I did many moons ago, so, in my Netscape Suite and 
Mozilla Suite and SeaMonkey Suite Ver 1.x.x profiles I did have 
userChrome.css and userContent.css files, complete with various 
additions, but when I installed SM Ver 2.0 (or, maybe, 2.1 (after the 
*profile conversion* )) there seems to have been no .css files!!


--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:29.0) Gecko/20100101 
Firefox/29.0 SeaMonkey/2.26 Build identifier: 20140415200419

or
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:29.0) Gecko/20100101 
SeaMonkey/2.26 Build identifier: 20140408191805

___
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

[Daniel]

On 05/07/14 04:34, EE wrote:

Daniel wrote:





As I noted, above, Barry, I've moved an old version of userChrome.css
into the appropriate location and had no effect, so I don't think your
files will help, but thanks for trying.


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";);


Got it! ;-)

--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:29.0) Gecko/20100101 
Firefox/29.0 SeaMonkey/2.26 Build identifier: 20140415200419

or
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:29.0) Gecko/20100101 
SeaMonkey/2.26 Build identifier: 20140408191805

___
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

[Daniel]

On 03/07/14 18:12, Daniel wrote:

On 02/07/14 22:50, Daniel wrote:

On 02/07/14 21:40, Hartmut Figge wrote:





It should be difficult not to notice the effect. :)

To get rid of the example, rename the userChrome.css or delete it and
restart SM again.

Hartmut


userChrome.css



#folderTree {
 background-color: green  !important;
}


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 different/lower level in the directory chain.


You're right, Hartmut, "It should be difficult not to notice the 
effect.", now that I've moved the .css file into the chrome directory, 
which didn't exist until I made it!!


The word "Ugly" springs to mind  maybe a different colour!! :-)

--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:29.0) Gecko/20100101 
Firefox/29.0 SeaMonkey/2.26 Build identifier: 20140415200419

or
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:29.0) Gecko/20100101 
SeaMonkey/2.26 Build identifier: 20140408191805

___
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

[Daniel]

On 04/07/14 23:36, Hartmut Figge wrote:

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 SeaMonkey profile on a Win7 partition and my
/home/daniel/.mozilla/seamonkey/profiles.ini points to the Win7 location
. (Don't ya just love people who refuse to do standard
installations!!  ;-( And then come looking for help!!)


Simply delightful. *g*


[Profile1]
Name=Default User
IsRelative=0
Path=/mnt/Games/Internet_Programs/Profile/Profile
Default=1


I would have to guess now. Better, others take over.

Hartmut


No problems, Hartmut, now that I've created a chrome directory in my 
Profile and copied the amended userChrome.css file there and re-booted 
SM, I can see the effect!! Yuck!


--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:29.0) Gecko/20100101 
Firefox/29.0 SeaMonkey/2.26 Build identifier: 20140415200419

or
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:29.0) Gecko/20100101 
SeaMonkey/2.26 Build identifier: 20140408191805

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Fwd: Character encoding since v.2.26

[Onno Ekker]

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 right. I can select Unicode in French in this box.
> 
>> But that doesn't matter anymore. Dennis was more attentive than me and
>> has pointed to the solution. I am assuming now that you also see the
>> unreadable chars in this way:
>> http://www.triffids.de/pub/screenshot/sm140705-3.png
> 
> That's true. That's what I'm reading.
> 
>> I hadn't noticed that before Dennis mentioned it. It looked like utf-8
>> displayed as iso-8859-x. You can verify by yourself. Select my message
>> with the unreadable chars, go to View->Character Encoding and choose
>> unicode. The result should be readable chars.
> 
> Setting View->Character Encoding to Unicode displays it correctly.
> 
>> Repeat that with your
>> reply to my message and the chars should also be ok.
> 
> That's correct. Unicode is already checked, but when I select it twice
> the characters are then correctly displayed. But in this case the "ç"
> character from my signature (François LE COAT) appears as a unique
> unreadable character (a sort of diamond with a question-mark).
> 
>> You have made a selection to force SM to ignore the charset of a message
>> and to use iso-8859-15 instead. Where? There is a problem.
> 
> I don't know myself.
> 
>> The handling for chars was changed recently for SM in Trunk and there
>> are still bugs. I am hesitating to use an older SM and am hoping, you
>> can find the selection yourself. :-D
> 
> Well, but it is not easy reading messages, and select View->Character
> Encoding->Unicode for every message ? You suggested me to select
> Unicode, that is a synonymous variant of UTF-8, though my encoding
> character is ISO-8859-15. Isn't there an incoherency ? I'm confused.
> 
> The situation hasn't be so complicated since I installed SM 2.26 =(
> 
> Regards,
> 

Characters that are not defined in a font are displayed as a diamond
with a question-mark. You can try to use another font to find a font
that has that character.

I for instance have the font Consolas for monospace characters, which
displays the 'ç' character as it should...

Onno
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: 2.26.1 mail password

[Arnie Goetchius]

Ed Mullen wrote:
> 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:
>>> 
>>>
>>>
>>
>> Not available for SeaMonkey 2.26.1?
>> unfortunately
>>
> 
> I'm using the extension v. 2.7.2 with that SM version just fine.  It was
> installed prior to SM 2.26.1 updating.
> 
Same here. If you installed it before 2.26.1, it will work in 2.26.1. If
you are trying to install it for the first time in 2.26.1, you cannot.
___
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

[Hartmut Figge]

Daniel:

>You're right, Hartmut, "It should be difficult not to notice the 
>effect.", now that I've moved the .css file into the chrome directory, 
>which didn't exist until I made it!!
>
>The word "Ugly" springs to mind  maybe a different colour!! :-)

*g* I am using #F7FFF9 for the folder pane and #EBF1FF for the thread pane.

Hartmut
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Fwd: Character encoding since v.2.26

[Hartmut Figge]

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 mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Fwd: Character encoding since v.2.26

[Francois LE COAT]

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_override;false" without better results.

I also downloaded and installed SeaMonkey 2.26 from the following site





including the linguistic package 2.26 (xpi) :



I always have problems with UTF-8 character encoding. Is there something
else I can do ? Is there somebody else using accentuated languages ?

Best regards,

--
François LE COAT



___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Fwd: Character encoding since v.2.26

[Hartmut Figge]

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
>
>   
>
>
>
>including the linguistic package 2.26 (xpi) :
>
>

The problem is your profile, not your SM.

>I always have problems with UTF-8 character encoding. Is there something
>else I can do ?

Yes. Start your SM in safe mode. Easiest way to this is by choosing
'Restart with Add-ons Disabled' from the top Help menu. Or you could
start SM with the parameter -safe-mode. Then press 'Continue in Safe
Mode' without checking any of the boxes.

>Is there somebody else using accentuated languages ?

Not here, but i am using umlauts. ;)

Hartmut
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Fwd: Character encoding since v.2.26

[Francois LE COAT]

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





including the linguistic package 2.26 (xpi) :




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
with UTF-8 character encoding. The problem occurs with plain text
messages, but also when I receive HTML formated messages.

If I set View->Character Encoding to Unicode it displays correctly.

The problem must be somewhere in the default configuration of SM,
or a bug detecting the UTF-8 character encoding.


I always have problems with UTF-8 character encoding. Is there something
else I can do ?


Yes. Start your SM in safe mode. Easiest way to this is by choosing
'Restart with Add-ons Disabled' from the top Help menu. Or you could
start SM with the parameter -safe-mode. Then press 'Continue in Safe
Mode' without checking any of the boxes.


That sounds very radical. I'm afraid I could corrupt my data.


Is there somebody else using accentuated languages ?


Not here, but i am using umlauts. ;)


Ho, yes ! I always use ccdile because my name contains this character =)

Many thanks for your help,

Best regards,

--
François LE COAT



___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Fwd: Character encoding since v.2.26

[WaltS48]

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 :
"mailnews.force_charset_override;false" without better results.



"mailnews.force_charset_overide:false" appears to be the default, in my 
Seamonkey.


Fonts for: Western and Monospce are selected in preferences.

"mailnews.send_default_charset:UTF-8" and 
"mailnews.view_default_charset:ISO-8859-1" are the defautl settings.


I can view Hartmut's accented characters just fine.




I also downloaded and installed SeaMonkey 2.26 from the following site

 



including the linguistic package 2.26 (xpi) :




I always have problems with UTF-8 character encoding. Is there something
else I can do ? Is there somebody else using accentuated languages ?

Best regards,




Other things you can do is "Restart SeaMonkey with Add-ons Disabled" and 
see if an extension is causing the problem, then track down which extension.


Try a new profile  or 



I'm not using them but I can add some accentuated characters from my 
systems character selecter application; à á ç ḉ


--
Sponsored by Thunderbird 24.6.0 or 31.0b2
Pittsburgh Vintage Grand Prix - July 11-20, 2014

GO Bucs!
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Fwd: Character encoding since v.2.26

[WaltS48]

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





including the linguistic package 2.26 (xpi) :





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
with UTF-8 character encoding. The problem occurs with plain text
messages, but also when I receive HTML formated messages.

If I set View->Character Encoding to Unicode it displays correctly.

The problem must be somewhere in the default configuration of SM,
or a bug detecting the UTF-8 character encoding.


I always have problems with UTF-8 character encoding. Is there something
else I can do ?


Yes. Start your SM in safe mode. Easiest way to this is by choosing
'Restart with Add-ons Disabled' from the top Help menu. Or you could
start SM with the parameter -safe-mode. Then press 'Continue in Safe
Mode' without checking any of the boxes.


That sounds very radical. I'm afraid I could corrupt my data.



Sounds like it is corrupted already. Safe mode will not corrupt 
anything, and neither will trying a new profile.




But as someone once said;"If you aren't planning on actually trying any 
of the advice given here, then why even bother asking questions???"


--
Sponsored by Thunderbird 24.6.0 or 31.0b2
Pittsburgh Vintage Grand Prix - July 11-20, 2014

GO Bucs!
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Fwd: Character encoding since v.2.26

[Francois LE COAT]

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 if
I've checked View->Character Encoding to Unicode. As I understood,
the message character encoding is not overridden ...

Many thanks for your help,

Best regards,

--
François LE COAT



___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Tagzilla

[sean]

JAS wrote:

sean nathan wrote:

JAS wrote:

sean nathan wrote:

JAS wrote:

My Tagzilla 0.7a2 and JsLib 0.1.367 worked fine in SM 2.21 but since
updating to SM 2.23 it is broken. I get no error message and in
extension it show it is loaded. Is there later versions that will
work or ??


working just fine then... and all the tagzilla settings are found via
about:config then search via tagzilla... thanks to phillip chee ;~)



Glad you got things working.



Its so nice to have this back!!!  I noticed this morning that the
"steal this tagline" functionality was working once again...  a
highlight and right click I was doing, in order to perform a search,
also revealed the "steal"... frankly that has been broken for me for
so long I'd almost forgotten about it...


Yes I use use the steal quite often.


just a note to say tagzilla working quite nicely in SM 2.26.1 ... all 
props to Phillip Chee  ;~)


Youth is when you blame all your troubles on your parents...
Maturity is when you learn everything is the fault of the younger generation
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Fwd: Character encoding since v.2.26

[Hartmut Figge]

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
>with UTF-8 character encoding.

I doubt that you made no changes to the original SM. ;) One of those
changes could be the reason for the problem and could have be done on
both machines.

>If I set View->Character Encoding to Unicode it displays correctly.
>
>The problem must be somewhere in the default configuration of SM,
>or a bug detecting the UTF-8 character encoding.

Neither. You have a suitable font, but your SM is forced to ignore the
encoding of a message. If a message contains the headers

Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

SM should treat the message as utf-8. Instead your SM insists on using
iso-8859-15. Displaying utf-8 as iso-8859-15 gives funny results. :)

The default configuration of SM would not allow such behaviour. It may
be caused by an extension. To test that starting SM in safe mode is
recommended.

>> Yes. Start your SM in safe mode. Easiest way to this is by choosing
>> 'Restart with Add-ons Disabled' from the top Help menu. Or you could
>> start SM with the parameter -safe-mode. Then press 'Continue in Safe
>> Mode' without checking any of the boxes.
>
>That sounds very radical. I'm afraid I could corrupt my data.

Should not be possible this way. But of course you are right. Should is
not enough. Therefore backups are advisable. ;)

Copy your whole .mozilla directory to .mozilla-sav. You will need a
backup anyway if something goes wrong.

If safe-mode does not help, the next step is to use a clean fresh test
profile. Without any extensions. That would not harm your current
profile. And even if, you have your backup.

In that new profile only...

Oh, i just noticed your reply that the problem is gone. So i do not have
to finish this message. :-D

Hartmut
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Fwd: Character encoding since v.2.26

[WaltS48]

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 UTF-8 message, it is now correctly displayed, as if
I've checked View->Character Encoding to Unicode. As I understood,
the message character encoding is not overridden ...

Many thanks for your help,

Best regards,




Glad you resolved your issue. Why was it set to "True"?

--
Sponsored by Thunderbird 24.6.0 or 31.0b2
Pittsburgh Vintage Grand Prix - July 11-20, 2014

GO Bucs!
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Sync broken in 2.26 beta 1?

[sean]

Philip Chee wrote:

On 11/04/2014 03:30, MCBastos wrote:

Interviewed by CNN on 10/04/2014 15:58, Byron Smith told the world:

Absolutely cannot set up Sync in Seamonkey 2.26 beta 1. I have
login credentials and recovery key. Could not pair a device to set
up a new sync on Seamonkey. Also could not login using credentials
and recovery key as Next button does nothing (and neither does the
link about having lost a device). Could this because I switched
over to the new sync profile in Firefox 29.0 beta?


Probably. From what I understand, the new Sync system is quite
different from the one heretofore being used.


Sync v2 uses a more traditional userid/password scheme. With the userid
an email-like string.

Phil



how long should one leave the sync window open after providing all the 
account data and clicking next? nothing has happened with mine for quite 
a while...



-- You step in the stream...
  But the water has moved on...
   This page is not here.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Tagzilla

[sean]

JAS wrote:

sean nathan wrote:

JAS wrote:

sean nathan wrote:

JAS wrote:

My Tagzilla 0.7a2 and JsLib 0.1.367 worked fine in SM 2.21 but since
updating to SM 2.23 it is broken. I get no error message and in
extension it show it is loaded. Is there later versions that will
work or ??


working just fine then... and all the tagzilla settings are found via
about:config then search via tagzilla... thanks to phillip chee ;~)



Glad you got things working.



Its so nice to have this back!!!  I noticed this morning that the
"steal this tagline" functionality was working once again...  a
highlight and right click I was doing, in order to perform a search,
also revealed the "steal"... frankly that has been broken for me for
so long I'd almost forgotten about it...


Yes I use use the steal quite often.


second trial of tagzilla 0.7a2 begins now   ;~0



-- You step in the stream...
  But the water has moved on...
   This page is not here.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

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

[Francois LE COAT]

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 message, it is now correctly displayed, as if
I've checked View->Character Encoding to Unicode. As I understood,
the message character encoding is not overridden ...


Glad you resolved your issue.


Yes. Hartmut Figge helped a lot to find out what was wrong with
character encoding. Now posts on the Usenet are correctly
displayed, and a lot of messages in my email inbox also.

I always had to correct accentuation when I replied to messages.


 Why was it set to "True"?


It is a default configuration of SeaMonkey 2.26. I never had
to modify the default configuration before that. That was
causing big troubles reading every days messages, indeed.

Many thanks for your patience. That helped a lot using SeaMonkey.

Best regards,

--
François LE COAT



___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Can we rename messages somehow?

[Geoff Welsh]

Onno Ekker wrote:

Geoff Welsh wrote:

sometimes I wanna save a message with important information, and after a
while there's tons of them, and some of the Subject titles are useless
to jog my memory

Can we rename messages somehow?  i.e. change the Subject line?

"Edit as New" and then changing the subject, and then sending it to
myself seems a cheesy workaround.

GW


I think you can do this with the extension Headers Tool Lite...
https://addons.mozilla.org/en-US/seamonkey/addon/header-tools-lite

Onno



I just got around to installing this Extension and it works exactly as I 
had hoped.


-Right-click on a highlighted message's subject/title/name in the Thread 
Pane


- select HeaderToolsLite from context menu

- change what you want.

no more will I have to stare at USELESS subjects/titles/names for 
important messages in my Inbox


For anyone else out there that essentially uses SM as their "day 
planner" / "to-do" list, this is priceless.


Thanks Onno!
GW
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

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

[Paul B. Gallagher]

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.

When I view a UTF-8 message, it is now correctly displayed, as if
I've checked View->Character Encoding to Unicode. As I understood,
the message character encoding is not overridden ...


Glad you resolved your issue.


Yes. Hartmut Figge helped a lot to find out what was wrong with
character encoding. Now posts on the Usenet are correctly
displayed, and a lot of messages in my email inbox also.

I always had to correct accentuation when I replied to messages.


 Why was it set to "True"?


It is a default configuration of SeaMonkey 2.26. I never had
to modify the default configuration before that. That was
causing big troubles reading every days messages, indeed.


I don't think it is. I've upgraded routinely without error, and SM did 
not take it into its head to change this setting to "true."


Of course, I can't say what the French localized version might do.

--
War doesn't determine who's right, just who's left.
--
Paul B. Gallagher

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Welcome to mozilla.support.seamonkey

[sean]

Dave Miller wrote:

Welcome to mozilla.support.seamonkey

fresh install of Seamonkey 2.26.1 on my peppermint5 linux laptop... 
happy happy once again...


sean

-- A dog is the only thing on earth
that loves you more than he loves himself.
~Josh Billings
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

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

[Francois LE COAT]

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 

I apologize if I've been a little irritated. I was really angry about
SeaMonkey 2.26, because I thought something was corrupted. It's not.

A few French SeaMonkey users around me will appreciate the solution =)

Best regards,

--
François LE COAT



___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

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

[Ray_Net]

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 localized version from 

I apologize if I've been a little irritated. I was really angry about
SeaMonkey 2.26, because I thought something was corrupted. It's not.

A few French SeaMonkey users around me will appreciate the solution =)

Best regards,

In my case, i always download and install SM English after "add/remove 
program" of the previous version.

then i download and install:
- seamonkey-2.24.fr.langpack.xpi
- dictionnaires_francais-5.0.1-tb+fx+sm.xpi
Then finally i switch the interface language to french and check if the 
french spelling is active.

___
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

[Barry Edwin Gilmour]

David E. Ross wrote on 07/04/2014 10:28 PM:

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 Linux, that's at /seamonkey/omni.ja
(/defaults/profile/chrome/userChrome-example.css and /seamonkey/omni.ja
(/defaults/profile/chrome/userContent-example.css). HTH


How, then, is someone supposed to extract userChrome.css and
userContent.css (or userChrome-example.css and userContent-example.css
to use as templates to create the others) from omni.ja and place them
into the chrome directory of a profile?


Sorry about that. I use an archive application to copy out of the Java
archive folder.
Copying the attached style sheets into the user's profile chrome
directory, and editing in your text editor is the way to go. HTH.


Actually, my question was rhetorical.  My updates of SeaMonkey have
continued to use the userChrome.css and userContent.css that I created
in my profile some years ago.  My question was intended to address the
situation of a somewhat experienced computer user who has just now
changed to SeaMonkey (or to Firefox), someone who understands CSS and
who quickly learns about Mozilla's chrome.

Why were userChrome.css, userContent.css, userChrome-example.css, and
userContent-example.css hidden in omni.ja?  Why is it now impossible to
even look into omni.ja?



For Windows users, this page about omni.ja may help.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

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

[Dennis]

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.
>>>
>>> When I view a UTF-8 message, it is now correctly displayed, as if
>>> I've checked View->Character Encoding to Unicode. As I understood,
>>> the message character encoding is not overridden ...
>>
>> Glad you resolved your issue.
> 
> Yes. Hartmut Figge helped a lot to find out what was wrong with
> character encoding. Now posts on the Usenet are correctly
> displayed, and a lot of messages in my email inbox also.
> 
> I always had to correct accentuation when I replied to messages.
> 
>>  Why was it set to "True"?
> 
> It is a default configuration of SeaMonkey 2.26. I never had
> to modify the default configuration before that. That was
> causing big troubles reading every days messages, indeed.
> 
> Many thanks for your patience. That helped a lot using SeaMonkey.
> 
> Best regards,
> 

It is not the default setting in SeaMonkey 2.26 here.

about:config shows
Preference Name   StatusTypeValue
mailnews.force_charset_override   default   boolean false

Dennis

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

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

[Dennis]

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 !
 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 if
 I've checked View->Character Encoding to Unicode. As I understood,
 the message character encoding is not overridden ...
>>>
>>> Glad you resolved your issue.
>>
>> Yes. Hartmut Figge helped a lot to find out what was wrong with
>> character encoding. Now posts on the Usenet are correctly
>> displayed, and a lot of messages in my email inbox also.
>>
>> I always had to correct accentuation when I replied to messages.
>>
>>>  Why was it set to "True"?
>>
>> It is a default configuration of SeaMonkey 2.26. I never had
>> to modify the default configuration before that. That was
>> causing big troubles reading every days messages, indeed.
>>
>> Many thanks for your patience. That helped a lot using SeaMonkey.
>>
>> Best regards,
>>
> 
> It is not the default setting in SeaMonkey 2.26 here.
> 
> about:config shows
> Preference Name StatusTypeValue
> mailnews.force_charset_override default   boolean false


Let me rephrase that:

True is not the default setting for mailnews.force_charset_override in
SeaMonkey 2.26 here.

about:config shows
Preference Name   StatusTypeValue
mailnews.force_charset_override   default   boolean false

Clearly, false is the default setting.

Dennis

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey