I think I understand, After all these notes.....
Content-type: What this thing is...
Content-Encoding: What you did to it to get it here....
and
Content-conversion: What I did to make the transport conveniet.
I proposed the Third header as a compromise between those who want to
load up the content-encoding (I oppose because it make automated UA's hard)
and recursive content-types (I'm not sure this solves the problem, and it
is a real pain for old fashoned users).
Example:
Content-type: WordPerfect ; 5.1
Content-encoding: Base 64
Content-conversion: Privacy-Enhansed, compressed
Time to shoot at a new target :-)
Greg V.