🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.windows.interviews
Article #585

Re: Problems in printing 3.1 IV ref docs with 3.0 doc

#585
From: Shailesh M. Potnis
Date: Thu, 03 Sep 1992 18:32
56 lines
2285 bytes
From article <pabo9co@fido.asd.sgi.com>, by linton@marktwain.rad.sgi.com (Mark Linton):
> In article <3511@babcock.cerc.wvu.wvnet.edu>, smp@cathedral.cerc.wvu.wvnet.edu (Shailesh M. Potnis) writes:
> |> 	I am having problems with the print quality of the .ps files produced
> |> from v 3.1 beta iv/src/man/refman/ch*.doc by using iv 3.0 doc.  Is the print
> |> quality problem due to the version mismatch of the doc bin and the doc files
> |> or is there a bug/font problem at my site.
> 
> Some older versions of doc need the resource "idraw_font_metrics" set off
> to use the correct PostScript fonts (a misfeature fixed in newer versions).
> There hasn't been a change in the doc file format.



	I do not quite understand.  I tried to set this resource as any of the
following in my .Xdefaults file:

idraw_font_metrics: 0
idraw_font_metrics: ""

Assuming a mis print and looking at the idraw man pages also tried:

idraw.font_metrics  0
idraw.font_metrics  ""

Neither of these have helped to improve the print quality.  Is there a
modification to the .ps file which can be useful?  Earlier I had a fix
on the net from Paul Calder for the glyphs.ps file.  
Change the definition of /sf in the file's prolog as follows ...

***************
*** 5,13 ****
  save 20 dict begin
  
  /sf {
!     exch FontDirectory 1 index known not
!     {pop /Courier} if
!     findfont exch scalefont
      setfont
  } def
  
--- 5,12 ----
  save 20 dict begin
  
  /sf {
!     exch {findfont} stopped {pop /Courier findfont} if
!     exch scalefont
      setfont
  } def
  

This fix does not however work with the *.ps files generated from refman/*.doc
files using doc v3.01

--
Shailesh Potnis, Associate	|Concurrent Engineering Research
Member of Technical Staff	|Center, West Virginia University
Technical Details
Message-ID: <3518@babcock.cerc.wvu.wvnet.edu>
Path: arc1-ca.pugleaf.net!sparky!uunet!gatech!darwin.sura.net!haven.umd.edu!cs.wvu.wvnet.edu!cerc.wvu.wvnet.edu!babcock.cerc.wvu.wvnet.edu
References: <pabo9co@fido.asd.sgi.com>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!gatech!darwin.sura.net!haven.umd.edu!cs.wvu.wvnet.edu!cerc.wvu.wvnet.edu!babcock.cerc.wvu.wvnet.edu
From: smp@babcock.cerc.wvu.wvnet.edu (Shailesh M. Potnis)
Newsgroups: comp.windows.interviews
Subject: Re: Problems in printing 3.1 IV ref docs with 3.0 doc
Message-ID: <3518@babcock.cerc.wvu.wvnet.edu>
Date: 3 Sep 92 18:32:47 GMT
References: <pabo9co@fido.asd.sgi.com>
Sender: news@cerc.wvu.wvnet.edu
Lines: 56