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.
As you probably know, if you use anything more than ascii text in
an email message, you must attach it as a file in an encoded format.
The person at the other end must unencode it in order to read it.
While I'm not so sure -html is a good option, I am sure that
an .RTF (Rich Text Format) file would hold most of typographic
format which you are wanting to maintain. In my experience,
.RTF files will open nicely in Quark, Word, Pagemaker and the
like. Framemaker doesn't like them much, however.
Sara
__________________________
I submit articles via email for subsequent publication using Quark,
FrameMaker, etc. I submit these in plain text for the follwoing reasons:
* I sometimes don't know the target application.
* I sometimes don't have the target application.
* Not everyone I send to can receive binary attachments reliably.
Nonetheless, I'd like to be able to indicate bold, italics, hanging indents,
bullets, em- and en-dashes, and other typographic niceties.
Does anyone know of a convention for this, preferably with filters for the
major publishing packages? Is HTML a good solution? ...RM
Sara Jane Mutton
Technical Writer
Techsmith Corporation
3001 Coolidge Road, Suite 400
East Lansing, MI 48823 USA
s -dot- mutton -at- techsmith -dot- com http://www.TechSmith.com/
Voicemail: (517) 333-2100x168
FAX : (517) 333-1888