[Tuglist] LaTex to pdf

[Radhakrishnan CV]

On Thu, 2 May 2002 at 20:18, Dileep Padinjarae Vengasseri wrote:

   I am getting an error message while doing this. It seems I do not
   have a config file for cms. I searched for a config.cms file but
   is missing in my computer. Is the problem coming because of this?
   If so, is there any solution for this?

You can create your own config.cms, which is trivial. Here goes my 
config.cms:

p +bsr.map
p +bakomaextra.map

The above two lines constitute my config.cms. Make sure that you 
have bsr.map and bakomaextra.map in the same directory where 
config.cms resides. And if you don't have the bsr.map, you can 
create that too:

cmbsy6  CMBSY7   <cmbsy7.pfb
cmbsy8  CMBSY7   <cmbsy7.pfb
cmbsy9  CMBSY10  <cmbsy10.pfb
cmbxti7 CMBXTI10 <cmbxti10.pfb
cmcsc8  CMCSC10  <cmcsc10.pfb
....

where the first field is the font name as used by TeX (see the
corresponding .fd file like ot1cmr.fd), second is the font name
given inside the font file, third field is the name of the real
postscript font file.

   And regarding Rai's suggestion of using pdflatex, I have fairly
   good number of .eps files in my document and I have read that
   pdflatex does not work when one is having .eps files included in
   Tex. I tried converting my .eps files to .pdf by epstopdf, but
   this also gave the same error of having type 3 fonts, and
   consequently some missing text when viewed with xpdf.

This is because, your eps graphic uses proprietary fonts (which are
not freely available and therefore ghostscript does not know
especially in the absence of font metrics and related info in the
graphic) and secondly, the fonts are not subset in your graphic.
This could be because, while exporting to eps from your graphic
application, it converts the glyphs into bitmapped images instead of
keeping it as characters and including the glyph metrics and related
info in the eps graphic.  If you can prevent this, you won't face
the type3 problem any more.

   I found a config.cm file and I tried the option dvips -Pcm on
   foo.dvi and converted to foo.ps. This on further conversion to

That is perfectly correct.

   foo.pdf gave a reasonable document in xpdf. But, whenever I am
   including figures from other softwares it is showing the error
   message as mentioned above and thus missing some texts.

Always use standard font families (like Times Roman, Helvetica, etc)  
available in any postscript printer. Your woes will be substantially
reduced.

-- 
Radhakrishnan