[OpenSPARC-T2-DV] / tools / perl-5.8.0 / doc / MHonArc / faq / msgpgs.html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML//EN">
<HTML>
<HEAD>
<TITLE>MHonArc FAQ: Message Pages</TITLE></HEAD>
<BODY>

<!--X-NavButtons-Start-->
<p align=center>
[<a href="indexpgs.html">Prev</a>][<a href="threads.html">Next</a>][<a href="faq.html">TOC</a>][<a href="http://www.mhonarc.org/">Home</a>]
</p>
<!--X-NavButtons-End-->

<!-- ===================================================================== -->
<hr>
<H2><a name="messagepages">Message Pages</a></H2>

<!--X-TOC-Start-->
<ul>
<li><a href="#msgorder">Can I change the order the message resources are printed?</a></li>
<li><a href="#msghead">How can I change how message headers gets formatted?</a></li>
<li><a href="#msgbody">How can I change how message body data gets formatted?</a></li>
<li><a href="#headnbody">Can I have the message header come after the body?</a></li>
<li><a href="#msgbody">Can I make changes to message formatting on existing archived messages?</a></li>
<li><a href="#msgcomms">What are those "&lt;!--X-... -->"?</a></li>
<li><a href="#commslegal">Are those "&lt;!--X-... -->" legal comments?</a></li>
</ul>
<!--X-TOC-End-->

<!-- ??????????????????????????????????????????????????????????????? -->
<hr noshade size=1>
<table border=0>
<tr valign=top><td><img src="monicon.png" align="bottom" alt=""></td><td>
<h3><b><a name="msgorder">Can I change the order the message resources are printed?</a></b></h3>
</td></tr></table>

<p>No.  However, with the exceptions of the message header and body
(but see next questions), those resource can be defined
anyway you like.  For example, I can change the TOPLINKS resource
to look like the BOTLINKS resource.  Or, I can change the
default meaning of the resource so it really outputs something
else entirely.  If you look at the documentation, the resources
are just defined by HTML markup and resource variables.  Many
of the resource variables can be used within any resource.
</p>

<!-- ??????????????????????????????????????????????????????????????? -->
<hr noshade size=1>
<table border=0>
<tr valign=top><td><img src="monicon.png" align="bottom" alt=""></td><td>
<h3><b><a name="msghead">How can I change how message headers gets formatted?</a></b></h3>
</td></tr></table>

<p>There are several resources for controlling how message headers
are converted into HTML.  You can exclude fields and style fields
with your own HTML markup.  For example, here are resources that
cause message headers to be formatted with a table:
</p>
<pre>
<b>&lt;FIELDSBEG></b>
&lt;table>
&lt;tbody>
<b>&lt;/FIELDSBEG></b>
<b>&lt;LABELBEG></b>
&lt;tr>
&lt;td align="right" valign="top">
<b>&lt;/LABELBEG></b>
<b>&lt;LABELEND></b>
&lt;/td>
<b>&lt;/LABELEND></b>
<b>&lt;FLDBEG></b>
&lt;td align="left">
<b>&lt;/FLDBEG></b>
<b>&lt;FLDEND></b>
&lt;/td>
&lt;/tr>
<b>&lt;/FLDEND></b>
<b>&lt;FIELDSEND></b>
&lt;/tbody>
&lt;/table>
<b>&lt;/FIELDSEND></b>
</pre>

<p>You can also control the order message fields are displayed:
</p>
<pre>
<b>&lt;FIELDORDER></b>
from
subject
date
-extra-
<b>&lt;/FIELDORDER></b>
</pre>
<p>The "-extra-" signifies all other message fields in alphabetic
order.
</p>

<p>You can also exclude specific message fields:
</p>
<pre>
<b>&lt;EXCS></b>
x-
precendence
<b>&lt;/EXCS></b>
</pre>
<p>Here, we are exluding all "X-..." fields and the Precendence
field.
</p>

<p>Consult the MHonArc documentation for more information
on how to use the resources shown here and other resources for
controlling message header formatting.
</p>

<!-- ??????????????????????????????????????????????????????????????? -->
<hr noshade size=1>
<table border=0>
<tr valign=top><td><img src="monicon.png" align="bottom" alt=""></td><td>
<h3><b><a name="msgbody">How can I change how message body data gets formatted?</a></b></h3>
</td></tr></table>

<p>Message body conversion are controlled by content-type filters.
See the <a href="mime.html">MIME</a> section of this FAQ for
more information.
</p>

<!-- ??????????????????????????????????????????????????????????????? -->
<hr noshade size=1>
<table border=0>
<tr valign=top><td><img src="monicon.png" align="bottom" alt=""></td><td>
<h3><b><a name="headnbody">Can I have the message header come after the body?</a></b></h3>
</td></tr></table>

<p>In general, no.  A limitation of MHonArc is that you cannot change
the relative order of the resources/message-data in the output (but see
other questions in this section).  MHonArc expects
a specific order so it can edit archived messages when needed w/o
using a bunch of logic, and performance degradation (special comment
declarations are used to mark off the different sections of a message).
Therefore, you cannot have the body come before the message header.
The best you can do is suppress the header (via EXCS) and create a
bogus header via the resource variables available.  For example:
</p>
<pre>
<b>&lt;EXCS override></b>
.
<b>&lt;/EXCS></b>
<b>&lt;MSGFOOT></b>
&lt;ul>
&lt;li>From: $FROM$
&lt;li>Subject: $SUBJECTNA$
&lt;li>Date: $DATE$
&lt;ul>
<b>&lt;/MSGFOOT></b>
</pre>

<!-- ??????????????????????????????????????????????????????????????? -->
<hr noshade size=1>
<table border=0>
<tr valign=top><td><img src="monicon.png" align="bottom" alt=""></td><td>
<h3><b><a name="msgbody">Can I make changes to message formatting on existing archived messages?</a></b></h3>
</td></tr></table>

<p>Yes, mostly.  The only thing cannot be changed once converted
is the message header and message body.  All other parts of the
message page can be changed at any time.  To make any changes
appear on existing archived messages, set the EDITIDX resource.
The EDITIDX resource tells MHonArc to recreate all archive
pages.
</p>

<!-- ??????????????????????????????????????????????????????????????? -->
<hr noshade size=1>
<table border=0>
<tr valign=top><td><img src="monicon.png" align="bottom" alt=""></td><td>
<h3><b><a name="msgcomms">What are those "&lt;!--X-... -->"?</a></b></h3>
</td></tr></table>

<p>If you ever looked at the HTML source of converted messages,
you will notice a bunch of comment declarations, "&lt;!--X-... -->".
These comment declarations are used by MHonArc to
properly edit messages when needed.  Therefore, <strong>DO NOT
MESS WITH THEM</strong>.
</p>

<!-- ??????????????????????????????????????????????????????????????? -->
<hr noshade size=1>
<table border=0>
<tr valign=top><td><img src="monicon.png" align="bottom" alt=""></td><td>
<h3><b><a name="commslegal">Are those "&lt;!--X-... -->" legal comments?</a></b></h3>
</td></tr></table>

<p>Yes.
</p>

<!-- ===================================================================== -->
<hr>

<!--X-NavButtons-Start-->
<p align=center>
[<a href="indexpgs.html">Prev</a>][<a href="threads.html">Next</a>][<a href="faq.html">TOC</a>][<a href="http://www.mhonarc.org/">Home</a>]
</p>
<!--X-NavButtons-End-->

<HR>
<address>
$Date: 2001/12/24 14:38:39 $ <br>
<img align="top" src="monicon.png" alt="">
<a href="http://www.mhonarc.org/"
><strong>MHonArc</strong></a><br>
Copyright &#169; 1997-1999, <a href="http://www.earlhood.com/"
>Earl Hood</a>, <a href="mailto:mhonarc@mhonarc.org"
>mhonarc@mhonarc.org</a><br>
</address>
</BODY>
</HTML>
Commit	Line	Data
86530b38 AT	1	<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML//EN">
	2	<HTML>
	3	<HEAD>
	4	<TITLE>MHonArc FAQ: Message Pages</TITLE></HEAD>
	5	<BODY>
	6
	7	<!--X-NavButtons-Start-->
	8	<p align=center>
	9	[<a href="indexpgs.html">Prev</a>][<a href="threads.html">Next</a>][<a href="faq.html">TOC</a>][<a href="http://www.mhonarc.org/">Home</a>]
	10	</p>
	11	<!--X-NavButtons-End-->
	12
	13	<!-- ===================================================================== -->
	14	<hr>
	15	<H2><a name="messagepages">Message Pages</a></H2>
	16
	17	<!--X-TOC-Start-->
	18	<ul>
	19	<li><a href="#msgorder">Can I change the order the message resources are printed?</a></li>
	20	<li><a href="#msghead">How can I change how message headers gets formatted?</a></li>
	21	<li><a href="#msgbody">How can I change how message body data gets formatted?</a></li>
	22	<li><a href="#headnbody">Can I have the message header come after the body?</a></li>
	23	<li><a href="#msgbody">Can I make changes to message formatting on existing archived messages?</a></li>
	24	<li><a href="#msgcomms">What are those "<!--X-... -->"?</a></li>
	25	<li><a href="#commslegal">Are those "<!--X-... -->" legal comments?</a></li>
	26	</ul>
	27	<!--X-TOC-End-->
	28
	29	<!-- ??????????????????????????????????????????????????????????????? -->
	30	<hr noshade size=1>
	31	<table border=0>
	32	<tr valign=top><td><img src="monicon.png" align="bottom" alt=""></td><td>
	33	<h3><b><a name="msgorder">Can I change the order the message resources are printed?</a></b></h3>
	34	</td></tr></table>
	35
	36	<p>No. However, with the exceptions of the message header and body
	37	(but see next questions), those resource can be defined
	38	anyway you like. For example, I can change the TOPLINKS resource
	39	to look like the BOTLINKS resource. Or, I can change the
	40	default meaning of the resource so it really outputs something
	41	else entirely. If you look at the documentation, the resources
	42	are just defined by HTML markup and resource variables. Many
	43	of the resource variables can be used within any resource.
	44	</p>
	45
	46	<!-- ??????????????????????????????????????????????????????????????? -->
	47	<hr noshade size=1>
	48	<table border=0>
	49	<tr valign=top><td><img src="monicon.png" align="bottom" alt=""></td><td>
	50	<h3><b><a name="msghead">How can I change how message headers gets formatted?</a></b></h3>
	51	</td></tr></table>
	52
	53	<p>There are several resources for controlling how message headers
	54	are converted into HTML. You can exclude fields and style fields
	55	with your own HTML markup. For example, here are resources that
	56	cause message headers to be formatted with a table:
	57	</p>
	58	<pre>
	59	<b><FIELDSBEG></b>
	60	<table>
	61	<tbody>
	62	<b></FIELDSBEG></b>
	63	<b><LABELBEG></b>
	64	<tr>
65	<td align="right" valign="top">
66	<b></LABELBEG></b>
67	<b><LABELEND></b>
68	</td>
69	<b></LABELEND></b>
70	<b><FLDBEG></b>
71	<td align="left">
72	<b></FLDBEG></b>
73	<b><FLDEND></b>
74	</td>
75	</tr>
76	<b></FLDEND></b>
77	<b><FIELDSEND></b>
78	</tbody>
79	</table>
80	<b></FIELDSEND></b>
81	</pre>
82
83	<p>You can also control the order message fields are displayed:
84	</p>
85	<pre>
86	<b><FIELDORDER></b>
87	from
88	subject
89	date
90	-extra-
91	<b></FIELDORDER></b>
92	</pre>
93	<p>The "-extra-" signifies all other message fields in alphabetic
94	order.
95	</p>
96
97	<p>You can also exclude specific message fields:
98	</p>
99	<pre>
100	<b><EXCS></b>
101	x-
102	precendence
103	<b></EXCS></b>
104	</pre>
105	<p>Here, we are exluding all "X-..." fields and the Precendence
106	field.
107	</p>
108
109	<p>Consult the MHonArc documentation for more information
110	on how to use the resources shown here and other resources for
111	controlling message header formatting.
112	</p>
113
114	<!-- ??????????????????????????????????????????????????????????????? -->
115	<hr noshade size=1>
116	<table border=0>
117	<tr valign=top><td><img src="monicon.png" align="bottom" alt=""></td><td>
118	<h3><b><a name="msgbody">How can I change how message body data gets formatted?</a></b></h3>
119	</td></tr></table>
120
121	<p>Message body conversion are controlled by content-type filters.
122	See the <a href="mime.html">MIME</a> section of this FAQ for
123	more information.
124	</p>
125
126	<!-- ??????????????????????????????????????????????????????????????? -->
127	<hr noshade size=1>
128	<table border=0>
129	<tr valign=top><td><img src="monicon.png" align="bottom" alt=""></td><td>
130	<h3><b><a name="headnbody">Can I have the message header come after the body?</a></b></h3>
131	</td></tr></table>
132
133	<p>In general, no. A limitation of MHonArc is that you cannot change
134	the relative order of the resources/message-data in the output (but see
135	other questions in this section). MHonArc expects
136	a specific order so it can edit archived messages when needed w/o
137	using a bunch of logic, and performance degradation (special comment
138	declarations are used to mark off the different sections of a message).
139	Therefore, you cannot have the body come before the message header.
140	The best you can do is suppress the header (via EXCS) and create a
141	bogus header via the resource variables available. For example:
142	</p>
143	<pre>
144	<b><EXCS override></b>
145	.
146	<b></EXCS></b>
147	<b><MSGFOOT></b>
148	<ul>
149	<li>From: $FROM$
150	<li>Subject: $SUBJECTNA$
151	<li>Date: $DATE$
152	<ul>
153	<b></MSGFOOT></b>
154	</pre>
155
156	<!-- ??????????????????????????????????????????????????????????????? -->
157	<hr noshade size=1>
158	<table border=0>
159	<tr valign=top><td><img src="monicon.png" align="bottom" alt=""></td><td>
160	<h3><b><a name="msgbody">Can I make changes to message formatting on existing archived messages?</a></b></h3>
161	</td></tr></table>
162
163	<p>Yes, mostly. The only thing cannot be changed once converted
164	is the message header and message body. All other parts of the
165	message page can be changed at any time. To make any changes
166	appear on existing archived messages, set the EDITIDX resource.
167	The EDITIDX resource tells MHonArc to recreate all archive
168	pages.
169	</p>
170
171	<!-- ??????????????????????????????????????????????????????????????? -->
172	<hr noshade size=1>
173	<table border=0>
174	<tr valign=top><td><img src="monicon.png" align="bottom" alt=""></td><td>
175	<h3><b><a name="msgcomms">What are those "<!--X-... -->"?</a></b></h3>
176	</td></tr></table>
177
178	<p>If you ever looked at the HTML source of converted messages,
179	you will notice a bunch of comment declarations, "<!--X-... -->".
180	These comment declarations are used by MHonArc to
181	properly edit messages when needed. Therefore, <strong>DO NOT
182	MESS WITH THEM</strong>.
183	</p>
184
185	<!-- ??????????????????????????????????????????????????????????????? -->
186	<hr noshade size=1>
187	<table border=0>
188	<tr valign=top><td><img src="monicon.png" align="bottom" alt=""></td><td>
189	<h3><b><a name="commslegal">Are those "<!--X-... -->" legal comments?</a></b></h3>
190	</td></tr></table>
191
192	<p>Yes.
193	</p>
194
195	<!-- ===================================================================== -->
196	<hr>
197
198	<!--X-NavButtons-Start-->
199	<p align=center>
200	[<a href="indexpgs.html">Prev</a>][<a href="threads.html">Next</a>][<a href="faq.html">TOC</a>][<a href="http://www.mhonarc.org/">Home</a>]
201	</p>
202	<!--X-NavButtons-End-->
203
204	<HR>
205	<address>
206	$Date: 2001/12/24 14:38:39 $ <br>
207	<img align="top" src="monicon.png" alt="">
208	<a href="http://www.mhonarc.org/"
209	><strong>MHonArc</strong></a><br>
210	Copyright © 1997-1999, <a href="http://www.earlhood.com/"
211	>Earl Hood</a>, <a href="mailto:mhonarc@mhonarc.org"
212	>mhonarc@mhonarc.org</a><br>
213	</address>
214	</BODY>
215	</HTML>