Commit e736d93e authored by Barry Warsaw's avatar Barry Warsaw

Added a note about the somewhat kludgey behavior of the message

epilogue, based on the discussion in this SF bug report:

https://sourceforge.net/tracker/index.php?func=detail&aid=472481&group_id=25568&atid=384678
parent 1f0fa92b
...@@ -390,4 +390,14 @@ Note that if the message object has no preamble, the ...@@ -390,4 +390,14 @@ Note that if the message object has no preamble, the
The \var{epilogue} attribute acts the same way as the \var{preamble} The \var{epilogue} attribute acts the same way as the \var{preamble}
attribute, except that it contains text that appears between the last attribute, except that it contains text that appears between the last
boundary and the end of the message. boundary and the end of the message.
One note: when generating the flat text for a \mimetype{multipart}
message that has no \var{epilogue} (using the standard
\class{Generator} class), no newline is added after the closing
boundary line. If the message object has an \var{epilogue} and its
value does not start with a newline, a newline is printed after the
closing boundary. This seems a little clumsy, but it makes the most
practical sense. The upshot is that if you want to ensure that a
newline get printed after your closing \mimetype{multipart} boundary,
set the \var{epilogue} to the empty string.
\end{datadesc} \end{datadesc}
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment