home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.text.frame
- Path: sparky!uunet!gatech!europa.asd.contel.com!howland.reston.ans.net!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!cis.ohio-state.edu!news.sei.cmu.edu!ask
- From: ask@sei.cmu.edu (Alan Koch)
- Subject: Re: UNIX FrameMaker Default Printer
- Message-ID: <1992Dec21.160417.29480@sei.cmu.edu>
- Keywords: UNIX FrameMaker Default Printer
- Sender: netnews@sei.cmu.edu (Netnews)
- Organization: The Software Engineering Institute
- Date: Mon, 21 Dec 1992 16:04:17 EST
- Lines: 37
-
-
- David Fuchs from Frame Technology writes to me:
-
- > Alan, I believe that the circumstances you describe do not match up with the
- > reality of FrameMaker 3.1 for X platforms.
-
- This is a VERY polite way of telling me I lied.
-
- > In particular, if a user never
- > changes the "Printer Name" field of the Print dialog, FrameMaker docs will
- > remember the fact that they are being printed to the "default" printer, and
- > not the particular name of the (default) printer, so when users exchange
- > doc, they should print to the respective default printer of each user.
-
- Through much experimentation (which I should have done in the first place),
- I found that he is, in fact, right.
-
- It seems that, if the contents of the PrinterName edit box in the Print dialog
- matches your Maker.printerName X resource, then the name is NOT stored in your
- document; if it does not match, then it IS stored.
-
- PARTIAL RETRACTION
- ------------------
-
- The problem I descibed in my article does not actually exist,
- BUT
- The "fix" I described DOES work as I indicated.
- (It just doen't fix anything.)
-
- Excuse me while I go crawl into a hole somewhere.
-
- ask@sei.cmu.edu
-
- Alan S. Koch
- Software Engineering Institute
- Carnegie Mellon University
- Pittsburgh, PA 15213
-