Word to FrameMaker
Please read all these notes before attempting this task.

Introduction
The process is a fairly involved one. In summary you should:
1)	Convert the Microsoft Word format file(s) to Microsoft Interchange format (also called RTF format).
2) 	Convert the RTF format file(s) to DCA format.
3)	Transfer the DCA format file(s) from the Macintosh to the  Sun. 
4)	Read the DCA file(s) into FrameMaker.
Full details are given below.

Before you start
Merging files 
You may wish to merge several Word files together before you convert and send them. The conversion from RTF format to DCA format seems quite touchy about how this is done. If you open the first file, and then read in the subsequent files, the DCA Conversion program may crash. The safest way to merge files is to paste them all into a new file:
1)	Open the Applications folder
2)	Double click on Microsoft Word
3)	Select New from the File menu.

Then, for each file to be merged, starting with the first one:
1)	Select Open from the File menu
2)	Select the file to be merged
3)	Select some text from the start of the file by dragging the mouse over it
4)	Scroll to the end of the file
5)	Select all the text by holding down the Shift key, and dragging the mouse over the end of the file
6)	Select Copy from the Edit menu, to read the file into the Clipboard
7)	Click the Close icon
8)	Select Paste from the Edit menu, to paste the file into the new file.
When you have pasted in all the files:
1)	Select Save As from the File menu
2)	Type in the name you want to use to save the merged files, pressing Return.
When you have merged all the groups of files you wish to, quit Word.

Create a working folder
Before you start, create an empty folder in the root directory of the Macintosh, and name it DCA Folder. Move all the files that are to be converted into this folder, or copy them if you wish to preserve the Word format files on hard disc. 
WARNING: The conversion as described will overwrite the Word format files. Please ensure that they are backed up to floppy (as they should be anyway!). 

Space requirements
This method is the quickest one I have found, as each of the applications you use is only loaded once. It assumes there is considerable free space on the hard disc - about three to four times the size of the folder to be converted. If you cannot make this much free space you will have to convert and transfer your files a few at a time, which will mean you have to load the applications several times over. 
The disc must have free space at least four times the size of the largest file to transfer (not allowing for any system overheads).

Converting from Word to RTF
Load Microsoft Word, which should be in the Applications folder. Then, for each file to be converted: 
1)	Open the file
2)	Select Save As from the File menu
3)	Click the File Format button
4)	Double click Interchange Format (RTF)
5)	Click the Save button
6)	Click the Yes button to overwrite the old file
7)	Close the file.
The RTF file will be about 1.5 times the size of the Word file.
When you have converted all the files, quit Word.

Converting from RTF to DCA
Load DCA Conversion, which should be in the Applications folder. Then, for each file to be converted:
1)	Select Convert from the File menu
2)	Double click the file to convert
3)	Click the Save button.
The DCA file will be about the size of the original Word file.
When you have converted all the files, quit DCA Conversion.
WARNING: Do not try to overwrite the RTF file with the DCA file as this will cause an I/O error and both files will be lost.

Freeing disc space
The DCA files will have the suffix '.RFT'. The RTF files can now be deleted: hold the Shift key down, select all files without the '.RFT' suffix, and drag them to the Trashcan. Select Empty Trash from the Special menu to free the disc space.

Moving files from the Mac to the Sun
Setting up the Sun
1)	Use the 'cd' command to put the Sun in the destination directory.
2)	Load Kermit by typing '/usr/local/mackermit'
3)	Make the Sun ready to receive files by typing 'server'
Setting up the Mac
1)	Load Kermit by double clicking on the file 'Kermit for binary transfer' in the Kermit folder, which is held in the Utilities folder.
Transferring the files
For each file to be sent:
1)	Select Send File from the File menu.
2)	Change the destination filename. Your name should consist of no more than 10 lower case letters and/or numerals, with the suffix '.dca'. 
	Example: manual.dca 
3)	Press the Return key to send the file, or click the Save button.
Finishing with the Mac
1)	Stop the Sun from waiting to be sent files by selecting Finish from the Remote menu.
2)	Select Quit from the File menu
Finishing with the Sun
1)	Type 'quit' at the Kermit command line.
The files will now be on the Sun in your current directory.

Reading the file into FrameMaker
The file can be read into FrameMaker in the normal way. When you are asked for the filename, include the '.dca' extension. FrameMaker will then recognise the file as one in DCA format, and use the filter automatically.

Shortcomings
The conversion to DCA format strips out a lot of information:
Graphics
All graphics are lost. 
Fonts
Many fonts are merged together. Their default mapping is as follows: 
Word 	FrameMaker
fonts	font 
9pt Avant Garde, Chicago, Geneva and Helveticas	9pt Helvetica
9pt Bookman, New Century, Palatino, Times and Zapf Chancery 	9pt Times
9pt Courier, Goudy, Monaco, Symbol and Zapf Dingbat 	10pt Courier
10pt Avant Garde, Chicago, Geneva and Helveticas	10pt Helvetica
10pt Bookman, New Century, Palatino, Times and Zapf Chancery 	10pt Times
10pt Courier, Goudy, Monaco, Symbol and Zapf Dingbat 	10pt Courier
12pt Avant Garde, Chicago, Geneva and Helveticas	12pt Helvetica
12pt Bookman, New Century, Palatino, Times and Zapf Chancery	12pt Times
12pt Courier, Goudy, Monaco, Symbol and Zapf Dingbat 	12pt Courier
14pt any font 	14pt Times
18pt any font 	18pt Times
24pt any font 	24pt Times
The mapping of all other fonts and/or point sizes is undefined.
This can be altered if necessary: see the Technical Appendix.
Characters
Many characters are altered by the conversion process:
	Mac	Obtained by	FrameMaker
	character		character
	`	` (grave)	‘
	'	' (singlequote)	’
	™	Option-2	_
	∞	Option-5	B
	•	Option-8	"
	∂	Option-d	_
	©	Option-g	+
	˙	Option-h	_
	∆	Option-j	_
	˚	Option-k	_
	π	Option-p	f
	œ	Option-q	oe
	†	Option-t	*
	√	Option-v	_
	∑	Option-w	S
	≈	Option-x	Z
	Ω	Option-z	L
	–	Option-- (endash)	- (hyphen)
	≠	Option-=	_
	“	Option-[	"
	‘	Option-] (leftquote)	’
	…	Option-;	.
	≤	Option-,	&
	≥	Option-.	/
	÷	Option-/	:
	‚	Shift-Option-0	_
	⁄	Shift-Option-1	_
	€	Shift-Option-2	_
	‹	Shift-Option-3	_
	›	Shift-Option-4	_
	ﬁ	Shift-Option-5	_
	ﬂ	Shift-Option-6	_
	‡	Shift-Option-7	_
	·	Shift-Option-9	_
	ı	Shift-Option-b	_
	Î	Shift-Option-d	_
	‰	Shift-Option-e	_
	Ï	Shift-Option-f	_
	Ì	Shift-Option-g	_
	Ó	Shift-Option-h	_
	È	Shift-Option-i	_
	Ô	Shift-Option-j	_
		Shift-Option-k	_
	Ò	Shift-Option-l	_
	˜	Shift-Option-m	_
	ˆ	Shift-Option-n	_
	∏	Shift-Option-p	_
	Œ	Shift-Option-q	OE
	Â	Shift-Option-r	_
	Í	Shift-Option-s	_
	Ê	Shift-Option-t	_
	Ë	Shift-Option-u	_
	◊	Shift-Option-v	*
	„	Shift-Option-w	_
	Ù	Shift-Option-x	_
	Á	Shift-Option-y	_
	Û	Shift-Option-z	_
	Ÿ	Shift-Option-`	_
	±	Shift-Option-=	B
	”	Shift-Option-[	"
	Ú	Shift-Option-;	_
	¯	Shift-Option-,	_
	˘	Shift-Option-.	_
These characters are incorrectly represented because they acquire the same character codes as other more frequently used characters. I have tried to pick the best compromises: it is clearly preferable that Ω should come out as L rather than vice-versa, for instance. These mappings can be changed if necessary: see the Technical Appendix.
One thing you should note is the handling of quotes. If you know you are going to have to transfer a file, use ` (grave) as an open quote, and ' (singlequote) as a close quote on the Mac. These will then become ‘ and ’ (left and right quotes) - probably what is desired.
Treat any underscore in a FrameMaker document with especial suspicion.
Special symbols
Fonts producing special symbols on the Mac (Symbol, Zapf Dingbat) are treated as ordinary fonts by the conversion, and produce the same characters as ordinary fonts. This is because I haven't been bothered to write the 500 lines of configuration file this would need.
Styles
Styles appear to be carried across fairly accurately; these may help you out of some of the problems you would otherwise meet.
Some styles may be split into several different ones, in which case I understand that they can then be merged back together using Frame. 
Spacing
Spaces before and after paragraphs are lost. If possible, use styles to set them up again.
Highlighting
Highlighting (ie bold print, italics) gets well and truly messed up. I don't know why or how!

Technical Appendix
Introduction
The section above listed some of the shortcomings of the conversion. This appendix contains information to help you tackle these problems:
•	the incorrect mapping of characters
•	the incorrect mapping of fonts.
Styles
Remember that styles are in general successfully carried across, and this may be sufficient to correct the font mapping. It is probably worth experimenting with one file. However, this will not work where different fonts occur within the same style - for instance some Courier text (as typed in by a user) within a block of Goudy. 
If you have not used styles then things are not so good. It is possible that 'styles' are assigned to text on the basis of what the conversion thinks looks similar, but I have not had a chance to look into this. This is left as an exercise for the reader(!) 

The file ‘dca.am’
When a DCA file is read into FrameMaker it is recognised as such because of its ‘.dca’ suffix. The ‘dcatomif’ conversion program is run. This uses the file $FMHOME/.makerinit/dca.am to specify how the DCA fonts and characters are mapped to FrameMaker fonts and characters. There are various files in the directory with names starting ‘dca.am.’:
dca.am		a link to the actual file being used
dca.am.issue	the version supplied - full of extra bugs
dca.am.mac	the standard default
dca.am.<name>	other versions set up for specific jobs

This annotated excerpt from dca.am.mac should show how the file specifies the mappings:
<Comment Please do not alter this default file. Work on a copy!>

GFID 26 is a magic number used to define all character mappings

<SrcChar
    <GFID 26>	
>
<MakerChar
    <FFamily Times> <FSize 12> <FPlain yes>
> 

<SrcChar <Code 0x40>> <MakerChar <Code ' '>>
<SrcChar <Code 0x42>> <MakerChar <Code 0x89>> <Comment a circumflex>

There are lots of these definitions showing which DCA character codes are mapped onto which FrameMaker character codes; for example DCA character 42hex is mapped to FrameMaker character 89hex by the above line.
<SrcChar <Code 0xfe>> <MakerChar <Code 0xf2>> <Comment U acute> 
<SrcChar <Code 0xff>> <MakerChar <Code '1'>> <Comment Eight Ones--TODO> 

Once all the character mapping has been defined, there then follow a series of blocks defining which FrameMaker font each GFID number represents:

<SrcChar
    <GFID 158>
>
    <PreChar <FSize 12>>
    <PostChar <FSize 10>>
<CopyFont
    <GFID 26>
>

The above block says that GFID 158 is the same as GFID 26, except that the font size of 12pt is changed to 10pt

<SrcChar
    <GFID 87> 
>
    <PreChar <FFamily Times>>
    <PostChar <FFamily Helvetica>>
<CopyFont
    <GFID 158> 
>

The above block says that GFID 87 is the same as GFID 158 except that it is in Helvetica rather than Times. Note that GFID 158 (defined above) was itself defined in terms of GFID 26 - such constructs are allowed. 

Font mapping
How it doesn't work
The RTF file produced by Microsoft Word is a text file. Fonts and point sizes are embedded within the text, and are represented as follows:
	\f<RTF font no>\fs<point size x 2>
 except for 12 pitch, which just has:
	\f<RTF font no>
The RTF font numbers are as follows:
Avant Garde	33
Bookman	14
Chicago	0
Courier	22
Geneva	3
Goudy	189
Helvetica	21
Helvetica Narrow	15
Monaco	4
New Century Schoolbook	34
Palatino	16
Symbol	23
Times	20
Zapf Chancery	18
Zapf Dingbat	13
So Courier 9pt would be represented in RTF as \f22\fs18

When the RTF file is converted to DCA format the font and point size are then changed to a single number, or GFID (Graphic Font ID): 
Word font	GFID
12pt Bookman	2
12pt Zapf Chancery	8
12pt Courier, Goudy, Monaco, Symbol and Zapf Dingbat 	11
12pt New Century and Palatino	12
12pt Avant Garde, Chicago, Geneva and Helveticas	13
12pt Times	15
10pt Zapf Chancery	80
10pt Courier, Goudy, Monaco, Symbol and Zapf Dingbat	85
10pt New Century and Palatino	86
10pt Avant Garde, Chicago, Geneva and Helveticas	87
10pt Bookman and Times 	158
9pt Bookman, New Century, Palatino and Times 	221
9pt Avant Garde, Chicago, Geneva and Helveticas	222
9pt Courier, Goudy, Monaco, Symbol and Zapf Dingbat 	223
9pt Zapf Chancery	225
24pt any font 	245
14pt any font 	264
18pt any font 	266
Thus Courier 9pt would have a GFID of 223.
It is this stage of the conversion that causes problems, as many Word fonts are mapped to each GFID.
When the files are read into FrameMaker the GFIDs are then converted to FrameMaker fonts using the configuration file 'dca.am' (see above).

How to make it work
There are two points in the above stages where the default mapping described earlier can be altered. Firstly, in the RTF file the fonts are represented by text strings, and so can easily be changed using global edits of the file. Secondly, the mapping of GFIDs to FrameMaker fonts can be altered by editing the configuration file 'dca.am'. 

Example
Suppose a file had both 10pt Courier and 10pt Goudy in it. 
When the file is converted to RTF, these fonts are represented as \f22\fs20 and \f189\fs20 respectively. They are still differentiated.
When this is then converted to DCA both fonts become GFID no 85, and merge.
This could be avoided by a global exchange on the RTF file, changing the Goudy to an unused font (say Palatino 10pt). All occurrences of \f189\fs20 (ie Goudy 10pt) are changed to \f16\fs20 (ie Palatino 10pt).
Now when the DCA conversion occurs, the Courier is still converted to GFID no 85, but the Goudy has been changed to Palatino, and so is converted to GFID no 86. The fonts have maintained a separate identity.
All that is needed then is to change the Sun file dca.am to map GFID 86 back to Goudy 10pt.

Character mapping
How it doesn't work
This is the full character set for the Apple Macintosh in Times font. It is laid out as follows:
Numerals
Shift-Numerals
Option-Numerals
Shift-Option-Numerals
Letters (2lines)
Shift-Letters (2lines)
Option-Letters (2lines)
Shift-Option-Letters (2lines)
Punctuation
Shift-Punctuation
Option-Punctuation
Shift-Option-Punctuation

0	1	2	3	4	5	6	7	8	9
)	!	@	#	$	%	^	&	*	(
º	¡	™	£	¢	∞	§	¶	•	ª
‚	⁄	€	‹	›	ﬁ	ﬂ	‡	°	·

a	b	c	d	e	f	g	h	i	j	k	l	m
n	o	p	q	r	s	t	u	v	w	x	y	z
A	B	C	D	E	F	G	H	I	J	K	L	M
N	O	P	Q	R	S	T	U	V	W	X	Y	Z
å	∫	ç	∂	´	ƒ	©	˙	^	∆	˚	¬	µ
~	ø	π	œ	®	ß	†	¨	√	∑	≈	¥	Ω
Å	ı	Ç	Î	‰	Ï	Ì	Ó	È	Ô		Ò	˜
ˆ	Ø	∏	Œ	Â	Í	Ê	Ë	◊	„	Ù	Á	Û

`	-	=	[	]	;	'	,	.	/	\
~	_	+	{	}	:	"	<	>	?	|
`	–	≠	“	‘	…	æ	≤	≥	÷	«
Ÿ	—	±	”	’	Ú	Æ	¯	˘	¿	»

The character codes these keys generate are as follows:

30	31	32	33	34	35	36	37	38	39
29	21	40	23	24	25	5e	26	2a	28
bc	c1	aa	a3	a2	b0	a4	a6	a5	bb
e2	da	db	dc	dd	de	df	e0	a1	e1

61	62	63	64	65	66	67	68	69	6a	6b	6c	6d
6e	6f	70	71	72	73	74	75	76	77	78	79	7a
41	42	43	44	45	46	47	48	49	4a	4b	4c	4d
4e	4f	50	51	52	53	54	55	56	57	58	59	5a
8c	ba	8d	b6	ab	c4	a9	fa	5e	c6	fb	c2	b5
7e	bf	b9	cf	a8	a7	a0	ac	c3	b7	c5	b4	bd
81	f5	82	eb	e4	ec	ed	ee	e9	ef	f0	f1	f7
f6	af	b8	ce	e5	ea	e6	e8	d7	e3	f4	e7	f3

60	2d	3d	5b	5d	3b	27	2c	2e	2f	5c
7e	5f	2b	7b	7d	3a	22	3c	3e	3f	7c
60	d0	ad	d2	d4	c9	be	b2	b3	d6	c7
d9	d1	b1	d3	d5	f2	ae	f8	f9	c0	c8

Within an RTF file, characters are represented as follows:
•	the three characters  {\}  are all preceded by the character  \  - so a single backslash in the text becomes a double backslash in the RTF file
•	all other printable characters from 00 hex to 7f hex are represented by the actual character
•	all characters from 80 hex upwards are represented as \'<hex number> ;  for example, © would be \'a9 .
The last of these can be successfully used to represent any character, although Word does not do so.

When the RTF file is converted to a DCA file, the characters codes are changed. This table has the most significant nibble (msn) of the Mac code in the left column, and the least signicant nibble in the top row. Each entry shows the resulting DCA code:
Least significant nibble
msn	0	1	2	3	4	5	6	7	8	9	a	b	c	d	e	f
0
1
2	40	4f	7f	7b	5b	6c	50	7d	4d	5d	5c	4e	6b	60	4b	61
3	f0	f1	f2	f3	f4	f5	f6	f7	f8	f9	7a	5e	4c	7e	6e	6f
4	7c	c1	c2	c3	4	c5	c6	c7	c8	c9	d1	d2	d3	d4	d5	d6
5	d7	d8	d9	e2	e3	e4	e5	e6	e7	e8	e9	4a	e0	5a	5f	6d
6	79	81	82	83	84	85	86	87	88	89	91	92	93	94	95	96
7	97	98	99	a2	a3	a4	a5	a6	a7	a8	a9	c0	bb	d0	a1	6d
8	63	67	68	71	69	ec	fc	45	44	42	43	46	47	48	51	54
9	52	53	55	58	56	57	49	ce	cd	cb	cc	cf	de	dd	db	dc
a	5c	90	b0	b1	b5	7f	b6	59	af	4e	6d	be	bd	6d	9e	80
b	c2	c2	50	61	b2	a0	6d	e2	6d	86	ee	9a	9b	d3	9c	70
c	ab	aa	ba	6d	b4	e9	6d	8a	8b	4b	41	65	66	ef	d6,	96,
															c5	85
d	60	ad	7f	7f	7d	7d	7a	5c	df	6d	6d	6d	6d	6d	6d	6d
e	6d	6d	6d	6d	6d	6d	6d	6d	6d	6d	6d	6d	6d	6d	6d	6d
f	6d	6d	6d	6d	6d	6d	6d	6d	6d	6d	6d	6d	6d	6d	6d	6d	

As with fonts, it is this stage of the conversion that causes problems, as several different Word character codes can be mapped to some of the DCA character codes.
When the files are read into FrameMaker the characters are then converted to FrameMaker ones using the configuration file 'dca.am' (see above).

How to make it work
The process is very similar to that for fonts. If two characters would share the same DCA character code, one of them is changed to an unused character by editing the RFT file. Then the configuration file 'dca.am' is edited so that this is reversed as the dca file is read into FrameMaker. 
Example
Suppose a file had both the ‘L’ and ‘Ω’ characters in it. 
When the file is converted to RTF, these characters are represented as L and \'bd respectively. They are still differentiated.
When this is then converted to DCA both characters become character code d3 hex, and merge.
This could be avoided by a global exchange on the RTF file, changing the Ω character to an unused character (say ∫). All occurrences of \'bd (ie Ω) are changed to \'ba (ie ∫).
Now when the DCA conversion occurs, the L is still converted to character code d3 hex, but the Ω characters have been changed to ∫ characters, and so are converted to character code ee hex. The characters have maintained a separate identity.
All that is needed then is to change the Sun file dca.am to map character code ee hex back to an ‘Ω’ character.

That's all folks!
If you have problems, get some help from me; it will possibly save you a lot of time reformatting your documents.
Good luck,
Mike.