Update of /home/users/mhonarc.org/ehood/cvs/mhonarc/mhonarc/MHonArc/doc/resources
In directory denethor.mallorn.com:/tmp/cvs-serv32633/resources
Modified Files:
charsetconverters.html mimealtprefs.html mimeargs.html
mimedecoders.html mimeexcs.html mimefilters.html perlinc.html
textencode.html
Log Message:
Doc fixes and cleanup.
Index: charsetconverters.html
===================================================================
RCS file: /home/users/mhonarc.org/ehood/cvs/mhonarc/mhonarc/MHonArc/doc/resources/charsetconverters.html,v
retrieving revision 1.24
retrieving revision 1.25
diff -C2 -r1.24 -r1.25
*** charsetconverters.html 6 Oct 2003 22:04:16 -0000 1.24
--- charsetconverters.html 13 May 2005 18:50:38 -0000 1.25
***************
*** 61,65 ****
<p>The CHARSETCONVERTERS resource specifies Perl routines to call
! for filtering characters of a character set to HTML legal characters.
The filtering occurs for message header data encoded
according to the MIME standard.
--- 61,65 ----
<p>The CHARSETCONVERTERS resource specifies Perl routines to call
! for filtering characters of a character set to legal HTML characters.
The filtering occurs for message header data encoded
according to the MIME standard.
***************
*** 172,177 ****
or base64 (as specified by the MIME syntax). Therefore, the
called routine will be passed the raw byte data. It is important
! that the routine convert the data into a format suitable to be
! included in HTML markup.
</p>
--- 172,177 ----
or base64 (as specified by the MIME syntax). Therefore, the
called routine will be passed the raw byte data. It is important
! that the routine convert the data into a format suitable for
! inclusion within HTML markup.
</p>
***************
*** 387,393 ****
</p>
<p>For more information about using MHonArc in a Japanese locale,
! see (documents in Japanese):<br>
! <a href="http://www.shiratori.riec.tohoku.ac.jp/~p-katoh/Hack/Docs/mhonarc-jp/index.html";><http://www.shiratori.riec.tohoku.ac.jp/~p-katoh/Hack/Docs/mhonarc-jp/index.html></a><br>
! <a href="http://www.shiratori.riec.tohoku.ac.jp/~p-katoh/Hack/Docs/mhonarc-jp/mhonarc-jp-2_4.html";><http://www.shiratori.riec.tohoku.ac.jp/~p-katoh/Hack/Docs/mhonarc-jp/mhonarc-jp-2_4.html></a>
</p>
</dd>
--- 387,392 ----
</p>
<p>For more information about using MHonArc in a Japanese locale,
! see (documents in Japanese):
! <a href="http://www.mhonarc.jp/";><http://www.mhonarc.jp/></a>
</p>
</dd>
Index: mimealtprefs.html
===================================================================
RCS file: /home/users/mhonarc.org/ehood/cvs/mhonarc/mhonarc/MHonArc/doc/resources/mimealtprefs.html,v
retrieving revision 1.7
retrieving revision 1.8
diff -C2 -r1.7 -r1.8
*** mimealtprefs.html 6 Oct 2003 22:04:18 -0000 1.7
--- mimealtprefs.html 13 May 2005 18:50:38 -0000 1.8
***************
*** 78,82 ****
<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:
--- 78,84 ----
<p>There are many who would like to have nothing to do with HTML in
! email (for
! <a href="../faq/security.html#htmldata">security reasons</a>).
! 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:
***************
*** 93,97 ****
</p>
! <p>Note, MIMEALTPREFS augments the normal processing of
<tt>multipart/alternative</tt> entities. For example, say the following
message entity structure exists,
--- 95,99 ----
</p>
! <p>MIMEALTPREFS augments the normal processing of
<tt>multipart/alternative</tt> entities. For example, say the following
message entity structure exists,
***************
*** 111,116 ****
</pre>
! <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
--- 113,118 ----
</pre>
! <p>Which entity will MHonArc actually use? In this case,
! the <tt>text/enriched</tt> part will be used. The reason is
the <tt>text/html</tt> will be excluded since a
<tt>text/plain</tt> alternative entity exists. However, MHonArc still
***************
*** 134,141 ****
</p>
! <table border=0 cellpadding=4>
! <tr valign=top>
! <td><strong>NOTE</strong></td>
! <td><p>Each time <tt><MIMEALTPREFS></tt> occurs in a resource file,
the last encountered setting will override any previous values. Therefore,
specifying the <tt>override</tt> attribute is redundant.
--- 136,144 ----
</p>
! <table class="note" width="100%">
! <tr valign="baseline">
! <td><strong>NOTE:</strong></td>
! <td width="100%"><p>
! Each time <tt><MIMEALTPREFS></tt> occurs in a resource file,
the last encountered setting will override any previous values. Therefore,
specifying the <tt>override</tt> attribute is redundant.
***************
*** 192,196 ****
<img align="top" src="../monicon.png" alt="">
<a href="http://www.mhonarc.org/";><strong>MHonArc</strong></a><br>
! Copyright © 2002, <a href="http://www.earlhood.com/";
>Earl Hood</a>, <a href="mailto:mhonarc%40mhonarc.org";
>mhonarc<!--
--- 195,199 ----
<img align="top" src="../monicon.png" alt="">
<a href="http://www.mhonarc.org/";><strong>MHonArc</strong></a><br>
! Copyright © 2002,2005 <a href="http://www.earlhood.com/";
>Earl Hood</a>, <a href="mailto:mhonarc%40mhonarc.org";
>mhonarc<!--
Index: mimeargs.html
===================================================================
RCS file: /home/users/mhonarc.org/ehood/cvs/mhonarc/mhonarc/MHonArc/doc/resources/mimeargs.html,v
retrieving revision 1.14
retrieving revision 1.15
diff -C2 -r1.14 -r1.15
*** mimeargs.html 6 Oct 2003 22:04:18 -0000 1.14
--- mimeargs.html 13 May 2005 18:50:38 -0000 1.15
***************
*** 84,88 ****
<h2><a name="default">Default Setting</a></h2>
! <PRE>
<b><MIMEArgs></b>
m2h_external::filter; inline
--- 84,88 ----
<h2><a name="default">Default Setting</a></h2>
! <PRE class="code">
<b><MIMEArgs></b>
m2h_external::filter; inline
***************
*** 105,109 ****
</p>
! <PRE>
<b><MIMEArgs></b>
m2h_text_plain::filter; quote
--- 105,109 ----
</p>
! <PRE class="code">
<b><MIMEArgs></b>
m2h_text_plain::filter; quote
Index: mimedecoders.html
===================================================================
RCS file: /home/users/mhonarc.org/ehood/cvs/mhonarc/mhonarc/MHonArc/doc/resources/mimedecoders.html,v
retrieving revision 1.13
retrieving revision 1.14
diff -C2 -r1.13 -r1.14
*** mimedecoders.html 6 Oct 2003 22:04:18 -0000 1.13
--- mimedecoders.html 13 May 2005 18:50:38 -0000 1.14
***************
*** 63,72 ****
<p>The MIMEDECODERS resource can only be defined via the
resource file. Each line of the element specifies a encoding,
! the Perl routine for filtering the character set, and the Perl source
file containing the routine.
</p>
<p>Example:</p>
! <pre>
<b><MIMEDecoders></b>
base64; base64::b64decode; base64.pl
--- 63,72 ----
<p>The MIMEDECODERS resource can only be defined via the
resource file. Each line of the element specifies a encoding,
! the Perl decoding routine, and the Perl source
file containing the routine.
</p>
<p>Example:</p>
! <pre class="code">
<b><MIMEDecoders></b>
base64; base64::b64decode; base64.pl
***************
*** 105,109 ****
<h2><a name="default">Default Setting</a></h2>
! <pre>
<b><MIMEDecoders></b>
7bit; as-is;
--- 105,109 ----
<h2><a name="default">Default Setting</a></h2>
! <pre class="code">
<b><MIMEDecoders></b>
7bit; as-is;
***************
*** 133,137 ****
</p>
! <pre>
<b><MIMEDecoders></b>
base64; MIME::Base64::decode_base64; MIME/Base64.pm
--- 133,137 ----
</p>
! <pre class="code">
<b><MIMEDecoders></b>
base64; MIME::Base64::decode_base64; MIME/Base64.pm
Index: mimeexcs.html
===================================================================
RCS file: /home/users/mhonarc.org/ehood/cvs/mhonarc/mhonarc/MHonArc/doc/resources/mimeexcs.html,v
retrieving revision 1.13
retrieving revision 1.14
diff -C2 -r1.13 -r1.14
*** mimeexcs.html 6 Oct 2003 22:04:18 -0000 1.13
--- mimeexcs.html 13 May 2005 18:50:39 -0000 1.14
***************
*** 39,43 ****
<var>content-type</var><br>
<var>content-type</var><br>
! ...
<code></MIMEEXCS></code><br>
</p>
--- 39,43 ----
<var>content-type</var><br>
<var>content-type</var><br>
! ...<br>
<code></MIMEEXCS></code><br>
</p>
***************
*** 61,68 ****
a note that the part was excluded.
</p>
! <table border=0 cellpadding=4>
! <tr valign=top>
! <td><strong>NOTE</strong></td>
! <td><p>Base types can also be listed to exclude all content-types
with a give base. For example, <tt>image/jpg</tt> will only exclude
JPEG images, but <tt>image</tt> will exclude all images.
--- 61,69 ----
a note that the part was excluded.
</p>
! <table class="note" width="100%">
! <tr valign="baseline">
! <td><strong>NOTE:</strong></td>
! <td width="100%"><p>Base types can also be listed in order exclude all
! content-types
with a give base. For example, <tt>image/jpg</tt> will only exclude
JPEG images, but <tt>image</tt> will exclude all images.
***************
*** 101,106 ****
</pre>
! <p>The following is a very restrictive setting to minimize archive
! exploits and large data files:
</p>
<pre class="code">
--- 102,107 ----
</pre>
! <p>The following is a very restrictive setting to minimize security
! risks and large data files:
</p>
<pre class="code">
Index: mimefilters.html
===================================================================
RCS file: /home/users/mhonarc.org/ehood/cvs/mhonarc/mhonarc/MHonArc/doc/resources/mimefilters.html,v
retrieving revision 1.29
retrieving revision 1.30
diff -C2 -r1.29 -r1.30
*** mimefilters.html 5 Mar 2004 22:03:16 -0000 1.29
--- mimefilters.html 13 May 2005 18:50:39 -0000 1.30
***************
*** 121,125 ****
<table class="note" width="100%">
<tr valign=top>
! <td><strong>NOTE</strong></td>
<td width="100%"><p>As of v2.5 of MHonArc, the API for filters is different from
v2.4.x, and earlier. The following describes the v2.5 API for
--- 121,125 ----
<table class="note" width="100%">
<tr valign=top>
! <td><strong>NOTE:</strong></td>
<td width="100%"><p>As of v2.5 of MHonArc, the API for filters is different from
v2.4.x, and earlier. The following describes the v2.5 API for
***************
*** 224,228 ****
<table class="note" width="100%">
<tr valign=top>
! <td><strong>NOTE</strong></td>
<td width="100%"><p>If you want MHonArc to treat the data as filtered, but not
have anything displayed on the page, just return a string with
--- 224,228 ----
<table class="note" width="100%">
<tr valign=top>
! <td><strong>NOTE:</strong></td>
<td width="100%"><p>If you want MHonArc to treat the data as filtered, but not
have anything displayed on the page, just return a string with
***************
*** 235,239 ****
<table class="note" width="100%">
<tr valign=top>
! <td><strong>NOTE</strong></td>
<td width="100%"><p>If the filter creates a subdirectory with files, the filter
only needs to return the subdirectory in the return list. If
--- 235,239 ----
<table class="note" width="100%">
<tr valign=top>
! <td><strong>NOTE:</strong></td>
<td width="100%"><p>If the filter creates a subdirectory with files, the filter
only needs to return the subdirectory in the return list. If
***************
*** 380,384 ****
<p>Boolean if part has already been filtered. This field should
be set to a true value by filters that explicitly filters other entity parts.
! This tells MHonArc itself to not invoke a filter for the data.
</p>
</dd>
--- 380,384 ----
<p>Boolean if part has already been filtered. This field should
be set to a true value by filters that explicitly filters other entity parts.
! This tells MHonArc to not invoke a filter for the entity.
</p>
</dd>
***************
*** 423,427 ****
<table class="note" width="100%">
<tr valign=top>
! <td><strong>NOTE</strong></td>
<td width="100%"><p><strong>Do not include</strong>
<strong><CODE>$mhonarc::OUTDIR</CODE></strong> as part as the
--- 423,427 ----
<table class="note" width="100%">
<tr valign=top>
! <td><strong>NOTE:</strong></td>
<td width="100%"><p><strong>Do not include</strong>
<strong><CODE>$mhonarc::OUTDIR</CODE></strong> as part as the
***************
*** 468,472 ****
<table class="note" width="100%">
<tr valign=top>
! <td><strong>NOTE</strong></td>
<td width="100%"><p>The filters use a <a href="mimeargs.html">MIMEARGS</a>
argument style similiar to HTML attribute values. For example:
--- 468,472 ----
<table class="note" width="100%">
<tr valign=top>
! <td><strong>NOTE:</strong></td>
<td width="100%"><p>The filters use a <a href="mimeargs.html">MIMEARGS</a>
argument style similiar to HTML attribute values. For example:
***************
*** 622,626 ****
<table class="caution" width="100%">
<tr valign=top>
! <td><strong style="color: red;">CAUTION</strong></td>
<td width="100%"><p>
Use this option with caution
--- 622,626 ----
<table class="caution" width="100%">
<tr valign=top>
! <td><strong style="color: red;">CAUTION:</strong></td>
<td width="100%"><p>
Use this option with caution
***************
*** 638,642 ****
<table class="caution" width="100%">
<tr valign=top>
! <td><strong style="color: red;">CAUTION</strong></td>
<td width="100%"><p>
Use this option with caution since it can lead to
--- 638,642 ----
<table class="caution" width="100%">
<tr valign=top>
! <td><strong style="color: red;">CAUTION:</strong></td>
<td width="100%"><p>
Use this option with caution since it can lead to
***************
*** 1616,1629 ****
<table class="caution" width="100%">
<tr valign=top>
! <td><strong style="color: red;">CAUTION</strong></td>
! <td width="100%"><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>
</tr>
--- 1616,1634 ----
<table class="caution" width="100%">
<tr valign=top>
! <td><strong style="color: red;">CAUTION:</strong></td>
! <td width="100%"><p>For
! <a href="../faq/security.html#htmldata">security reasons</a>,
! it is highly recommended to disable
support of HTML messages in your mail archives. There is no
! guarantee this filter is robust enough to eliminate all possible
! exploits that can occur with HTML data.
! See the following <a href="../faq/faq.html">FAQ</a> questions for more
! information:
</p>
+ <ul>
+ <li><a href="../faq/security.html#htmldata">Why are HTML messages a security risk?</a></li>
+ <li><a href="../faq/security.html#htmlexchow">So how can I exclude HTML mail?</a></li>
+ </ul>
+ <p> </p>
</td>
</tr>
***************
*** 1632,1648 ****
<p>This filter is designed to process <tt>text/html</tt>, or
<tt>text/x-html</tt>, data.
! The filter modifies HTML documents so they can be
! included into the message pages without causing invalid markup
! to occur. The following modification are done to HTML documents when
processed by MHonArc:
</p>
<ul>
! <li><p>The HEAD element is removed. Since some elements within the HEAD
element may be relevant to the rest of the document, the following is
! done when removing the HEAD element:</p>
<ul>
<li>The title will be extracted and prepended
to the body data.</li>
! <li>Any BASE URL will be propogated to any relative URLs in the
document.</li>
</ul>
--- 1637,1651 ----
<p>This filter is designed to process <tt>text/html</tt>, or
<tt>text/x-html</tt>, data.
! The following modifications are done to HTML documents when
processed by MHonArc:
</p>
<ul>
! <li><p>The HEAD element is removed. Since some content within the HEAD
element may be relevant to the rest of the document, the following is
! done when the HEAD element is removed:</p>
<ul>
<li>The title will be extracted and prepended
to the body data.</li>
! <li>Any BASE URL will be propogated to relative URLs in the
document.</li>
</ul>
***************
*** 1686,1691 ****
<li><p><b><tt>cid:</tt></b> URLs are resolved, if possible. Therefore,
if image data related to the HTML document is included with the message,
! the URLs will be modified to the filenames of the images that were
! decoded.</p>
</li>
</ul>
--- 1689,1695 ----
<li><p><b><tt>cid:</tt></b> URLs are resolved, if possible. Therefore,
if image data related to the HTML document is included with the message,
! the URLs in the HTML will be modified to reference the decoded image
! data.
! </p>
</li>
</ul>
***************
*** 1699,1705 ****
<tr valign=top>
<td><strong><tt>allowcomments</tt></strong></td>
! <td><p>Preserve any comment declarations. Comment declarations
! are sometimes used to contain executable commands, like for
! server-side includes. Normally, comment declarations are munged
to protect against potential exploits, but this option will
disable that behavior.
--- 1703,1708 ----
<tr valign=top>
<td><strong><tt>allowcomments</tt></strong></td>
! <td><p>Preserve any comment declarations.
! By default, comment declarations are munged
to protect against potential exploits, but this option will
disable that behavior.
***************
*** 1707,1714 ****
<table class="caution" width="100%">
<tr valign=top>
! <td><strong style="color: red;">CAUTION</strong></td>
<td width="100%"><p>
Using this option can open up security vulnerabilies, including the
! potential accessing of server resources.
</p>
</td></tr></table>
--- 1710,1718 ----
<table class="caution" width="100%">
<tr valign=top>
! <td><strong style="color: red;">CAUTION:</strong></td>
<td width="100%"><p>
Using this option can open up security vulnerabilies, including the
! accessing of server resources. If you have server-side includes
! enabled for your site, you SHOULD NOT use this option.
</p>
</td></tr></table>
***************
*** 1718,1728 ****
<td><strong><tt>allownoncidurls</tt></strong></td>
<td><p>Preserve URL-based attributes that are not cid: URLs.
! Normally, any URL-based attribute -- <tt>href</tt>, <tt>src</tt>,
<tt>background</tt>, <tt>classid</tt>, <tt>data</tt>, <tt>longdesc</tt>
! -- will be stripped if it is not a cid: URL.
! This is to prevent
! malicious URLs that verify mail addresses for spam purposes, secretly
! set cookies, or gather some statistical data automatically with the
! use of elements that cause browsers to automatically fetch data:
<tt>IMG</tt>, <tt>BODY</tt>, <tt>IFRAME</tt>, <tt>FRAME</tt>,
<tt>OBJECT</tt>, <tt>SCRIPT</tt>, <tt>INPUT</tt>.
--- 1722,1733 ----
<td><strong><tt>allownoncidurls</tt></strong></td>
<td><p>Preserve URL-based attributes that are not cid: URLs.
! By default, any URL-based attribute -- <tt>href</tt>, <tt>src</tt>,
<tt>background</tt>, <tt>classid</tt>, <tt>data</tt>, <tt>longdesc</tt>
! -- will be stripped if it is not a cid URL.
! This prevents
! malicious URLs from verifying mail addresses, secretly
! setting cookies, or gathering statistical data with the
! use of elements that cause browsers to automatically fetch data without
! user interaction:
<tt>IMG</tt>, <tt>BODY</tt>, <tt>IFRAME</tt>, <tt>FRAME</tt>,
<tt>OBJECT</tt>, <tt>SCRIPT</tt>, <tt>INPUT</tt>.
***************
*** 1730,1734 ****
<table class="note" width="100%">
<tr valign=top>
! <td><strong>NOTE</strong></td>
<td width="100%"><p><tt>Href</tt> attributes for anchor, <tt><A></tt>,
elements are preserved, even if <tt>allownoncidurls</tt> is
--- 1735,1739 ----
<table class="note" width="100%">
<tr valign=top>
! <td><strong>NOTE:</strong></td>
<td width="100%"><p><tt>Href</tt> attributes for anchor, <tt><A></tt>,
elements are preserved, even if <tt>allownoncidurls</tt> is
***************
*** 1747,1754 ****
<table class="caution" width="100%">
<tr valign=top>
! <td><strong style="color: red;">CAUTION</strong></td>
<td width="100%"><p>
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>
--- 1752,1759 ----
<table class="caution" width="100%">
<tr valign=top>
! <td><strong style="color: red;">CAUTION:</strong></td>
<td width="100%"><p>
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>
***************
*** 1767,1771 ****
<table class="caution" width="100%">
<tr valign=top>
! <td><strong style="color: red;">CAUTION</strong></td>
<td width="100%"><p>
If <tt>attachcheck</tt> is specified, the HTML
--- 1772,1776 ----
<table class="caution" width="100%">
<tr valign=top>
! <td><strong style="color: red;">CAUTION:</strong></td>
<td width="100%"><p>
If <tt>attachcheck</tt> is specified, the HTML
***************
*** 1781,1786 ****
<tr valign=top>
<td><strong><tt>disablerelated</tt></strong></td>
! <td><p>Disable processing of related parts processing. I.e. Things
! like cid URLs will not be resolved.
</p></td>
</tr>
--- 1786,1791 ----
<tr valign=top>
<td><strong><tt>disablerelated</tt></strong></td>
! <td><p>Disable processing of related parts processing:
! cid URLs will not be resolved.
</p></td>
</tr>
***************
*** 1793,1799 ****
<td><strong><tt>notitle</tt></strong></td>
<td><p>Do not print extracted title at the beginning of converted
! output. Since this filter strips out HEAD markup so the document
! can be included into the message page, this filter will extract
! the title and print the title of the document before the document
body. The <tt>notitle</tt> argument disables this behavior.
</p></td>
--- 1798,1802 ----
<td><strong><tt>notitle</tt></strong></td>
<td><p>Do not print extracted title at the beginning of converted
! output. By default, the title is printed before the document
body. The <tt>notitle</tt> argument disables this behavior.
</p></td>
***************
*** 1852,1856 ****
<table class="note" width="100%">
<tr valign=top>
! <td><strong>NOTE</strong></td>
<td width="100%"><p>The <tt>asis</tt> option is deprecated.
It is recommended to use the
--- 1855,1859 ----
<table class="note" width="100%">
<tr valign=top>
! <td><strong>NOTE:</strong></td>
<td width="100%"><p>The <tt>asis</tt> option is deprecated.
It is recommended to use the
***************
*** 1877,1881 ****
<table class="note" width="100%">
<tr valign=top>
! <td><strong>NOTE</strong></td>
<td width="100%"><p>
The effects of <tt>fancyquote</tt> and
--- 1880,1884 ----
<table class="note" width="100%">
<tr valign=top>
! <td><strong>NOTE:</strong></td>
<td width="100%"><p>
The effects of <tt>fancyquote</tt> and
***************
*** 1896,1900 ****
<table class="note" width="100%">
<tr valign=top>
! <td><strong>NOTE</strong></td>
<td width="100%"><p>
If message text is denoted as flowed text by
--- 1899,1903 ----
<table class="note" width="100%">
<tr valign=top>
! <td><strong>NOTE:</strong></td>
<td width="100%"><p>
If message text is denoted as flowed text by
***************
*** 1938,1944 ****
<table class="note" width="100%">
<tr valign=top>
! <td><strong>NOTE</strong></td>
<td width="100%"><p>A line that contains no whitespace and is longer
! than <tt>maxwidth</tt>, will <strong>NOT</strong> be wrapped.
</p>
</td></tr></table>
--- 1941,1947 ----
<table class="note" width="100%">
<tr valign=top>
! <td><strong>NOTE:</strong></td>
<td width="100%"><p>A line that contains no whitespace and is longer
! than <tt>maxwidth</tt>, will not be wrapped.
</p>
</td></tr></table>
***************
*** 1962,1967 ****
<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>
--- 1965,1969 ----
<td><p>Italicize quoted message text. Any quoted lines in the message
will be wrapped in the HTML <tt>I</tt> element.
! Compare this option with the <tt>fancyquote</tt> option.
</p>
</tr>
***************
*** 1974,1980 ****
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>
--- 1976,1982 ----
generation of inline styles.
</p>
! <p>This option is useful if a master stylesheet controls the
appearance of archives. By using this option, the master stylesheet
! can be used to control the rendering of quoted text.
</p>
</tr>
***************
*** 1994,2002 ****
<td><strong><tt>usename</tt></strong></td>
<td><p>When decoding uuencoded data, use the full filename specified
! when write the data to disk instead of just the filename extension.
</p>
<table class="caution" width="100%">
<tr valign=top>
! <td><strong style="color: red;">CAUTION</strong></td>
<td width="100%"><p>
Use this option with caution
--- 1996,2004 ----
<td><strong><tt>usename</tt></strong></td>
<td><p>When decoding uuencoded data, use the full filename specified
! in the message instead of the filename extension.
</p>
<table class="caution" width="100%">
<tr valign=top>
! <td><strong style="color: red;">CAUTION:</strong></td>
<td width="100%"><p>
Use this option with caution
***************
*** 2011,2028 ****
<td><strong><tt>uudecode</tt></strong></td>
<td><p>Decode any embedded uuencoded data. Including uuencoded data
! within messages was a way to trasmit binary data
via email before MIME was developed. The inclusion of uuencoded
data is deprecated within email, but is still common in the
! USENET (binary) newsgroups. Note, specifying <b><tt>uudecode</tt></b>
adds extra
overhead in the processing of text messages, including messages without
any uuencoded data.
</p>
! <p>Uuencoded data is treated as <tt>application/octet-stream</tt>
! data for purposes of checking if the data should be excluded when
! checked against the <a href="mimeexcs.html">MIMEEXCS</a> resource.
! Therefore, if <tt>application/octet-stream</tt> data is listed
! in MIMEEXCS, uuencoded data will be excluded.
! </p></td>
</tr>
--- 2013,2038 ----
<td><strong><tt>uudecode</tt></strong></td>
<td><p>Decode any embedded uuencoded data. Including uuencoded data
! within messages was a way to transmit binary data
via email before MIME was developed. The inclusion of uuencoded
data is deprecated within email, but is still common in the
! USENET (binary) newsgroups.
! </p>
! <p>Uuencoded data is treated as <tt>application/octet-stream</tt>
! for data exclusion purposes: <a href="mimeexcs.html">MIMEEXCS</a>.
! If <tt>application/octet-stream</tt> data is listed
! in MIMEEXCS, uuencoded data will be excluded.
! </p>
! <table class="note" width="100%">
! <tr valign="baseline">
! <td><strong>NOTE:</strong></td>
! <td width="100%"><p>Specifying <b><tt>uudecode</tt></b>
adds extra
overhead in the processing of text messages, including messages without
any uuencoded data.
</p>
! </td>
! </tr>
! </table>
! </td>
</tr>
***************
*** 2062,2066 ****
<table class="note" width="100%">
<tr valign=top>
! <td><strong>NOTE</strong></td>
<td width="100%"><p>The sematics of using the
<a href="mimeexcs.html">MIMEEXCS</a> resource vs this filter are different.
--- 2072,2076 ----
<table class="note" width="100%">
<tr valign=top>
! <td><strong>NOTE:</strong></td>
<td width="100%"><p>The sematics of using the
<a href="mimeexcs.html">MIMEEXCS</a> resource vs this filter are different.
***************
*** 2071,2078 ****
<tt>multipart/alternative</tt> entity.
</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>
--- 2081,2084 ----
***************
*** 2085,2089 ****
<table class="note" width="100%">
<tr valign=top>
! <td><strong>NOTE</strong></td>
<td width="100%"><p>It is important to have an explicit entry for
<b><tt>application/octet-stream</tt></b> for handling unknown
--- 2091,2095 ----
<table class="note" width="100%">
<tr valign=top>
! <td><strong>NOTE:</strong></td>
<td width="100%"><p>It is important to have an explicit entry for
<b><tt>application/octet-stream</tt></b> for handling unknown
***************
*** 2172,2175 ****
--- 2178,2182 ----
<p>
<a href="charsetconverters.html">CHARSETCONVERTERS</a>,
+ <a href="mimealtprefs.html">MIMEALTPREFS</a>,
<a href="mimeargs.html">MIMEARGS</a>,
<a href="mimedecoders.html">MIMEDECODERS</a>,
***************
*** 2189,2193 ****
<img align="top" src="../monicon.png" alt="">
<a href="http://www.mhonarc.org";><strong>MHonArc</strong></a><br>
! Copyright © 1997-2003 <a href="http://www.mhonarc.org/~ehood/";>Earl Hood</a>, <a href="mailto:mhonarc%40mhonarc.org";>mhonarc<!--
-->@<!--
-->mhonarc.org</a><br>
--- 2196,2200 ----
<img align="top" src="../monicon.png" alt="">
<a href="http://www.mhonarc.org";><strong>MHonArc</strong></a><br>
! Copyright © 1997-2005 <a href="http://www.mhonarc.org/~ehood/";>Earl Hood</a>, <a href="mailto:mhonarc%40mhonarc.org";>mhonarc<!--
-->@<!--
-->mhonarc.org</a><br>
Index: perlinc.html
===================================================================
RCS file: /home/users/mhonarc.org/ehood/cvs/mhonarc/mhonarc/MHonArc/doc/resources/perlinc.html,v
retrieving revision 1.13
retrieving revision 1.14
diff -C2 -r1.13 -r1.14
*** perlinc.html 6 Oct 2003 22:04:19 -0000 1.13
--- perlinc.html 13 May 2005 18:50:39 -0000 1.14
***************
*** 79,85 ****
</p>
! <dl>
! <dt><strong>NOTE</strong></dt>
! <dd><p>During the installation of <em>MHonArc</em>, the
<em>MHonArc</em> library location gets prepended to
<code><strong><!--
--- 79,86 ----
</p>
! <table class="note" width="100%">
! <tr valign="baseline">
! <td><strong>NOTE:</strong></td>
! <td width="100%"><p>During the installation of <em>MHonArc</em>, the
<em>MHonArc</em> library location gets prepended to
<code><strong><!--
***************
*** 87,92 ****
-->INC</strong></code>.
</p>
! </dd>
! </dl>
<!-- *************************************************************** -->
--- 88,94 ----
-->INC</strong></code>.
</p>
! </td>
! </tr>
! </table>
<!-- *************************************************************** -->
***************
*** 114,118 ****
</p>
! <pre>
<b><PerlINC></b>
/usr/local/lib/MHonArc/filters
--- 116,120 ----
</p>
! <pre class="code">
<b><PerlINC></b>
/usr/local/lib/MHonArc/filters
Index: textencode.html
===================================================================
RCS file: /home/users/mhonarc.org/ehood/cvs/mhonarc/mhonarc/MHonArc/doc/resources/textencode.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -r1.3 -r1.4
*** textencode.html 15 Mar 2004 21:07:18 -0000 1.3
--- textencode.html 13 May 2005 18:50:39 -0000 1.4
***************
*** 65,70 ****
<p>TEXTENCODE allows you to specify a destination character encoding
! for all message text data. For each message read to be
! archived, text data, including message header fields and text body parts,
is translated from the charset(s) used in the message
to the charset specified by the TEXTENCODE resource.
--- 65,70 ----
<p>TEXTENCODE allows you to specify a destination character encoding
! for all message text data. For each message read, textual data,
! -- including message header fields and text body parts --
is translated from the charset(s) used in the message
to the charset specified by the TEXTENCODE resource.
***************
*** 89,93 ****
<td width="100%"><p>The terms <em>character set (charset)</em> and
<em>character encoding</em> are used interchangeably within MHonArc
! documentation. The reasoning is that <em>charset</em> is used within
the MIME RFCs, but it blurs the concepts of <em>character encoding</em>
and <em>coded characer set</em> and probably a few other things.
--- 89,93 ----
<td width="100%"><p>The terms <em>character set (charset)</em> and
<em>character encoding</em> are used interchangeably within MHonArc
! documentation. The reasoning is <em>charset</em> is used within
the MIME RFCs, but it blurs the concepts of <em>character encoding</em>
and <em>coded characer set</em> and probably a few other things.
***************
*** 119,123 ****
<a href="charsetaliases.html">CHARSETALIASES</a> for character sets
MHonArc is aware of. The official list of registered character
! sets for use on the Interenet is available from
<a href="http://www.iana.org/assignments/character-sets";>IANA</a>.
</P>
--- 119,123 ----
<a href="charsetaliases.html">CHARSETALIASES</a> for character sets
MHonArc is aware of. The official list of registered character
! sets for use on the Internet is available from
<a href="http://www.iana.org/assignments/character-sets";>IANA</a>.
</P>
***************
*** 334,338 ****
</p>
<li><p><em>fallback</em>: If none of the above are present, then
! the fallback implementation is used. Fallback code is written
pure Perl, so it may not be as efficient as the modules
listed above. However, many popular character encodings are
--- 334,338 ----
</p>
<li><p><em>fallback</em>: If none of the above are present, then
! the fallback implementation is used. Fallback code is written in
pure Perl, so it may not be as efficient as the modules
listed above. However, many popular character encodings are
***************
*** 439,445 ****
</pre>
<p>For more information about using MHonArc in a Japanese locale,
! see (documents in Japanese):<br>
! <a href="http://www.shiratori.riec.tohoku.ac.jp/~p-katoh/Hack/Docs/mhonarc-jp/index.html";><http://www.shiratori.riec.tohoku.ac.jp/~p-katoh/Hack/Docs/mhonarc-jp/index.html></a><br>
! <a href="http://www.shiratori.riec.tohoku.ac.jp/~p-katoh/Hack/Docs/mhonarc-jp/mhonarc-jp-2_4.html";><http://www.shiratori.riec.tohoku.ac.jp/~p-katoh/Hack/Docs/mhonarc-jp/mhonarc-jp-2_4.html></a>
</p>
</td>
--- 439,444 ----
</pre>
<p>For more information about using MHonArc in a Japanese locale,
! see (documents in Japanese):
! <a href="http://www.mhonarc.jp/";><http://www.mhonarc.jp/></a>.
</p>
</td>
---------------------------------------------------------------------
To sign-off this list, send email to majordomo(_at_)mhonarc(_dot_)org with the
message text UNSUBSCRIBE MHONARC-COMMITS