| > I guess my question is...
>
> * Why doesn't the mail subsystem of ALL-IN-1 us the
> WPS+ formatter to read documents?
For performance reasons mail messages are not fully formatted in a Read
operation. Instead they are read through the Compound Document text
dataset which allows the message and all it's attachments to be viewed as
whole, that is, you can move forwards and backwards across attachments.
When you print a mail message it and each attachment is indvidually fully
formatted according it's handling and/or data type. Not all attachments
will be WPS-PLUS so it would not be correct to always use the WPS-PLUS
formatter. Some attachments may already be formatted (for example,
PostScript) and should not be formatted at all.
The decision on whether to fully format during a Read is not determined by
the sub-system (EM or WP) but is determined by the document type (MAIL or
DOCUMENT). MAIL messages are not fully formatted and DOCUMENTS are fully
formatted.
If you want to Read a message with full formatting do a Print to TERMINAL,
which will indvidually format the message and each attachment.
Richard
|
| Hello,
Thanks for the quick reply!!
Can you (or anyone else) think of a reason why it would be
more difficult to use a template when creating a document
from EM C then from WP C??
It sounds like perhaps all the customer really needs to do
is create the message as an attachment and then the header
and footers will be correctly displayed?
Lastly, does anyone have any info/examples of how to use
the document classification information now stored in 3.0?
Thanks!
Peter
|
| As Richard says in .1, Read from the Mail menu uses a mechanism to
display the message which doesn't do full formatting. It would be quite
easy to customise this so that it did do full formatting (i.e. the same
as Print to Terminal does), but it would be a bit slower, and you
wouldn't be able to use <prev screen> to go up past the top of the
attachment you were currently reading (I think).
As to your question about the new (v3.0) security attributes. The main
problem with these, and the main reason why they weren't used in v3.0
(in the User Interface) is that they aren't carried across the network
by Message Router. In future versions of MR (conforming to X.400/88)
there are/may be message elements which could be used to carry security
attributes, so this might change. Meanwhile, there's no way to carry
them, except by such "hacks" as putting them on the end of the Subject
field, or (as some installations have done) encoding them as text into
an extra bodypart which is attached to the end of the message.
Dave.
|