From e736d93eab79d7bcda3f47df7ab41c7b413e2a26 Mon Sep 17 00:00:00 2001 From: Barry Warsaw Date: Fri, 19 Oct 2001 04:34:42 +0000 Subject: 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 --- Doc/lib/emailmessage.tex | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/Doc/lib/emailmessage.tex b/Doc/lib/emailmessage.tex index ea2d0df..fbf30cf 100644 --- a/Doc/lib/emailmessage.tex +++ b/Doc/lib/emailmessage.tex @@ -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} attribute, except that it contains text that appears between the last 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} -- cgit v0.12