Path: utzoo!mnetor!uunet!husc6!cmcl2!brl-adm!umd5!uvaarpa!mcnc!ecsvax!mjg
From: mjg@ecsvax.UUCP (Michael Gingell)
Newsgroups: comp.sys.ibm.pc
Subject: Re: New Microsoft Word Question
Message-ID: <4314@ecsvax.UUCP>
Date: 15 Dec 87 18:31:55 GMT
References: <3204@tut.cis.ohio-state.edu>
Organization: UNC Educational Computing Service
Lines: 24
Summary: Microsoft printer definition files seem to be sequence oriented.

In article <3204@tut.cis.ohio-state.edu>, mdf@tut.cis.ohio-state.edu (Mark D. Freeman) writes:
> I just upgraded from 3.1 to 4.0.  I use an Okidata Laser, and under 3.1
> I used the HPLASPS driver, as there wasn't an OKILASER driver yet.
> 
> In switching over to the OKILASER driver, I noticed something rather
> odd.  The TMSRMN font was roman-a in one driver and roman-i (or some other
> variant) in the other.  This meant either modifying the OKILASER driver
> to match the HPLASPS driver, or changing all my style sheets.
> 
I noticed the same thing switching from version 2 to version 3. The
printer definition file for the Cordata Laser Printer was changed with
the addition of a number of new fonts.  If I use the new file with
a document prepared with the old file I get all the wrong fonts.  It
looks as if the document you write has embedded in it codes which tell
Word to get the nth font from the start of the file - NOT a specific
code for a style and size of font.

I have ended up with retaining the old file and the new, and selecting
whichever one is needed at print time. I am still waiting for my
upgrade to 4.0. I fully expect to have to maintain 3 different definition
files - and worse to have to remember which documents were prepared
with which definition files.

Mike Gingell    ...decvax!mcnc!ecsvax!mjg