Microsoft KB Archive/95270

{|
 * width="100%"|

WD: How Fonts Are Mapped Between MacWord 5.0/5.1 and WinWord 2.

 * }

Q95270

-

The information in this article applies to:


 * Microsoft Word for the Macintosh, versions 5.0, 5.1
 * Microsoft Word for Windows, versions 2.0, 2.0a, 2.0a-CD, 2.0b, 2.0c, 2.0c-CD

-

SUMMARY
When documents are converted between Microsoft Word for the Macintosh and Word for Windows, Word automatically maps the majority of the most common fonts to their closest equivalents on the target platform. However, given the large number of printer drivers available for Windows, and the large number of soft fonts and font cartridges available for both operating environments, Word cannot automatically anticipate and map all source font possibilities to equivalents that may or may not be available on the other platform.

For example, in Word for the Macintosh when you open a document in Word for Windows format, TrueType fonts such as Lucida Blackletter will most likely map to New York. Likewise, in Word for Windows when you save the same document directly in Word for the Macintosh format, Lucida Blackletter will most likely map to Times.

MORE INFORMATION
Because neither Word product can automatically provide perfect mapping of all fonts to or from the other Word product, you can create a custom font- mapping file to override the default mappings performed by the converter. A font-mapping file is simple to create, and if you create mappings for all the fonts you anticipate using on your Windows and Macintosh computers, you only need to create a custom font-mapping file once.

If you plan to open or save Word for the Macintosh format files from within Word for Windows, all necessary information on the creation of a custom font-mapping file under Windows is included in the font-mapping information files Rtf_mw5.txt and Mw5_rtf.txt located in your Word for Windows directory. Rtf_mw5.txt provides instructions on creating a font-mapping file that the converter will use when saving a document from Word for Windows in Word for the Macintosh format. Mw5_rtf.txt provides instructions on creating a font-mapping file that will be used by the converter when opening from Word for the Macintosh format files into Word for Windows. See the contents of each file below for more information.

If you choose instead to open or save Word for Windows format files from within Word for the Macintosh, all necessary information on the creation of a Macintosh-based custom font-mapping file is included in the section titled &quot;Sample Font-Mapping Files&quot; in the Conversion Information document located in your Word for the Macintosh folder. Unlike the two unidirectional mapping files used by Word for Windows, the MS Word for Win FontMap file used by Word for the Macintosh is a single, bidirectional font-mapping file. See the copy of these instructions below for more information.

NOTE: There is no advantage to using the custom font-mapping functionality on one platform versus the other. The option is available on both platforms to provide maximum flexibility. Although the syntax of the mapping files on the two platforms differs slightly, the purpose and outcomes are identical. If you want to make the process completely transparent for users in an environment where Word is used on both platforms, you may want to create font-mapping files on both platforms to anticipate whatever File Open or File Save As option a user might choose.

Contents of Word for Windows Rtf_mw5.txt Sample Font-Mapping File
 # This is a sample font mapping file for converting Word for # # # # # # # # # # #
 * 1) Windows documents into Word for the Macintosh 5.0.  In
 * 2) order for this file to be used by the converter, it should
 * 3) be renamed RTF_MW5.DAT.
 * 1) Each line of this file describes how a particular Word for
 * 2) Windows font should map to a Word for Macintosh font during
 * 3) the conversion.  The syntax for each entry is:
 * 1)      MacFontName;FontName[;FontFamily]
 * 1) FontName is the name of the original font used in the Word
 * 2) for Windows document.  MacFontName is the name of the
 * 3) Macintosh font you would like used in place of the FontName
 * 4) when that document is converted to Word for the Macintosh.
 * 5) The FontName must be separated from the MacFontName by a
 * 6) semicolon.  The FontFamily describes what type of font the
 * 7) MacFontName is.  This allows Word for the Macintosh to find
 * 8) a similar font if the NewFontName specified doesn't exist
 * 9) on the Macintosh platform.  The FontFamily is optional and
 * 10) does not need to be included in the entry.  If it is
 * 11) present, it must be separated from the NewFontName by a
 * 12) semicolon.  The possible values for the font family are:
 * 1) R    Roman - Proportionally spaced serif fonts (Tms Rmn,
 * 2)      Roman, etc.)
 * 1) S    Swiss - Proportionally spaced sans serif fonts (Helv,
 * 2)      Helvetica-Narrow, etc.)
 * 1) M    Modern - Fixed pitch fonts (Courier, Pica, etc.)
 * 1) N    No family
 * 1) P    Script - Script fonts (cursive, etc.)
 * 1) D    Decor - Decorative fonts (Old English, Zapf Chancery
 * 2)      etc.)
 * 3) T    Technical - symbol, and mathematical fonts (Symbol)
 * 1) Each entry in this sample file is marked as a comment.  In
 * 2) order for the mapping to take effect, remove the comment
 * 3) marker (#) that appears as the first character in the line.
 * 1) AvanteGarde;AvantGarde;S
 * 2) Bookman;Bookman;R
 * 3) Courier;Courier;M
 * 4) Fences;Fences;T
 * 5) Helv;Helv;S
 * 6) Helvetica-Narrow;Nelvetica-Narrow;S
 * 7) LinePrinter;LinePrinter;M
 * 8) Modern;Modern;S
 * 9) MS Linedraw;MS LineDraw;T
 * 10) MT Extra;MT Extra;T
 * 11) MT Symbol;MT Symbol;T
 * 12) NewCenturySchlbk;NewCenturySchlbk;R
 * 13) Palatino;Palatino;R
 * 14) Roman;Roman;R
 * 15) Embassy BT;Script;D
 * 16) Symbol;Symbol;T
 * 17) Tms Rmn;Tms Rmn;R
 * 18) ZapfChancery;ZapfChancery;D
 * 19) ZapfDingbats;ZapfDingbats;T

Contents of Word for Windows MW5_RTF.TXT Sample Font-Mapping File
 # This is a sample font mapping file for converting Word for # # # # # # # # # # #
 * 1) Macintosh 5.0 documents into Word for Windows.  In order
 * 2) for this file to be used by the converter, it should be
 * 3) renamed MW5_RTF.DAT.
 * 1) Each line of this file describes how a particular Word for
 * 2) Macintosh font should map to a Word for Windows font during
 * 3) the conversion.  The syntax for each entry is:
 * 1)      MacFontName;NewFontName[;FontFamily]
 * 1) MacFontName is the name of the original font used in the
 * 2) Word for Macintosh document.  NewFontName is the name of the
 * 3) Windows font you would like used in place of the MacFontName
 * 4) when that document is converted to Word for Windows.  The
 * 5) NewFontName must be separated from the MacFontName by a
 * 6) semicolon.  The FontFamily describes what type of font the
 * 7) MacFontName is.  This allows Word to find a similar font if
 * 8) the NewFontName specified doesn't exist on the Windows
 * 9) printer driver currently being used.  The FontFamily is
 * 10) optional and does not need to be included in the entry.  If
 * 11) it is present, it must be separated from the NewFontName by
 * 12) a semicolon.  The possible values for the font family are:
 * 1) R    Roman - Proportionally spaced serif fonts (Tms Rmn,
 * 2)      Roman, etc.)
 * 1) S    Swiss - Proportionally spaced sans serif fonts (Helv,
 * 2)      Helvetica-Narrow, etc.)
 * 3) M    Modern - Fixed pitch fonts (Courier, Pica, etc.)
 * 1) N    No family
 * 1) P    Script - Script fonts (cursive, etc.)
 * 1) D    Decor - Decorative fonts (Old English, Zapf Chancery
 * 2)      etc.)
 * 1) T    Technical - symbol, and mathematical fonts (Symbol)
 * 1) Each entry in this sample file is marked as a comment.  In
 * 2) order for the mapping to take effect, remove the comment
 * 3) marker (#) that appears as the first character in the line.
 * 1) 1-800-Monotype;1-800-Monotype;M
 * 2) Abadi-Light;Abadi-Light;S
 * 3) Arial reg;Arial reg;S
 * 4) Chicago;Chicago;S
 * 5) Courier;Courier;M
 * 6) Embassy BT;Script;D
 * 7) Geneva;Geneva;S
 * 8) Helvetica;Helv;S
 * 9) Kells;Roman;D
 * 10) Monaco;Monaco;M
 * 11) MT Extra;MT Extra;T
 * 12) New York;New York;R
 * 13) Palatino;Palatino;R
 * 14) Sans Serif;Helv;S
 * 15) Stencil BT;Roman;D
 * 16) Symbol;Symbol;T
 * 17) Times;Times;R

Contents of the Word for the Macintosh &quot;MS Word for Win FontMap&quot;
 # This is a sample font-mapping file for converting documents between # # # # # # # # # # # # # # # # # To win word # From win word Additional query words: fontmap translate transfer formats formatting
 * 1) Word for the Macintosh and Word for Windows. In order for this file
 * 2) to be used by the converter, all of the lines of this sample file
 * 3) should be selected then copied and pasted into a new document. You
 * 4) must save the new document as a Text Only file with the name &quot;MS
 * 5) Word for Win FontMap&quot; in one of the following locations:
 * 1) - The Preferences folder if you are using System 7
 * 1) - The same folder as the Word for Windows document being read into
 * 2)   Word for the Macintosh or saved as Word for Windows
 * 1) - The same folder as the Word for Windows converter. Word installs
 * 2)   this converter in the Word Commands folder within the Word folder.
 * 1) - The Word folder
 * 1) Converting to Word for Windows
 * 1) The font-mapping entries for converting to Word for Windows are in
 * 2) the section called &quot;To win word.&quot; It is necessary to have a space
 * 3) between the words &quot;win&quot; and &quot;word.&quot; Each line of this section
 * 4) describes how a particular Word for the Macintosh font should map to
 * 5) a Word for Windows font during the conversion. The syntax for each
 * 6) entry is:
 * 1) 
 * 1)  is the name of the Macintosh font you want to replace
 * 2) with the Windows font defined by . It is separated from
 * 3) the  by a semicolon.
 * 1) For example, suppose you want to customize how the Geneva font is
 * 2) mapped when converting to Word for Windows. If you are using the
 * 3) Windows PostScript printer driver, then you will probably want that
 * 4) font to become &quot;Helvetica.&quot; In the &quot;To win word&quot; section, the
 * 5) following entry should be made without the comment marker (#) at the
 * 6) start of the line:
 * 1) Geneva; Helvetica
 * 1) This entry tells the converter to use font &quot;Helvetica&quot; in place of
 * 2) Geneva whenever it creates a Word for Windows document. It is
 * 3) important for the font to be spelled in the font-mapping file
 * 4) exactly as it is in Word for the Macintosh.
 * 1) Converting from Word for Windows
 * 1) The font-mapping entries for converting from Word for Windows are in
 * 2) the section called &quot;From win word.&quot; Once again, it is necessary to
 * 3) have a space between the words &quot;win&quot; and &quot;word.&quot; Each line of this
 * 4) section describes how a particular Word for Windows font should map
 * 5) to a Word for the Macintosh font during conversion. The syntax for
 * 6) each entry is:
 * 1) 
 * 1)  is the name of the Windows font you want to replace
 * 2) with the Macintosh font defined by . It is separated
 * 3) from the  by a semicolon.  must be spelled
 * 4) exactly as it appears on your Macintosh.
 * 1) Each entry in this sample file is marked as a comment. In order for
 * 2) the mapping to take effect, remove the comment marker (#) at the
 * 3) beginning of each appropriate line. Any new entries you insert
 * 4) should not have a # comment marker at the beginning of the line.
 * 1) Chicago; Chicago
 * 2) Courier; Courier New
 * 3) Geneva; Arial
 * 4) Helvetica; Arial
 * 5) Monaco; Courier New
 * 6) New York; Times New Roman
 * 7) Palatino; Palatino
 * 8) Symbol; Symbol
 * 9) Times; Times New Roman
 * 1) Arial; Arial reg
 * 2) Courier; Courier
 * 3) Courier New; Courier
 * 4) Modern; Helvetica
 * 5) Symbol; Symbol
 * 6) Times New Roman; Times
 * 7) Roman; Times
 * 8) Script; Embassy BT

Keywords : kbinterop winword macword wordconvert

Issue type : kbinfo

Technology : kbWordSearch kbWordWSearch kbWordMSearch