Version 2.0	15 Fen 1995
	Miscellaneous minor changes and tweaks in preparation for the
	release with the Xew-3.1 MIME viewer (miew).

Version 1.4	14 Sep 1993
	Initialize all new MsgBodies to text/plain or message/rfc822
	depending on parent (digest), default character set to US-ASCII
	and the content transfer encoding into 7bit. (In some special
	cases these initializations were not made properly.)

	In display.c Rictext handling, added "lt"->"<" mapping.

	If content-type had parameter "id", MamLoad erroneusly put this
	value into body->id field (which is reserved for Content-Id).

	MamLoad didn't parse (unfold) message/rfc822 if it was within
	multipart/digest without any further content type specification
	(child was not allocated and all of rfc822 text was put into
	content unparsed).

	Parsing functions for transfer-content-type/subtype parameters
	didn't return the updated pointer over the parsed value. fixed.

Version 1.3	2 July 1993

	MamDeleteFolder didn't remove associated type information from MFM,
	and MamMoveFolder omitted to return the result. Both fixed in Mam.c.

	Added character set initialization for text widgets, when the content
	type specificies character set parameter. Also, character set is now
	saved in MamSave (was omitted accidentally).

	When error is detected in decoding base64, instead of error, return
	whatever has been decoded up to that point.

	Following private parameter names in content-type have been changed
		x-type			x-eb-type
		x-subtype		x-eb-subtype
		x-transfer-type		x-eb-transfer-type
		x-transfer-subtype	x-eb-transfer-subtype
	In MamSave the original type/subtype string is used for unknown
	types, if the original is recorded in params (x-eb-type/x-eb-subtype).

	The first test with external body parts (anon-ftp only). Also, fixed
	a serious bug in freeing the content buffer, when widget content type
	was not known (buffer was free'd twice!)

Version 1.2	22 June 1993

	Fixes to test utilities mamtest and mamview.

	In tables.h, ST_external was defined as "external", when the correct
	string is "external-body".

	In display.c, hanlding of multipart/alternative changed (it showed
	all parts in certain situations). DisplayContent returns the top
	level widget of content in unmanaged state. Other tweaks made.

Version 1.1	4 June 1993

	DisplayContent (display.c) now handles multipart/alternative. Also,
	XawChain* symbols changed into XtChain* to allow compilation under
	X11R4.

	MamMakeHeader (and thus MamSaveMessage indirectly) require that if
	msgfname points to a directory, it must be typed as "eurobridge/
	message".

	Mfm{Put,Set,Get}ContentType worked incorrectly if the name parameter
	was actual filepath containing directories. Processing was made with
	the full path instead of the plain filename component.

	Inclusion of body content from a file to message header works
	now. MamLoad will always have content->filename==NULL, if content
	is taken from message header file; and otherwise it will always
	set content->length = -1, content->start_offset = 0.

	MamMoveFolder implemented (the code is same as MamMoveMessage).

	The change to use NewMessage from message.c caused x-transfer-type
	and x-transfer-subtype to multiply in content-type parameters. Every
	MamSaveMessage added new entries. This has been fixed.

Version 1.0	1 June 1993
