mhonarc-commits
[Top] [All Lists]

CVS: mhonarc/MHonArc/doc/resources mimealtprefs.html,1.2,1.3 mimeexcs.html,...

2002-11-13 19:58:42
Update of /cvsroot/mhonarc/mhonarc/MHonArc/doc/resources
In directory subversions:/tmp/cvs-serv3947

Modified Files:
	mimealtprefs.html mimeexcs.html mimefilters.html 
Log Message:
* Additions and corrections.


Index: mimealtprefs.html
===================================================================
RCS file: /cvsroot/mhonarc/mhonarc/MHonArc/doc/resources/mimealtprefs.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -r1.2 -r1.3
*** mimealtprefs.html	27 Jul 2002 05:13:10 -0000	1.2
--- mimealtprefs.html	14 Nov 2002 02:58:33 -0000	1.3
***************
*** 52,56 ****
  the last filterable media-type is normally used.  However, it is sometimes
  desirable to override this behavior for certain media-types.  For example,
! it has become more common for many MUAs to generate the following
  message structures:
  </p>
--- 52,56 ----
  the last filterable media-type is normally used.  However, it is sometimes
  desirable to override this behavior for certain media-types.  For example,
! it has become common for many MUAs to generate the following
  message structures:
  </p>
***************
*** 60,74 ****
      text/html</pre>
  
! <p>A message with HTML, and a plain text equivalent for those receiving
! MUAs who may not be able to render HTML in email.  When MHonArc processes
  such a message, MHonArc will use the <tt>text/html</tt> part since it
  is filterable and comes after <tt>text/plain</tt>.
  </p>
  
! <p>There are some who would like to have nothing to do with HTML in
! email.  Or, due to security concerns, would prefer to not minimize the
! amount of HTML from email in their archives.  With MIMEALTPREFS, you
! can tell MHonArc to prefer the <tt>text/plain</tt> over the <tt>text/html</tt>
! part with the following setting:
  </p>
  <pre>
--- 60,73 ----
      text/html</pre>
  
! <p>A message with HTML and a plain text equivalent for receiving
! MUAs who cannot render HTML.  When MHonArc processes
  such a message, MHonArc will use the <tt>text/html</tt> part since it
  is filterable and comes after <tt>text/plain</tt>.
  </p>
  
! <p>There are many who would like to have nothing to do with HTML in
! email, like for security reasons.  With MIMEALTPREFS, you can tell
! MHonArc to use the <tt>text/plain</tt> entity (if it exists) over
! the <tt>text/html</tt> part with the following setting:
  </p>
  <pre>
***************
*** 103,110 ****
  <p>So which entity will MHonArc actually use?  In this case,
  the <tt>text/enriched</tt> part will be used.  The reason is that
! the <tt>text/html</tt> will be excluded since there does exist a
! <tt>text/plain</tt> alternative entity.  However, MHonArc still
! tries to use the last filterable alternative part, which in this
! case is <tt>text/enriched</tt>.
  </p>
  
--- 102,109 ----
  <p>So which entity will MHonArc actually use?  In this case,
  the <tt>text/enriched</tt> part will be used.  The reason is that
! the <tt>text/html</tt> will be excluded since a
! <tt>text/plain</tt> alternative entity exists.  However, MHonArc still
! tries to use the last filterable alternative part, which is
! <tt>text/enriched</tt> in this case.
  </p>
  

Index: mimeexcs.html
===================================================================
RCS file: /cvsroot/mhonarc/mhonarc/MHonArc/doc/resources/mimeexcs.html,v
retrieving revision 1.7
retrieving revision 1.8
diff -C2 -r1.7 -r1.8
*** mimeexcs.html	27 Jul 2002 05:13:10 -0000	1.7
--- mimeexcs.html	14 Nov 2002 02:58:33 -0000	1.8
***************
*** 115,118 ****
--- 115,119 ----
  
  <p>
+ <a href="mimealtprefs.html">MIMEALTPREFS</a>,
  <a href="mimefilters.html">MIMEFILTERS</a>
  </p>

Index: mimefilters.html
===================================================================
RCS file: /cvsroot/mhonarc/mhonarc/MHonArc/doc/resources/mimefilters.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -C2 -r1.16 -r1.17
*** mimefilters.html	21 Oct 2002 16:55:19 -0000	1.16
--- mimefilters.html	14 Nov 2002 02:58:33 -0000	1.17
***************
*** 80,83 ****
--- 80,90 ----
  </P>
  
+ <H3><a name="defaultfilters">Default Filters</a></H3>
+ 
+ <p>MHonArc provides an existing set of filters which should be sufficient
+ for most of your needs.  For information about the filters, see
+ the <a href="#default"><cite>Default Setting</cite></a> section below.
+ </p>
+ 
  <H3><a name="writefilters">Writing Filters</a></H3>
  
***************
*** 98,111 ****
  </table>
  
- <table border=0 cellpadding=4>
- <tr valign=top>
- <td><strong>NOTE</strong></td>
- <td><p>The default filters provided by MHonArc are described
- in the <strong>Default Settings</strong> section.
- </p>
- </td>
- </tr>
- </table>
- 
  <H4>Function Interface of Filter</H4>
  
--- 105,108 ----
***************
*** 144,148 ****
  the <tt>Received:</tt> header field is typically repeated
  multiple times.  For fields that only occur once,
! then array for the field will only contain one
  item.
  </p>
--- 141,145 ----
  the <tt>Received:</tt> header field is typically repeated
  multiple times.  For fields that only occur once,
! the array for the field will only contain one
  item.
  </p>
***************
*** 152,157 ****
  <tr valign=top>
  <td><strong><code>$body_data_ref</code></strong></td>
! <td><p>Reference to body data.  It is okay for the
! filter to modify the text in-place.
  </p>
  </td>
--- 149,154 ----
  <tr valign=top>
  <td><strong><code>$body_data_ref</code></strong></td>
! <td><p>Reference to body data.  The filter can safely
! modify referenced data.
  </p>
  </td>
***************
*** 270,274 ****
  <!-- *************************************************************** -->
  <hr>
! <h2>Default Setting</h2>
  
  <table border=0 cellpadding=4>
--- 267,271 ----
  <!-- *************************************************************** -->
  <hr>
! <h2><a name="default">Default Setting</a></h2>
  
  <table border=0 cellpadding=4>
***************
*** 312,315 ****
--- 309,330 ----
  </p>
  
+ <table border=0 cellpadding=4>
+ <tr valign=top>
+ <td><strong>NOTE</strong></td>
+ <td><p>The default filters use a <a href="mimeargs.html">MIMEARGS</a>
+ argument style similiar to HTML attribute values.  For example:
+ </p>
+ <pre>
+ <b>&lt;MIMEArgs&gt;</b>
+ m2h_text_plain::filter; attachcheck fancyquote maxwidth=80
+ <b>&lt;/MIMEArgs&gt;</b>
+ </pre>
+ <p>If writing your own filters, you are encouraged to use the same
+ style for consistency.
+ </p>
+ </td>
+ </tr>
+ </table>
+ 
  <hr size=0 noshade width="50%">
  <H3><a name="m2h_external">m2h_external::filter</a></h3>
***************
*** 344,348 ****
  <P>By default, the filter ignores any filename specification
  given in the message when writing the data to disk. 
! A unique filename with an extenstion based upon sub-type is
  generated.
  </P>
--- 359,363 ----
  <P>By default, the filter ignores any filename specification
  given in the message when writing the data to disk. 
! A unique filename with an extension based upon sub-type is
  generated.
  </P>
***************
*** 350,354 ****
  <p><strong><tt>m2h_external::filter</tt></strong> can take the
  following
! <a href="mimeargs.html">arguments</a>:
  </p>
  
--- 365,369 ----
  <p><strong><tt>m2h_external::filter</tt></strong> can take the
  following
! <a href="mimeargs.html">MIMEARGS arguments</a>:
  </p>
  
***************
*** 428,432 ****
  The subdirectory will be called "<tt>msg<var>MSGNUM</var></tt>".
  This option may be useful if <strong><tt>usename</tt></strong> is
! specified to avoid security and name conflict problems.
  </p></td>
  </tr>
--- 443,447 ----
  The subdirectory will be called "<tt>msg<var>MSGNUM</var></tt>".
  This option may be useful if <strong><tt>usename</tt></strong> is
! specified to minimize security and name conflict problems.
  </p></td>
  </tr>
***************
*** 449,456 ****
  <td><strong><tt>usename</tt></strong></td>
  <td><p>Use (file)name attribute for determining name
! of derived file.  Use this option with caution
  since it can lead to filename conflicts and
! security problems (however, see the <strong><tt>subdir</tt></strong>
! option).
  </p></td>
  </tr>
--- 464,473 ----
  <td><strong><tt>usename</tt></strong></td>
  <td><p>Use (file)name attribute for determining name
! of derived file.
! </p>
! <p><strong><font color="red">CAUTION</font></strong>:
! Use this option with caution
  since it can lead to filename conflicts and
! security problems.
  </p></td>
  </tr>
***************
*** 458,465 ****
  <td><strong><tt>usenameext</tt></strong></td>
  <td><p>Use (file)name attribute for determining the extension
! of derived file.  Use this option with caution
! since it can lead to
! security problems (however, see the <strong><tt>subdir</tt></strong>
! option).
  </p></td>
  </tr>
--- 475,483 ----
  <td><strong><tt>usenameext</tt></strong></td>
  <td><p>Use (file)name attribute for determining the extension
! of derived file.
! </p>
! <p><strong><font color="red">CAUTION</font></strong>:
! Use this option with caution since it can lead to
! security problems.
  </p></td>
  </tr>
***************
*** 1321,1325 ****
  <p><strong><tt>m2h_msg_extbody::filter</tt></strong> can take the
  following
! <a href="mimeargs.html">arguments</a>:
  </p>
  
--- 1339,1343 ----
  <p><strong><tt>m2h_msg_extbody::filter</tt></strong> can take the
  following
! <a href="mimeargs.html">MIMEARGS arguments</a>:
  </p>
  
***************
*** 1351,1407 ****
  <tr valign=top>
  <td><strong>&lt;Bold&gt;</strong></td>
! <td>&lt;B&gt;</td>
  </tr>
  <tr valign=top>
  <td><strong>&lt;Italic&gt;</strong></td>
! <td>&lt;I&gt;</td>
  </tr>
  <tr valign=top>
  <td><strong>&lt;Underline&gt;</strong></td>
! <td>&lt;U&gt;</td>
  </tr>
  <tr valign=top>
  <td><strong>&lt;Fixed&gt;</strong></td>
! <td>&lt;TT&gt;</td>
  </tr>
  <tr valign=top>
  <td><strong>&lt;Smaller&gt;</strong></td>
! <td>&lt;SMALL&gt;</td>
  </tr>
  <tr valign=top>
  <td><strong>&lt;Bigger&gt;</strong></td>
! <td>&lt;BIG&gt;</td>
  </tr>
  <tr valign=top>
  <td><strong>&lt;FontFamily&gt;&lt;Param&gt;<var>family</var>&lt;/Param&gt;</strong></td>
! <td>&lt;FONT face="<var>family</var>"&gt;</td>
  </tr>
  <tr valign=top>
  <td><strong>&lt;Color&gt;&lt;Param&gt;<var>color</var>&lt;/Param&gt;</strong></td>
! <td>&lt;FONT color="<var>color</var>"&gt;</td>
  </tr>
  <tr valign=top>
  <td><strong>&lt;Center></strong></td>
! <td>&lt;P align="center"&gt;</td>
  </tr>
  <tr valign=top>
  <td><strong>&lt;FlushLeft&gt;</strong></td>
! <td>&lt;P align="left"&gt;</td>
  </tr>
  <tr valign=top>
  <td><strong>&lt;FlushRight&gt;</strong></td>
! <td>&lt;P align="right"&gt;</td>
  </tr>
  <tr valign=top>
  <td><strong>&lt;FlushBoth&gt;</strong></td>
! <td>&lt;P align="both"&gt; <em>(not supported in HTML)</em></td>
  </tr>
  <tr valign=top>
  <td><strong>&lt;ParaIndent&gt;</strong></td>
! <td>&lt;BLOCKQUOTE&gt;</td>
  </tr>
  <tr valign=top>
  <td><strong>&lt;Excerpt&gt;</strong></td>
! <td>&lt;BLOCKQUOTE&gt;</td>
  </tr>
  <tr valign=top>
--- 1369,1425 ----
  <tr valign=top>
  <td><strong>&lt;Bold&gt;</strong></td>
! <td>&lt;b&gt;</td>
  </tr>
  <tr valign=top>
  <td><strong>&lt;Italic&gt;</strong></td>
! <td>&lt;i&gt;</td>
  </tr>
  <tr valign=top>
  <td><strong>&lt;Underline&gt;</strong></td>
! <td>&lt;u&gt;</td>
  </tr>
  <tr valign=top>
  <td><strong>&lt;Fixed&gt;</strong></td>
! <td>&lt;tt&gt;</td>
  </tr>
  <tr valign=top>
  <td><strong>&lt;Smaller&gt;</strong></td>
! <td>&lt;small&gt;</td>
  </tr>
  <tr valign=top>
  <td><strong>&lt;Bigger&gt;</strong></td>
! <td>&lt;big&gt;</td>
  </tr>
  <tr valign=top>
  <td><strong>&lt;FontFamily&gt;&lt;Param&gt;<var>family</var>&lt;/Param&gt;</strong></td>
! <td>&lt;font face="<var>family</var>"&gt;</td>
  </tr>
  <tr valign=top>
  <td><strong>&lt;Color&gt;&lt;Param&gt;<var>color</var>&lt;/Param&gt;</strong></td>
! <td>&lt;font color="<var>color</var>"&gt;</td>
  </tr>
  <tr valign=top>
  <td><strong>&lt;Center></strong></td>
! <td>&lt;p align="center"&gt;</td>
  </tr>
  <tr valign=top>
  <td><strong>&lt;FlushLeft&gt;</strong></td>
! <td>&lt;p align="left"&gt;</td>
  </tr>
  <tr valign=top>
  <td><strong>&lt;FlushRight&gt;</strong></td>
! <td>&lt;p align="right"&gt;</td>
  </tr>
  <tr valign=top>
  <td><strong>&lt;FlushBoth&gt;</strong></td>
! <td>&lt;p align="justify"&gt;</td>
  </tr>
  <tr valign=top>
  <td><strong>&lt;ParaIndent&gt;</strong></td>
! <td>&lt;blockquote&gt;</td>
  </tr>
  <tr valign=top>
  <td><strong>&lt;Excerpt&gt;</strong></td>
! <td>&lt;blockquote&gt;</td>
  </tr>
  <tr valign=top>
***************
*** 1431,1439 ****
  <tr valign=top>
  <td><strong><font color="red">CAUTION</font></strong></td>
! <td><p>
! If you are worried about security, it is recommended that you disable
! support of text/html messages in your mail archives.  There is no
  guarantee that this filter is robust enough to eliminate all possible
! exploits that can occur with HTML data.
  </p>
  </td>
--- 1449,1460 ----
  <tr valign=top>
  <td><strong><font color="red">CAUTION</font></strong></td>
! <td><p>If you are worried about security, it is recommended that you disable
! support of HTML messages in your mail archives.  There is no
  guarantee that this filter is robust enough to eliminate all possible
! exploits that can occur with HTML data.  See the
! <a href="mimealtprefs.html">MIMEALTPREFS</a> and
! <a href="mimeexcs.html">MIMEEXCS</a> resource and the
! <a href="#m2h_null">m2h_null::filter</a> on ways to exclude
! HTML data.
  </p>
  </td>
***************
*** 1503,1507 ****
  <p><strong><tt>m2h_text_html::filter</tt></strong> can take the
  following
! <a href="mimeargs.html">arguments</a>:
  </p>
  
--- 1524,1528 ----
  <p><strong><tt>m2h_text_html::filter</tt></strong> can take the
  following
! <a href="mimeargs.html">MIMEARGS arguments</a>:
  </p>
  
***************
*** 1513,1518 ****
  server-side includes.  Normally, comment declarations are munged
  to protect against potential exploits, but this option will
! disable that behavior.  Use this options with <strong>EXTREME</strong>
! care.
  </p></td>
  </tr>
--- 1534,1542 ----
  server-side includes.  Normally, comment declarations are munged
  to protect against potential exploits, but this option will
! disable that behavior.
! </p>
! <p><strong><font color="red">CAUTION</font></strong>:
! Using this option can open up security vulnerabilies, including the
! potential accessing of server resources.
  </p></td>
  </tr>
***************
*** 1533,1540 ****
  <td><strong><tt>allowscript</tt></strong></td>
  <td><p>Preserve any markup associated with scripting.
! This includes elements and attributes related to scripting.  This option
! can cause security problems for your archive since someone can introduce
! foreign client-side code.  Use this options with <strong>EXTREME</strong>
! care.
  </p></td>
  </tr>
--- 1557,1566 ----
  <td><strong><tt>allowscript</tt></strong></td>
  <td><p>Preserve any markup associated with scripting.
! This includes elements and attributes related to scripting.
! </p>
! <p><strong><font color="red">CAUTION</font></strong>:
! Use of this option can open up your archives to cross-site scripting (XSS)
! attacks.  It is highly recommended to not use this option, especially
! for publicly accessible archives.
  </p></td>
  </tr>
***************
*** 1548,1552 ****
  with a link to it from the message page.
  </p>
! <p><b>CAUTION:</b> If <tt>attachcheck</tt> is specified, the HTML
  data is saved "as-is".  For example, no stripping of scripting-based
  markup is performed and no resolution of cid URLs are performed.
--- 1574,1579 ----
  with a link to it from the message page.
  </p>
! <p><strong><font color="red">CAUTION</font></strong>:
! If <tt>attachcheck</tt> is specified, the HTML
  data is saved "as-is".  For example, no stripping of scripting-based
  markup is performed and no resolution of cid URLs are performed.
***************
*** 1555,1559 ****
  <tr valign=top>
  <td><strong><tt>nofont</tt></strong></td>
! <td><p>Remove font tags.
  </p></td>
  </tr>
--- 1582,1586 ----
  <tr valign=top>
  <td><strong><tt>nofont</tt></strong></td>
! <td><p>Remove font tags and styles.
  </p></td>
  </tr>
***************
*** 1578,1582 ****
  
  <p>The default behavior of the filter is wrap the data in
! the HTML PRE element and escape special characters.  It will
  also convert text that looks like a URL into a hyperlink.
  If the data contains non-ASCII character, the filter will
--- 1605,1609 ----
  
  <p>The default behavior of the filter is wrap the data in
! the HTML <tt>PRE</tt> element and escape special characters.  It will
  also convert text that looks like a URL into a hyperlink.
  If the data contains non-ASCII character, the filter will
***************
*** 1595,1601 ****
  </table>
  
  <p><strong><tt>m2h_text_plain::filter</tt></strong> can take the
  following
! <a href="mimeargs.html">arguments</a>:
  </p>
  
--- 1622,1644 ----
  </table>
  
+ <p>This filter supports text data donoted with flowed sematics as
+ defined by <a href="http://www.ietf.org/rfc/rfc2646.txt";>RFC 2646</a>.
+ Quoted text will be wrapped in HTML <tt>BLOCKQUOTE</tt> tags with
+ inline CSS styles to highlight quoted text with a vertical bar in the
+ left margin as follows:
+ </p>
+ <blockquote style="border-left: #0000FF solid 0.1em; margin-left: 0.0em; padding-left: 1.0em">This is some quoted text.
+ This is some quoted text.
+ This is some quoted text.
+ This is some quoted text.
+ This is some quoted text.</blockquote>
+ 
+ <p>CSS style customization can be done by using the
+ <tt>quoteclass</tt> argument described below.
+ </p>
+ 
  <p><strong><tt>m2h_text_plain::filter</tt></strong> can take the
  following
! <a href="mimeargs.html">MIMEARGS arguments</a>:
  </p>
  
***************
*** 1627,1634 ****
  </tr>
  <tr valign=top>
! <td><strong><tt>inlineexts=</tt></strong><var>ext1</var><tt>,</tt>...</td>
! <td><p>A comma separated list of message specified filename
! extensions to treat as inline data.
! Applicable only when <b><tt>uudecode</tt></b> is specified.
  </p>
  </tr>
--- 1670,1692 ----
  </tr>
  <tr valign=top>
! <td><strong><tt>disableflowed</tt></strong></td>
! <td><p>Flowed sematics will be ignored for text denoted with flowed
! formatting.
! </p>
! <p><strong>Note:</strong> The effects the <tt>fancyquote</tt> and
! <tt>quote</tt> will still occur if either option is specified.
! </tr>
! <tr valign=top>
! <td><strong><tt>fancyquote</tt></strong></td>
! <td><p>Highlight quoted message text.  Quoted text will be wrapped
! in HTML <tt>BLOCKQUOTE</tt> elements.  By default, inline CSS style
! settings are generated to render a vertical bar in the left margin.  The
! inline styles are suppressed if the <tt>quoteclass</tt> option is set.
! </p>
! <p>This option generates similiar rendering of quoted text as is done
! for flowed text data, but without the flowed text wrapping sematics.
! </p>
! <p><strong>Note:</strong> If message text is denoted as flowed text by
! message headers, the text will always be rendered with flowed sematics.
  </p>
  </tr>
***************
*** 1642,1645 ****
--- 1700,1710 ----
  </tr>
  <tr valign=top>
+ <td><strong><tt>inlineexts=</tt></strong><var>ext1</var><tt>,</tt>...</td>
+ <td><p>A comma separated list of message specified filename
+ extensions to treat as inline data.
+ Applicable only when <b><tt>uudecode</tt></b> is specified.
+ </p>
+ </tr>
+ <tr valign=top>
  <td><strong><tt>keepspace</tt></strong></td>
  <td><p>Preserve all spaces if the <strong><tt>nonfixed</tt></strong>
***************
*** 1657,1664 ****
  <tr valign=top>
  <td><strong><tt>nonfixed</tt></strong></td>
! <td><p>Do not wrap message text in the HTML PRE element.  This will
  cause text to be rendered in the default font (which is normally
  proportionally spaced).  Each line of the message will have
! a <tt>&lt;BR&gt;</tt> appended in order to preserve the line representation
  of the message.
  </p>
--- 1722,1729 ----
  <tr valign=top>
  <td><strong><tt>nonfixed</tt></strong></td>
! <td><p>Do not wrap message text in the HTML <tt>PRE</tt> element.  This will
  cause text to be rendered in the default font (which is normally
  proportionally spaced).  Each line of the message will have
! a <tt>&lt;br&gt;</tt> appended in order to preserve the line representation
  of the message.
  </p>
***************
*** 1671,1680 ****
  <tr valign=top>
  <td><strong><tt>quote</tt></strong></td>
! <td><p>Italicize quoted message text.
  </p>
  </tr>
  <tr valign=top>
  <td><strong><tt>target=</tt></strong><var>name</var></td>
! <td><p>Set the TARGET attribute of an anchor links generated from
  hyperlinking URLs.
  </p>
--- 1736,1761 ----
  <tr valign=top>
  <td><strong><tt>quote</tt></strong></td>
! <td><p>Italicize quoted message text.  Any quoted lines in the message
! will be wrapped in the HTML <tt>I</tt> element.
! </p>
! <p>Compare this with the <tt>fancyquote</tt> option.
! </p>
! </tr>
! <tr valign=top>
! <td><strong><tt>quoteclass=</tt></strong><var>classname</var></td>
! <td><p>CSS classname to use for quoted text.  This option applies only
! for flowed text data or if <tt>fancyquote</tt> is specified.  The
! <var>classname</var> will be the value of the <tt>CLASS</tt> attbribute
! for the <tt>BLOCKQUOTE</tt> elements, and this option suppresses the
! generation of inline styles.
! </p>
! <p>This option is useful for where a master stylesheet controls the
! appearance of archives.  By using this option, the master stylesheet
! has complete control on how quoted text in messages should be rendered.
  </p>
  </tr>
  <tr valign=top>
  <td><strong><tt>target=</tt></strong><var>name</var></td>
! <td><p>Set the TARGET attribute of anchors generated from
  hyperlinking URLs.
  </p>
***************
*** 1684,1688 ****
  <td><p>When decoding uuencoded data, use the full filename specified
  when write the data to disk instead of just the filename extension.
! <b>Note:</b> Be aware that there are potential security problems when
  using this option.
  </p></td>
--- 1765,1771 ----
  <td><p>When decoding uuencoded data, use the full filename specified
  when write the data to disk instead of just the filename extension.
! </p>
! <p><strong><font color="red">CAUTION</font></strong>:
! Be aware that there are potential security problems when
  using this option.
  </p></td>
***************
*** 1738,1742 ****
  <b>&lt;/MIMEFilters&gt;</b>
  </pre>
! <p>The markup returned by this filter displays the a one line description
  of what was excluded.  Examples:
  </p>
--- 1821,1825 ----
  <b>&lt;/MIMEFilters&gt;</b>
  </pre>
! <p>The markup returned by this filter displays the one line description
  of what was excluded.  Examples:
  </p>
***************
*** 1751,1754 ****
--- 1834,1856 ----
  </p>
  
+ <table border=0 cellpadding=4>
+ <tr valign=top>
+ <td><strong>NOTE</strong></td>
+ <td><p>The sematics of using the
+ <a href="mimeexcs.html">MIMEEXCS</a> resource vs this filter are different.
+ When using this filter, MHonArc considers the data
+ successfully converted.  But with <a href="mimeexcs.html">MIMEEXCS</a>,
+ MHonArc does not consider the data converted.  This is relevant when
+ MHonArc processes <tt>multipart/alternative</tt> entities and is
+ determing which alternative parts will be used.
+ </p>
+ <p>The <tt>m2h_null::filter</tt> existed before
+ <a href="mimeexcs.html">MIMEEXCS</a> was added to MHonArc, hence it mainly
+ exists for compatibility reasons.
+ </p>
+ </td>
+ </tr>
+ </table>
+ 
  <!-- *************************************************************** -->
  <hr>
***************
*** 1819,1823 ****
  <img align="top" src="../monicon.png" alt="">
  <a href="http://www.mhonarc.org";><strong>MHonArc</strong></a><br>
! Copyright &#169; 1997-2001 <a href="http://www.mhonarc.org/~ehood/";>Earl Hood</a>, <a href="mailto:mhonarc(_at_)mhonarc(_dot_)org">mhonarc(_at_)mhonarc(_dot_)org</a><br>
  </address>
  
--- 1921,1925 ----
  <img align="top" src="../monicon.png" alt="">
  <a href="http://www.mhonarc.org";><strong>MHonArc</strong></a><br>
! Copyright &#169; 1997-2002 <a href="http://www.mhonarc.org/~ehood/";>Earl Hood</a>, <a href="mailto:mhonarc(_at_)mhonarc(_dot_)org">mhonarc(_at_)mhonarc(_dot_)org</a><br>
  </address>
  

---------------------------------------------------------------------
To sign-off this list, send email to majordomo(_at_)mhonarc(_dot_)org with the
message text UNSUBSCRIBE MHONARC-DEV