On Sunday, 1 Nov 2015 at 17:25, Uwe Brauer wrote: [...]
Post by Uwe BrauerBut what if I don't know the type? The beauty of the interactive
call is that it offers various possibilities which I never
remember by heart.
I am confused. In your OP, you said you wanted to erroneously set
the type, e.g. to application/octet-stream. Either you know what
you want to set to (erroneously) or the problem is a more
fundamental one in your mailcap settings? That is, if I
misunderstood you and you in fact want to correct erroneous file
types, the problem is not with mml-xxx but with your system's
settings which mml uses to determine file types.
Ok here is the longer story. It concerns Xemacs and GNU emacs, tex files
and latin-1 and UTF-8 encoding.
Xemacs 21.5.X still uses Mule, while GNU emacs has moved to UFT-8
internally as far as I know.
Now the problem is the following:
- I send a latex file with latin-1 chars, buffer coding is set to
latin-1, via gnus as text/x-tex type to a Xemacs user: the
coding is corrupted.
- I send a latex file with latin-1 chars, buffer coding is set to
UTF-8, via gnus as text/x-tex type to a Xemacs user: the
coding is ok.
Now
- the user sends it back, but now it is the other way around: if he
sends using buffer coding is set to latin-1 via gnus as text/x-tex type
to me: the coding is ok
- The user sends it back, buffer coding is set to
UTF-8 via gnus as text/x-tex type me: the
coding is corrupted.
GNU emacs ---UTF8-> Xemacs OK
Xemacs ---latin-1-> GNU emacs ok
The problem can be circumvent using application/octet-stream then both
buffer codings are fine.
But I don't want that for every latex file.
That is why I want to be able to change the mml type, in case I made a
mistake, or using the dired function (since this much more comfortable
to use) which would allow me to chose the coding
Uwe Brauer