[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference abbott::macintosh_office

Title:	Macintosh Office
Notice:	V2.5 of Mail Available, see note 30.48
Moderator:	ORION::chayna.zko.dec.com::tamara::eppes

Created:	Thu Jun 20 1991
Last Modified:	Wed Jun 04 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	700
Total number of notes:	2612

689.0. "translation_table questions" by GIDDAY::BACOT () Tue Mar 11 1997 02:37

    
    Could someone please explain how the translation_table file
    can be used to translate differently for incoming and outgoing
    documents of the same type?
    
    My customer would like all outbound attachments (from TeamLinks) to 
    end up as Macbinary, but for inbound PC attachments an appropriate
    mapping could be done and a minimal resource forck created for the file
    based on the attachment name.
    
    Is this possible?
    
    thanks, 
    
    angela

T.R	Title	User	Personal Name	Date	Lines
689.1	RE: 689.0	TAMARA::TAMARA::CLARK	Lee Clark,DTN:381-0422,TeamLinks	`Tue Mar 11 1997 11:46`	10
	TeamLinks Mail for Mac doesn't use attachment names (or .EXT) to determine file / application mappings. That seems to indicate that what the customer wants to do is not supported. Maybe another alternative might come up if you can provide a description of what the customer wants to do (as opposed to what the customer wants Mail to do). Your description makes it seem like the Mac users will be sending mail only to other Mac users (outbound MacBinary can only be read by Mac clients), but will be receiving mail from PC users.
689.2	problem statement	GIDDAY::BACOT		`Tue Mar 11 1997 19:45`	69
	I apologise as I am not as familiar with TeamLinks for Mac as I would like to be... The problem is with sending and receiving attachments in TeamLinks for Mac, our customer is trying to send and receive attachments to both TeamLinks for Mac users and PC users properly tagged. TeamLinks V2.5 for Macintosh MailWorks Server V1.3A MessageRouter V3.3 PMDF V5 QuickMail SMTP When sending mail from TeamLinks for Mac via MessageRouter to PMDF and then to another TeamLinks for Mac user (in a different organisation) the attachments were not coming through with resource fork intact. Somewhere along the way it was being stripped off. We tried changing BINARY to MACBINARY in the translation table, which resulted in forcing TeamLinks for Mac to send the full Mac file, but the end user got attachments which were labelled as per the MR tag instead of being AppleDouble. If the attachment was saved and decoded a Mac file resulted. If an entry can't be found in the translation table, MACBINARY is used, so we deleted all entries so that attachments to TeamLinks messages were being left as MACBINARY and reaching QuickMail intact. (QuickMail is the point just before the other organisation picks it up). and these attachments, when autoforwarded back from QuickMail, come back as MACBINARY but TeamLinks no longer identifies the file type or displays an icon, therefore the attachment cannot be launched from within TeamLinks. If the file is saved, the file type and creator information held in the MACBINARY format is extracted and a "double clickable" file is produced. So, at this stage we are using 'default tagging and encoding' in the translation table (MACBINARY) and hence PMDF-MR(CONVERT_MACBINARY=2) can do the conversion to APPLEDOUBLE. This fixes exchange of attachments with Mac users but causes problems with inbound PC files. Thus the perceived need for inbound and outbound translation table entries. We are also working with Innosoft on the PMDF side. Thanks, Angela CSC - Sydney example: \|\|Microsoft Word for Macintosh \|MAC\|WINWORD6\|BINARY\|W6BN\|MSWD\| also maps the MR tag WINWORD6 back to the appropriate Word 6 file type and creator. So if I "nuke" most of the contents of Translation_Table.txt to force TeamLinks for Mac to send out both the resource fork and the data fork, do I lose the capability to map PC files back to Mac apps?