Re: SeaMonkey 2.48 release

[Frank-Rainer Grahl]

These are actually the release notes for the 2.48 beta 1. The final notes 
contain a few more items but overall not much changed.

FRG

David E. Ross wrote:

On 7/23/2017 12:58 PM, Frank-Rainer Grahl wrote:

https://www.seamonkey-project.org/releases/seamonkey2.48/
Updates release notes and the release itself should hopefully appear in the
next 48h. Bug 1351985 needs to be fixed for the update server:

https://bugzilla.mozilla.org/show_bug.cgi?id=1351985
FRG


Yesterday, I downloaded SeaMonkey 2.48 from
 but delayed
installing until I could read the release notes.  I followed your link
to the notes, read them, and installed 2.48 about 5 hours ago.  So far,
everything seems to work very well, including those of my 28 extensions
that I have exercised.



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

Re: SeaMonkey 2.48 release

[David E. Ross]

On 7/23/2017 12:58 PM, Frank-Rainer Grahl wrote:
> https://www.seamonkey-project.org/releases/seamonkey2.48/
> Updates release notes and the release itself should hopefully appear in the 
> next 48h. Bug 1351985 needs to be fixed for the update server:
> 
> https://bugzilla.mozilla.org/show_bug.cgi?id=1351985
> FRG

Yesterday, I downloaded SeaMonkey 2.48 from
 but delayed
installing until I could read the release notes.  I followed your link
to the notes, read them, and installed 2.48 about 5 hours ago.  So far,
everything seems to work very well, including those of my 28 extensions
that I have exercised.

-- 
David Ross


President Trump now denies there are any tapes that
recorded his conversations with ex-FBI Director Comey.
Between when Trump hinted there might be such tapes
and his denial, there was sufficient time to destroy
any tapes.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey 2.48 release

[Chris Ilias]

On 2017-07-23 6:08 PM, Cruz, Jaime wrote:

WaltS48 wrote:

On 7/22/17 1:57 PM, EE wrote:

I got the SeaMonkey 2.48 release version yesterday from the Mozilla
FTP site.  It is not yet on the SeaMonkey project release page.  Why?


Cause it hasn't been officially released, the developers are putting
some finishing touches on release notes and other fine tuning like
putting it on the SeaMonkey project release page. AIUI.


It has been "advertised" as available at DistroWatch for the past week:
http://distrowatch.com/


This situation is covered in the second blog post I linked to[1]. 
DistroWatch is flat-out wrong, and as a result, should not be trusted. 
If there's something wrong with the builds ewong uploaded, and they have 
to be re-spun before release, there are going to be people with bad 
builds because they downloaded it from DistroWatch.


[1]

--
Chris Ilias 
Newsgroup moderator
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey 2.48 release

[WaltS48]

On 7/23/17 6:08 PM, Cruz, Jaime wrote:

WaltS48 wrote:

On 7/22/17 1:57 PM, EE wrote:

I got the SeaMonkey 2.48 release version yesterday from the Mozilla
FTP site.  It is not yet on the SeaMonkey project release page.  Why?


Cause it hasn't been officially released, the developers are putting
some finishing touches on release notes and other fine tuning like
putting it on the SeaMonkey project release page. AIUI.




It has been "advertised" as available at DistroWatch for the past week:
http://distrowatch.com/




Well, you have to be careful with those fake news sites. ;)

--
Go Bucs!
Coexist 
National Popular Vote 
Ubuntu 16.04LTS - Unity Desktop
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey 2.48 release

[Cruz, Jaime]

WaltS48 wrote:

On 7/22/17 1:57 PM, EE wrote:

I got the SeaMonkey 2.48 release version yesterday from the Mozilla
FTP site.  It is not yet on the SeaMonkey project release page.  Why?


Cause it hasn't been officially released, the developers are putting
some finishing touches on release notes and other fine tuning like
putting it on the SeaMonkey project release page. AIUI.




It has been "advertised" as available at DistroWatch for the past week:
http://distrowatch.com/


--
Jaime A. Cruz
President
Nassau Wings Motorcycle Club
http://www.nassauwings.org/

AMA District 34
http://www.AMADistrict34.com/
Freddy's Run
http://www.freddysrun.org/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey 2.48 release

[Frank-Rainer Grahl]

> Actually, my add-ons were fine, except I had to do a minor patch to most of
> my themes to fix the Error Console.
Yes now part of SeaMonkey. Already in the Beta 1 release notes:

https://www.seamonkey-project.org/releases/seamonkey2.48/
Updates release notes and the release itself should hopefully appear in the 
next 48h. Bug 1351985 needs to be fixed for the update server:


https://bugzilla.mozilla.org/show_bug.cgi?id=1351985
FRG

EE wrote:

Frank-Rainer Grahl wrote:
ewong is still running verifications and hasn't given the green light yet. 
Probably tomorrow. He said he missed something but we knew that updates were 
not working. The builds (full installers) are good. I am waiting with the 
release notes till I know it only affects updates and/or the partials and 
not pulling from the official sites.


You can pick it but please backup your profile before installing. Some new 
breaking changes in the Gecko code which might break some older add-ons.

FRG

EE wrote:
I got the SeaMonkey 2.48 release version yesterday from the Mozilla FTP 
site. It is not yet on the SeaMonkey project release page.  Why?


Actually, my add-ons were fine, except I had to do a minor patch to most of my 
themes to fix the Error Console.




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

Re: SeaMonkey 2.48 release

[EE]

Frank-Rainer Grahl wrote:
ewong is still running verifications and hasn't given the green light 
yet. Probably tomorrow. He said he missed something but we knew that 
updates were not working. The builds (full installers) are good. I am 
waiting with the release notes till I know it only affects updates 
and/or the partials and not pulling from the official sites.


You can pick it but please backup your profile before installing. Some 
new breaking changes in the Gecko code which might break some older 
add-ons.

FRG

EE wrote:
I got the SeaMonkey 2.48 release version yesterday from the Mozilla 
FTP site. It is not yet on the SeaMonkey project release page.  Why?


Actually, my add-ons were fine, except I had to do a minor patch to most 
of my themes to fix the Error Console.


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

Re: SeaMonkey 2.48 release

[EE]

Felix Miata wrote:

EE composed on 2017-07-22 10:57 (UTC-0700):


I got the SeaMonkey 2.48 release version yesterday from the Mozilla FTP
site.  It is not yet on the SeaMonkey project release page.  Why?


Could it be because https://archive.mozilla.org/pub/seamonkey/releases/2.48/
lacks Win64?


Maybe.  I am using MacOS.


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

Re: Encoding without headers

[EE]

Richmond wrote:

"Paul B. Gallagher"  writes:


I should say that it doesn't seem to be using the default of
 because 224 represents
à on that system.


Yes and no.

Yes, it's not using that system.

No, 0224 is à but 224 is α, AFAICT.


What do you mean? that 0224 is hex? That would make it more than 8
bits. 224 is decimal in the table, the hex is above: e0.


One byte can be 0-FF in hexadecimal.  In decimal, that is 0-255.

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

Re: Encoding without headers

[Stanimir Stamenkov via support-seamonkey]

Sun, 23 Jul 2017 17:54:57 +0100, /Richmond/:

Stanimir Stamenkov writes:

Sun, 23 Jul 2017 12:00:15 +0100, /Richmond/:

Richmond writes:

If someone posts the characters Left Double Quotation Mark “ or Right 
Double Quotation Mark ” without any mime headers to indicate the encoding, 
Seamonkey seems to manage to display them anyway, whereas Gnus displays 
\223 \224. How is Seamonkey managing to find out what these codes mean? and 
how can I find out what character encoding it has chosen to use?


Can Seamonkey change encodings in the middle of an article? For example if 
I use Greek Drachma Sign 𐅻 will that appear?


I should say that it doesn't seem to be using the default of 
https://en.wikipedia.org/wiki/ISO/IEC_8859-1 because 224 represents à on 
that system.


I guess it is because browsers generally default to Windows-1252 (see the 
table in the last point 8):


https://www.w3.org/TR/html51/syntax.html#determining-the-character-encoding


According to https://en.wikipedia.org/wiki/Windows-1252 char 224 is à
too.


Seems like you've found the answer (in another reply to this thread) – 
the 224 number is octal, which corresponds to HEX 94... Who uses/needs 
octal nowadays – gosh, it is confusing to programmers, even.


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

Re: Encoding without headers

[Richmond via support-seamonkey]

mozilla-lists.mbou...@spamgourmet.com writes:

> Gnus probably makes different assumptions. It might be that it assumes
> 7-bit ASCII and displays any bytes >127 as \xxx. Or it might be that
> it assumes an 8-bit encoding which happens not to define 223 and
> 224. Or it might be that it assumes utf-8 but, since the single bytes
> 223 and 224 are not valid utf-8 sequences, it displays them as \223
> and \224.

I think I have found the answer. Those numbers are in octal! Who would
have guessed it?

https://www.experts-exchange.com/questions/26616492/html2latex-rendering-quotes-as-93-94-and-223-224-in-vim-emacs-what's-goning-on.html
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Encoding without headers

[Richmond via support-seamonkey]

Stanimir Stamenkov  writes:

> Sun, 23 Jul 2017 12:00:15 +0100, /Richmond/:
>> Richmond writes:
>>
>>> If someone posts the characters Left Double Quotation Mark “ or Right
>>> Double Quotation Mark ” without any mime headers to indicate the encoding,
>>> Seamonkey seems to manage to display them anyway, whereas Gnus displays
>>> \223 \224. How is Seamonkey managing to find out what these codes mean? and
>>> how can I find out what character encoding it has chosen to use?
>>>
>>> Can Seamonkey change encodings in the middle of an article? For example if
>>> I use Greek Drachma Sign 𐅻 will that appear?
>>
>> I should say that it doesn't seem to be using the default of
>> https://en.wikipedia.org/wiki/ISO/IEC_8859-1 because 224 represents à on
>> that system.
>
> I guess it is because browsers generally default to Windows-1252 (see the
> table in the last point 8):
>
> https://www.w3.org/TR/html51/syntax.html#determining-the-character-encoding

According to https://en.wikipedia.org/wiki/Windows-1252 char 224 is à
too.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Encoding without headers

[Richmond via support-seamonkey]

"Paul B. Gallagher"  writes:

>> I should say that it doesn't seem to be using the default of
>>  because 224 represents
>> à on that system.
>
> Yes and no.
>
> Yes, it's not using that system.
>
> No, 0224 is à but 224 is α, AFAICT.

What do you mean? that 0224 is hex? That would make it more than 8
bits. 224 is decimal in the table, the hex is above: e0.

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

Re: Encoding without headers

[Paul B. Gallagher]

Richmond wrote:


Richmond  writes:


If someone posts the characters Left Double Quotation Mark “ or
Right Double Quotation Mark ” without any mime headers to indicate
the encoding, Seamonkey seems to manage to display them anyway,
whereas Gnus displays \223 \224. How is Seamonkey managing to find
out what these codes mean? and how can I find out what character
encoding it has chosen to use?

Can Seamonkey change encodings in the middle of an article? For
example if I use Greek Drachma Sign 𐅻 will that appear?


I should say that it doesn't seem to be using the default of
 because 224 represents
à on that system.


Yes and no.

Yes, it's not using that system.

No, 0224 is à but 224 is α, AFAICT.

--
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: OT Re: Google not displaying

[Ed Mullen]

On 7/23/17 at 12:01 AM, Daniel created this epitome of digital genius:

On 23/07/2017 12:57 AM, Ed Mullen wrote:

On 7/21/17 at 2:00 PM, Spyhunter created this epitome of digital genius:

This is my user agent : Mozilla/5.0 (Windows NT 10.0; Win64; x64;
rv:54.0) Gecko/20100101 Firefox/54.0 SeaMonkey/2.51 Lightning/5.6

The one by default with Seamonkey 2.51.

What's your SeaMonkey version ?




Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:54.0) Gecko/20100101
Firefox/54.0 SeaMonkey/2.51

That's the default UA.



Just by-the-by 

Does/Can a "Default UA" for SM include the FF version?? Or does 
selecting to "Advertise FF compatibility" in Prefs make it a non-Default 
UA??




With AFFC unchecked the UA is:

Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:54.0) Gecko/20100101 
SeaMonkey/2.51


--
Ed Mullen
http://edmullen.net/
Show me a man with both feet firmly on the ground, and I'll show you a 
man who can't get his pants off.

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

Re: Encoding without headers

[Stanimir Stamenkov via support-seamonkey]

Sun, 23 Jul 2017 12:00:15 +0100, /Richmond/:

Richmond writes:

If someone posts the characters Left Double Quotation Mark “ or Right 
Double Quotation Mark ” without any mime headers to indicate the 
encoding, Seamonkey seems to manage to display them anyway, whereas Gnus 
displays \223 \224. How is Seamonkey managing to find out what these 
codes mean? and how can I find out what character encoding it has chosen 
to use?


Can Seamonkey change encodings in the middle of an article? For example 
if I use Greek Drachma Sign 𐅻 will that appear?


I should say that it doesn't seem to be using the default of 
https://en.wikipedia.org/wiki/ISO/IEC_8859-1 because 224 represents à on 
that system.


I guess it is because browsers generally default to Windows-1252 (see 
the table in the last point 8):


https://www.w3.org/TR/html51/syntax.html#determining-the-character-encoding

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

Re: Encoding without headers

[mozilla-lists . mbourne]

Richmond via support-seamonkey wrote:

If someone posts the characters Left Double Quotation Mark “ or
Right Double Quotation Mark ” without any mime headers to indicate
the encoding, Seamonkey seems to manage to display them anyway,
whereas Gnus displays \223 \224. How is Seamonkey managing to find
out what these codes mean? and how can I find out what character
encoding it has chosen to use?


At Edit > Preferences > Mail & Newsgroups > Text Encoding is an option 
"Fallback Text Encoding" with an explanation "Used for legacy content 
that does not declare its encoding". I haven't confirmed, but that 
suggests this option determines the encoding assumed in the situation 
you describe. For me, it's set to "Default for Current Locale"; I'm not 
sure whether that's picked up from the SeaMonkey UI language or the OS.


Gnus probably makes different assumptions. It might be that it assumes 
7-bit ASCII and displays any bytes >127 as \xxx. Or it might be that it 
assumes an 8-bit encoding which happens not to define 223 and 224. Or it 
might be that it assumes utf-8 but, since the single bytes 223 and 224 
are not valid utf-8 sequences, it displays them as \223 and \224.



Can Seamonkey change encodings in the middle of an article?


No. The whole page/email/message is in the same encoding. That's not a 
limitation of SeaMonkey, but defined by the protocols it uses.



For
example if I use Greek Drachma Sign 𐅻 will that appear?


Only if you're using a character set which includes that character as 
well. If you use the Unicode character set, e.g. with the utf-8 encoding 
(which it appears you did for your post), you can use characters which 
would otherwise be in different character sets. The font used to display 
the message on the recipient's system has to include the characters for 
them to be displayed though, and few if any fonts include all defined 
Unicode characters.


The font I'm currently using doesn't include the Greek Drachma Sign, so 
all I see is a box with "01017B" in it, that being the Unicode code 
point for Greek Drachma Sign. Someone else might see that character as 
intended (as might you) it they use a font which includes it.


(In case anyone else shares my initial confusion, 01017B is indeed named 
"Greek Drachma Sign" in the Ancient Greek Numbers block of the 
Supplementary Multilingual Plane; there's also 0020AF named just 
"Drachma Sign" in the Currency Symbols block of the Basic Multilingual 
Plane, which is a different character)


--
Mark

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

Re: Encoding without headers

[Richmond via support-seamonkey]

Richmond  writes:

> If someone posts the characters Left Double Quotation Mark “ or Right
> Double Quotation Mark ” without any mime headers to indicate the
> encoding, Seamonkey seems to manage to display them anyway, whereas Gnus
> displays \223 \224. How is Seamonkey managing to find out what these
> codes mean? and how can I find out what character encoding it has chosen
> to use?
>
> Can Seamonkey change encodings in the middle of an article? For example
> if I use Greek Drachma Sign 𐅻 will that appear?

I should say that it doesn't seem to be using the default of
https://en.wikipedia.org/wiki/ISO/IEC_8859-1 because 224 represents à on
that system.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Encoding without headers

[Richmond via support-seamonkey]

If someone posts the characters Left Double Quotation Mark “ or Right
Double Quotation Mark ” without any mime headers to indicate the
encoding, Seamonkey seems to manage to display them anyway, whereas Gnus
displays \223 \224. How is Seamonkey managing to find out what these
codes mean? and how can I find out what character encoding it has chosen
to use?

Can Seamonkey change encodings in the middle of an article? For example
if I use Greek Drachma Sign 𐅻 will that appear?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Message filters

[rogersonsteve]

I am using 2.46

If I try to edit my message filters or create a new one, I can't because the 
bar where it says to move message to is greyed and it says no available 
folders. The existing filters still work and send the emails to the folders to 
which they should go despite this now being greyed out. But if I try to edit 
it, it won't let me because I haven't specified a folder. Same problem if I try 
to create a new filter.

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

Re: Message filters

[rogersonsteve]

I should have said, I am using Mac Os 10.9.5
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey