home *** CD-ROM | disk | FTP | other *** search
Wrap
Received: from marziani.fe.infn.it (marziani.fe.infn.it [192.84.144.200]) by nacm.com (8.6.10/8.6.9) with ESMTP id OAA16287 for <executor@nacm.com>; Thu, 30 Nov 1995 14:29:42 -0800 Received: (from marziani@localhost) by marziani.fe.infn.it (8.6.12/8.6.9) id XAA00190; Thu, 30 Nov 1995 23:26:43 +0100 From: marziani@vaxfe.fe.infn.it (Michele Marziani) To: executor@nacm.com Cc: root@abel-jtramp.unl.edu Subject: Linux font & printer problems (Re: executor-digest V1 #350) Date: Thu, 30 Nov 1995 15:12:43 +0100 Organization: Dept. of Physics, Ferrara University, ITALY Reply-To: marziani@vaxfe.fe.infn.it MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <bvbvwETrf67W088yn@vaxfe.fe.infn.it> In-Reply-To: <199511290247.SAA27655@nacm.com> Lines: 90 Sender: owner-paper@nacm.com Precedence: bulk This is a follow-up to a message recently posted to this list, concerning Executor problems with PS output under Linux. I wish to expand on, especially in the MS-Word and font area. > > I recently installed Word 5.1 for macintosh on the emulator > > using Executor Linux- Bleeding Edge version p6. Everything > > seems to work within the program- but I am having problems > > getting the printer to recognize or interpret the postscript > > output.. The printer is attached to the university network > > and appears to print other postscript files just fine.. > > I have gotten this to print on a panasonic 2123 using > > ghostscript- it does fairly well- the true postcript printer > > is coming up with this output.. I know its sending it there at least.. > > > > NewYork-Roman not found, using Courier > > %%[ Error: message: process (0x5d05bc, 'Unnamed Process', runnable) > > Command: 'Array_exec' > > Ostack > > Estack: > > at: '.array_exec_cont' {/execstackoverflow *'standarderroraction'] > > > > > > bunch of stuff.. > > > > Empty Stack > > ]%% > > > > the package I guess this thing is using is neWSprint Interpreter 2.5 Rev B > > > > If I can get the printer to work- then excutor would have the best word > > processor available for linux right now in my opinion. Guess Ill have > > to keep working on it- anyone know how to get gs to interpret a PS file > > so I can have it check it before it is sent to the other interpreter? > > > > root@abel-jtramp.unl.edu I totally agree. I too am wondering how to obtain proper printer output from Word 5.1 under Executor/Linux. A series of comments is in order, IMHO: 1) I have several documents which were created with my Mac IIsi and Word 5.1. When opened with Word under Executor they are shown OK onscreen but the drop-down font list doesn't show, e.g., the default New York font. It seems this and several other very common Mac fonts are not part of Executor. 2) I've got Font D/A Mover 4.1 and tried to install a new font folder consisting of New York fonts. Now, Word correctly displays New York in the dropdown fontlist or when clicking in the middle of a New York paragraph. It even seems to sense bold attributes and the like. The question is: how to print? I have an Apple LW Pro 630 connected to my PC and it should have the New York font built in. However it seems I'm only able to print garbage, i.e. missplaced Courier characters. I've set up a printer filter file (executor_filter) which only includes the following #!/bin/sh lpr -Plw where 'lw' is my printer queue pointing to the LW 630. There is NO printer filter associated with the queue 'lw'. It simply sends the PS output to the printer, directly. It's my preferred printer queue and normally it prints PS flawlessly. 3) How to modify the paper size? Normally a Word 5.1 Page Setup menu item allows this (in the File menu). However, the fake Executor dialog box only allows a limited number of options and it seems there is no means of changing the paper size. Again, the printed output comes out visibly missplaced on the sheet. I'm not surprised at all since a captured PS output clearly showed a %%DocumentPaperSizes: Letter in its header. My feeling is that Word and maybe other important productivity packages are really unusable under Executor, at least until these IMHO serious bugs (?) are fixed. Until then I'm unable to even consider registering (...pardon me, getting a license key for) Executor. Furthermore, it seems quite pricey given the current functional level. I hope someone is able to shed light on the above technical aspects. Take care. -- Michele Marziani Universita' di Ferrara e-mail (work) marziani@vaxfe.fe.infn.it Dipartimento di Fisica (home) marziani@estense.global.it 44100 Ferrara - ITALY * * * voice/fax +39-532-63631