TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: Cross-platform files and e-mail From:Arlen -dot- P -dot- Walker -at- JCI -dot- COM Date:Thu, 23 Jan 1997 11:54:00 -0600
We need contractors creating files on Macs to be able to send Mac
files as e-mail attachments to our PCs (which are the only computers
that have e-mail access) where we can download them to diskette
and then use them on our Macs. This isn't working for some reason,
and some people think it's impossible. Is it? If you're doing this
successfully, can you give me any tips (encoding, etc.)?
"Some people" also think the world is a disc balanced on the backs of
turtles. Both groups have about the same chance of being correct. ;{>}
It's not only possible, it's being done thousands of times every single day.
This is probably not germane to the list, so we should take the
troubleshooting process off-list. But I need to know what kind of files are
involved (Word, Pagemaker, whatever) what kind of mail system is being used
by the PCs, and what system software version (7.0, 6.0.8, 7.5.5, 7.6, etc.)
you're using on the Macs you want to read the files.
There's a generic way which will work, but it may be more than you require
and by giving me the requested information I may be able to simplify the
process further.
Here's the generic way. It requires both Mac groups have Stuffit (not an
onerous requirement). Have the contractor BinHex the file before attaching
and sending. (With Stuffit Lite 3.5, you'll find the BinHex->Encode command
under the "Translate" menu.) Then, when you get the file to the destination
Mac, use Stuffit again to decode the BinHex encoded file.
My guess would be either you're losing part of the file (such as the
resource fork) when handling it on a PC, or you're losing the file type and
creator code information when bringing it back onto the Mac. BinHex encoding
will help preserve both while in transit.
Computers are like children; they're at their best when they play nice with
each other.
Have fun,
Arlen
Chief Managing Director In Charge, Department of Redundancy Department
DNRC 224
Arlen -dot- P -dot- Walker -at- JCI -dot- Com
----------------------------------------------
In God we trust; all others must provide data.
----------------------------------------------
Opinions expressed are mine and mine alone.
If JCI had an opinion on this, they'd hire someone else to deliver it.
TECHWR-L (Technical Communication) List Information: To send a message
to 2500+ readers, e-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send commands
to LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU (e.g. HELP or SIGNOFF TECHWR-L).
Search the archives at http://www.documentation.com/ or search and
browse the archives at http://listserv.okstate.edu/archives/techwr-l.html