no one wrote:
On Monday, January 11, 2021 at 12:09:55 PM UTC, no one wrote:
After rereading this thread I started from the beginning and noticed on my
system the only way to get the unicode setting to remain as default
in the composer window is to actually select "default for locale"
unicode
On Monday, January 11, 2021 at 12:09:55 PM UTC, no one wrote:
> After rereading this thread I started from the beginning and noticed on my
> system the only way to get the unicode setting to remain as default
> in the composer window is to actually select "default for locale"
> unicode is not
After rereading this thread I started from the beginning and noticed on my
system the only way to get the unicode setting to remain as default
in the composer window is to actually select "default for locale"
unicode is not available as an option in the
On 22/12/2020 15:05, no one wrote:
...>
Silly me, expecting the configuration to be available via seamonkey mail, I mean who wouldn't expect it to be located in the browser ;)
...
You can always save an email containing a link to (like
this one) if you wish.
But your entire previous
no one wrote:
this "solution" doesn't make much sense? "1- Enter about:config"
where/what do you mean by this, enter the file? a hidded menu? maybe
a console somewhere..
Dave, if you enter "about:config" (without the double quotes) in the
addressbar and accept the warning, you get to see all
no one wrote:
this "solution" doesn't make much sense? "1- Enter about:config"
where/what do you mean by this, enter the file? a hidded menu? maybe
a console somewhere..
Dave, if you enter "about:config" (without the double quotes) in the
addressbar and accept the warning, you get to see all
> > this "solution" doesn't make much sense? "1- Enter about:config"
> > where/what do you mean by this, enter the file? a hidded menu? maybe
> > a console somewhere..
> >
> Dave, if you enter "about:config" (without the double quotes) in the
> addressbar and accept the warning, you get to
Dave Barber wrote on 25/11/20 20:53:
On Monday, 11 March 2019 at 16:34:35 UTC, Rubens wrote:
Rubens wrote on 25/02/2019 13:32:
Hello all,
I am receiving some Unicode-encoded e-mails which look garbled
because Seamonkey always try to display them with Western
encoding in the first place, so
On 25/11/2020 09:53, Dave Barber wrote:
...> this "solution" doesn't make much sense? "1- Enter
about:config" where/what do you mean by this, enter the file? a
hidded menu? maybe a console somewhere..
In the address bar, where you would put http://www.mozilla.org. Perhaps
you knew this and
On Monday, 11 March 2019 at 16:34:35 UTC, Rubens wrote:
> Rubens wrote on 25/02/2019 13:32:
> >
> > Hello all,
> >
> >
> > I am receiving some Unicode-encoded e-mails which look garbled because
> > Seamonkey always try to display them with Western encoding in the first
> > place,
> > so I
j...@comcast.com wrote on 14/03/2019 15:11:
On Mon, 25 Feb 2019 13:32:00 +0100, Rubens in
mozilla.support.seamonkey wrote:
so I always have to manually change the Text Encoding option for every Unicode
e-mail I read.
Just a wild thought, does the user you are reading the email as have
j...@comcast.com wrote on 14/03/2019 15:11:
On Mon, 25 Feb 2019 13:32:00 +0100, Rubens in
mozilla.support.seamonkey wrote:
so I always have to manually change the Text Encoding option for every Unicode
e-mail I read.
Just a wild thought, does the user you are reading the email as have
On Mon, 25 Feb 2019 13:32:00 +0100, Rubens in
mozilla.support.seamonkey wrote:
>so I always have to manually change the Text Encoding option for every Unicode
>e-mail I read.
Just a wild thought, does the user you are reading the email as have
authority to make global changes in the
Rubens wrote on 25/02/2019 13:32:
Hello all,
I am receiving some Unicode-encoded e-mails which look garbled because
Seamonkey always try to display them with Western encoding in the first place,
so I always have to manually change the Text Encoding option for every Unicode
e-mail I read.
In
Nuno Silva wrote on 05/03/2019 21:32:
On 2019-03-05, Rubens wrote:
Rubens wrote:
I am receiving some Unicode-encoded e-mails which look garbled because
Seamonkey always try to display them with Western encoding in the first place,
so I always have to manually change the Text Encoding option
Rubens via support-seamonkey wrote:
Hello all,
I am receiving some Unicode-encoded e-mails which look garbled because
Seamonkey always try to display them with Western encoding in the first
place,
so I always have to manually change the Text Encoding option for every
Unicode e-mail I read.
On 2019-03-05, Rubens wrote:
>>> Rubens wrote:
I am receiving some Unicode-encoded e-mails which look garbled because
Seamonkey always try to display them with Western encoding in the first
place,
so I always have to manually change the Text Encoding option for every
Rubens wrote on 26/02/2019 22:38:
Paul Bergsagel wrote on 26/02/2019 02:14:
Rubens wrote:
Hello all,
I am receiving some Unicode-encoded e-mails which look garbled because
Seamonkey always try to display them with Western encoding in the first place,
so I always have to manually change the
Paul Bergsagel wrote on 26/02/2019 02:14:
Rubens wrote:
Hello all,
I am receiving some Unicode-encoded e-mails which look garbled because
Seamonkey always try to display them with Western encoding in the first place,
so I always have to manually change the Text Encoding option for every
Rubens wrote:
Hello all,
I am receiving some Unicode-encoded e-mails which look garbled because
Seamonkey always try to display them with Western encoding in the first
place,
so I always have to manually change the Text Encoding option for every
Unicode e-mail I read.
In the "Text
Hello all,
I am receiving some Unicode-encoded e-mails which look garbled because
Seamonkey always try to display them with Western encoding in the first place,
so I always have to manually change the Text Encoding option for every Unicode
e-mail I read.
In the "Text Encoding - Message
21 matches
Mail list logo
