unify-8859-on-encoding-mode

unify-8859-on-encoding-mode

[Pavel Janík]

Hi,

JFYI: Eli notified me, that my e-mails are sent with

Content-Type: text/plain; charset=iso-8859-15

sometimes:

--- cut here ---
Btw, Pavel: I was surprised to see this header in your message:

  Content-Type: text/plain; charset=iso-8859-15

(which, of course, means the non-ASCII 0xED character in your name
was interpreted as Latin-9).  Is this some side effect of
unify-on-encode, and if so, is this something we should fix, or at
least be aware of, or maybe you don't mind?
--- cut here ---

When I sent an e-mail without any other ISO 8859-2 character (í can also
be encoded using IS-8859-1), it is sent as iso-8859-15.

When I sent an e-mail with some ISO 8859-2 character (that can not be
encoded using ISO 8859-1, I think), the whole e-mail is sent as iso-8859-2.

When I disable unify-8859-on-encoding-mode (via M-x
unify-8859-on-encoding-mode), all e-mails are sent as iso8859-2.

I can provide any other details on request.

This is JFYI, that turning this on can have various effects.
-- 
Pavel Janík

After 40 Terabytes, your fingers start to hurt.
                  -- David Miller about typing

Re: unify-8859-on-encoding-mode

[Stefan Monnier]

> JFYI: Eli notified me, that my e-mails are sent with
> 
> Content-Type: text/plain; charset=iso-8859-15
> 
> sometimes:
> 
> --- cut here ---
> Btw, Pavel: I was surprised to see this header in your message:
> 
>   Content-Type: text/plain; charset=iso-8859-15
> 
> (which, of course, means the non-ASCII 0xED character in your name
> was interpreted as Latin-9).  Is this some side effect of
> unify-on-encode, and if so, is this something we should fix, or at
> least be aware of, or maybe you don't mind?

Clearly it's wrong: assuming that his language environment is setup so
that his preferred coding-system is latin-2, when either of latin-1,
latin-2 or latin-9 can be used to encode the region, latin-2 should
be chosen.

Pavel does the same thing happen when writing a file ?
E.g. starting with an empty file, enter your name, save
the file and check the coding-system used for writing.


	Stefan

Re: unify-8859-on-encoding-mode

[Pavel Janík]

   From: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>
   Date: Wed, 03 Apr 2002 11:17:04 -0500

   > Pavel does the same thing happen when writing a file ?
   > E.g. starting with an empty file, enter your name, save
   > the file and check the coding-system used for writing.

No, it does not happen with files. So I think it is connected to Gnus
only. I use current CVS Gnus for handling mail.
-- 
Pavel Janík

Have you considered defenestrating your computer and replacing Windows with
GNU/Linux?  It is a shame for you to be in bondage to Microsoft.
                  -- Richard Stallman <rms@gnu.org> in emacs-devel

unify-8859-on-encoding-mode

[Richard Stallman]

How come unify-8859-on-encoding-mode is not enabled by default?
I thought we had decided to enable it.

Re: unify-8859-on-encoding-mode

[Kai Großjohann]

Richard Stallman <rms@gnu.org> writes:

> How come unify-8859-on-encoding-mode is not enabled by default?
> I thought we had decided to enable it.

The functionality is enabled, even though the variable is nil.  You
can test it yourself: open a file, type ä.  C-x RET f latin-1 RET C-x
C-s C-x RET f latin-9 RET C-x C-s.  If it wasn't enabled, one of the
two saves should have asked a question.

kai
-- 
Silence is foo!

Re: unify-8859-on-encoding-mode

[Richard Stallman]

    > How come unify-8859-on-encoding-mode is not enabled by default?
    > I thought we had decided to enable it.

    The functionality is enabled, even though the variable is nil.

Does that mean the variable is obsolete?  If so, let's get rid of it.
At the very least, the doc string seems not to be accurate, so
it would be good to fix it.