		(Frequently Asked/Answered Questions)

			  Kazuhiko Yamamoto
			    March 3, 1995
		       kazu@is.aist-nara.ac.jp
	

* *iso-2022-jp*

Because Mew supports Mule(MULtilingual Enhancement to GNU Emacs),
byte-compile-file on pure Emacs shows following warnings.

	While compiling toplevel forms in file mew.el:
	  !! Symbol's value as variable is void ((*iso-2022-jp*))

Please don't care. It's not harmful since Mew never use *iso-2022-jp*
symbol in pure Emacs. *iso-2022-jp* means a standard charter set for
Japanese.


* ISO-8859-1

Both US-ASCII and ISO-8859-1 are supported on Emacs 19.

If you use character code other than US-ASCII and ISO-8859-1, please
use Mule. Mule is available by anonymous ftp from:

        etlport.etl.go.jp [192.31.197.99]:/pub/mule
        ftp.mei.co.jp [132.182.49.2]:/public/free/gnu/emacs/Mule
        sh.wide.ad.jp [133.4.11.11]:/JAPAN/mule/mule-1.0
        ftp.funet.fi [128.214.6.100]:/pub/gnu/emacs/mule
        cs.huji.ac.il [132.65.16.10]:/pub/gnu/mule


* PGP(Pretty Good Privacy)

Mew is tested with PGP 2.6ui(unofficial international version) and
2.6.i. But I hopefully guess Mew can work with any other version
higher than 2.3a.

PGP 2.6ui is available as follows;

ftp://ftp.demon.co.uk/pub/pgp/pgp26ui-src.tar.gz
ftp://ftp.aist-nara.ac.jp/pub/Security/tools/pgp/pgp26ui-src.tar.gz

PGP 2.6.i is available as follows;

ftp://ftp.dsi.unimi.it/pub/security/crypt/PGP/pgp26is.tar.gz
ftp://ftp.aist-nara.ac.jp/pub/Security/tools/pgp/pgp26is.tar.gz

Mew uses 'Content-Type: application/pgp' for its tag according to the
internet draft, "The application/pgp MIME Content-type"
(draft-borenstein-pgp-mime-00.txt). 

<<<<attention>>>

The auther of draft-borenstein-pgp-mime-00.txt withdrew this spec. I
don't know where PGP/MIME will go. X-(

Some people uses application/x-pgp as a tag. But Mew never support it.
If PGP message is not automatically decrypted or veryfied (or both)
due to luck of 'Content-Type: application/pgp', type C-cd in summary
mode to force decrypting or vrfying (or both).

At this time, Mew's PGP interface implementation is for conventional
usage only. Thus, you can sign up/encrypt to a plain text, but you
never sign up/encrypt to MIME and include PGP message in MIME
multipart.


* PEM(Privacy Enhanced Mail)

Mew supports only FJPEM. It's available from following site.

sh.wide.ad.jp:          /WIDE/free-ware/fjpem/fjpem1.1.tar.Z
ftp.wg.omron.co.jp:     /pub/security/tools/fjpem1.1.tar.Z
ftp.csce.kyushu-u.ac.jp:/pub/Security/tools/pem/fjpem1.1.tar.Z
ftp.u-tokyo.ac.jp:      /pub/Mail/security/fjpem1.1.tar.Z
ftp.iij.ad.jp:          /pub/security/WIDE/fjpem1.1.tar.Z
ftp.dit.co.jp:          /pub/security/WIDE/fjpem1.1.tar.Z
ftp.kuis.kyoto-u.ac.jp: /net/security/fjpem1.1.tar.Z
ftp.fujixerox.co.jp:    /pub/Unix/Security/fjpem1.1.tar.Z

I don't believe this PEM is useful for people other than Japanese
due to its Japanese documents and keyserv issue.

Please pay attention that Mew uses 'Content-Type:
Application/Pem-1421' as a tag. It is just to support conventional PEM
because there is no way to tell whether this message is a PEM or not
without tag. It's a just temporary solution for backward
compatibility.

Since Mew supports only conventional PEM, what you can do is just
sign or encrypt a plain text. You can't make a MIME message PEM or
include PEM to MIME multipart. 

* MOSS(was PEM/MIME)

PEM and MIME integration is proposed on 
	draft-ietf-pem-sigenc-03.txt
and
;;	draft-ietf-pem-mime-07.txt. --> moss draft

This spec is going to the final stage. I hope I can release our MOSS
package(COSMOS -- COSy MOSs) soon.


* To read application/pem-1421 with other application.

mhn:

Add following line to .mh_profile

	mhn-show-application/pem-1421: %l/usr/local/bin/pemcrypt -d -i < '%F' | $PAGER

Metamail:

Add following line to ~/.mailcap.

	application/pem-1421; /usr/local/bin/pemcrypt -d -i < %s ; 


* Mark based composing.

0.8x is the last version that adopts good old PEM and PGP composing. 
Later version will introduce mark based composing and eliminate old
one(e.g. composing of RFC1421 PEM). Please don't be confused and
understand that Mew is a research oriented interface to integrate
structured messages.

Mark based composer is also designed to support compression MIME
single part.  'mewencode' can make a gzip+base64-encoded message.


* Adjusting a multipart message after C-cC-m.

If you want to adjust a message after typing C-cC-m on draft mode,
please take care to modify appropriately. (You'd better learn MIME
syntax.) If the message is multipart, never insert string before the
first boundary and after the last boundary. The preamble and epilogue
is ignored by mail interface.


* xv

"xv" is a share ware to display gif, jpeg, bitmap and so on. If you
don't like to pay for it, alternative free software is "xloadimage" or
"display". I way change the default software to "display" to get rid
of the dependency of share ware.


* X-Face:

To display X-Face:, you need to set following three variables.

(defvar mew-x-face-filter '("uncompface" "ikon2xbm"))
(defvar mew-x-face-prog "xv")
(defvar mew-x-face-args nil)

"uncompface" and ikon2xbm are included "faces" package. It is
avairable from;

ftp://moose.cs.indiana.edu/pub/faces/faces/faces-1.6.1.tar.Z
ftp://ftp.ics.es.osaka-u.ac.jp/unix/misc/faces-1.6.1.tar.Z

Type "C-cC-x" to display X-Face: in summary mode.


--
