Fonts in eps figures

[Ganz, Frank, Springer US]

Dear Sue,

First thought that comes to my mind, add the following optional command
line flags to the command line when you run DVIPSONE.

-*i -v -j

Usage:

Dvipsone -*i -v -j book.dvi


If you run DVIPSONE from within DVIWINDO, you can add -*i -v -j to

Preferences > Command Line > dvipsone


If this doesn't do anything for you, then please provide a .log file
from your dvipsone session.


Next thing, I'd be willing to look at a sample file if you don't mind.
It seems a complicated enough scenario to warrant a sample so that the
issue can be tranced to the correct cause in one go. Otherwise, we might
give you suggestions over and over without avail.

Thanks,
Frank

>-----Original Message-----
>From: Support for users of Y&Y's TeX system
>[mailto:YANDYTEX at LISTS.UCC.IE] On Behalf Of Don R. Robinson
>Sent: Thursday, July 14, 2005 2:57 PM
>To: YANDYTEX at LISTS.UCC.IE
>Subject: Re: Fonts in eps figures
>
>On Thu, 14 Jul 2005 19:20:31 +0100, Sue Rodd <jcm at LMS.AC.UK> wrote:
>
>>Hi there
>>
>>Once again, I have (I think) a problem with fonts (nothing
>changes...).
>>
>>I have a paper from an author, which includes dozens of eps
>figures. He
>has
>>used mathtype for the labelling, and it all prints out
>perfectly on my
>>HP printer if I print direct from the dvi file.  His conversion of the
>original
>>tex file to pdf also prints out correctly.
>>
>>However, if _I_ convert to postscript and then PDF using my trusty
>>YandY,
>a
>>number of the symbols just disappear from some of the figures
>(\varnothing,
>>\alpha, \prime, \vee and \wedge -- but all the letters seem
>to come out
>OK)!
>>This happens with both his original tex file and with the one that I
>>have edited with our journal style.
>>
>>I have tried various subterfuges like using different
>>graphics-insertion techniques, but that doesn't seem to help.
>>
>>I seem to need MTMI, MTEX, MTMS and MTSYN.  I'm using Windows 2K, and
>>all these appear in the list of fonts in WINNT, with the
>correct red "a"
>symbol
>>for type 1 fonts.  If I list the fonts in the paper, using DVIWIndo,
>>none
>of
>>them appears in the "TT" column.  There is also, however, an
>"MT Extra"
>>Truetype font in WINNT -- could that be confusing the issue?  I could
>>see
>a
>>tfm file when I looked, but not an AFM one, so I tried making
>one from
>>DVIWindo.  The pfb and pfm files are in lower-case, and the
>tfm and afm
>>in upper -- does this matter?
>>
>>(I have just been to the ctan site and picked up new tfm files, but
>>that also seems to have no effect.)
>>
>>Printing out one of the pages with a problem figure on, I get the
>following
>>log:
>>
>>***************************************
>>Printing directly from DVIPSONE.DLL
>>Current directory: `C:\Texdocs\folder\subfolder'
>> 0: `DVIPSONE'
>> 1: `-v'
>> 2: `-d=C:\Texdocs\jcm2004\jcm2004-060b\filename.ps'
>> 3: `-B=11'
>> 4: `-E=11'
>> 5: `-l=a4'
>> 6: `-K'
>> 7: `-y'
>> 8: `142'
>> 9: `-V'
>>10: `C:\Texdocs\folder\subfolder\filename.dvi'
>>DVIPSONE 2.2.8  2002 Apr 30 09:44:06 SN 4962 Copyright (C)
>1990--2002,
>>Y&Y, Inc.  http://www.YandY.com
>>
>>Command:
>>DVIPSONE -v -d=C:\Texdocs\folder\subfolder\filename.ps -B=11 -E=11
>>-l=a4 -
>K
>>-y 142 -V C:\Texdocs\folder\subfolder\filename.dvi
>>Processing DVI file C:\Texdocs\folder\subfolder\filename.dvi
>>(to C:\Texdocs\folder\subfolder\filename.ps)
>>TeX output 2005.07.14:1909
>>Warning: no ATMREG.ATM Font Table:
>>  0 tii        at:    10 pt
>>  1 tir        at:     8 pt
>>  2 tir        at:    12 pt base:  1 ( 38) *new-size*
>>  3 tirsc      at:    10 pt *unused*
>>  4 tir        at:    10 pt base:  1 ( 38) *new-size*
>>  5 MTMI       at:    10 pt
>>  6 tib        at:    10 pt
>>  7 MTSYN      at:    10 pt
>>  8 tii        at:     8 pt base:  0 ( 15) *new-size*
>>  9 msbm10     at:    10 pt
>> 10 tir        at:   7.6 pt base:  1 ( 38) *new-size*
>> 11 MTEX       at:    10 pt
>> 12 MTMS       at:    10 pt *unused*
>> 13 MTSYN      at:   7.6 pt base:  7 ( 21) *new-size*
>> 14 MTMI       at:   7.6 pt base:  5 ( 18) *new-size*
>> 15 msam10     at:    10 pt *unused*
>> 16 MTSYN      at:     6 pt base:  7 ( 21) *new-size*
>> 17 msbm7      at:   7.6 pt *unused*
>> 18 lasy10     at:    10 pt *unused*
>> 19 tir        at:     6 pt base:  1 ( 38) *new-size*
>> 20 msam7      at:   7.6 pt *unused*
>> 21 MTMS       at:   7.6 pt base: 12 ( 41) *new-size*
>> 22 MTMI       at:     6 pt base:  5 ( 18) *new-size*
>> 23 com        at:     9 pt *unused*
>> 24 com        at:    10 pt base: 23 ( 64) *new-size*
>>
>>[tii~] [tir~] [MTMI] [tib~] [MTSYN] [msbm10] [MTEX] Processed 7 font
>>files  - remapped 3 fonts to `TEXNANSI' encoding.
>>[11 fig1.eps fig2.eps]
>>Max stack depth 16 - 25 font slots used - DVI file contains 50 pages
>>Processed 1 page
>>Time: 0.547 sec (0.029 sec per font file + 0.344 sec per page output)
>>
>>DONE
>>***********************************
>>
>>Please, someone, tell me I've done something dumb, and there's an easy
>fix!
>>
>>All the best
>>
>>Sue
>
>I have had similar problems when including ps files in LaTeX
>documents.  I created the ps files with metapost and use the
>LaTeX commands to typeset labels for various diagrams.  When I
>included the ps files in LaTeX documents all that showed up
>was a box and a label indicating which file was used.  I
>printed to Actobat distiller (5.0) to produce pdf files and
>was surprised that only some of the typeset material showed up
>in my diagrams.  It finally dawned on me that the distiller
>only partially embeds fonts (a requirement for the font
>license) and does not recognize characters within a ps file as
>needing to be embedded.
>
>I got around the problem by including a line in the document
>(outside of any diagram) that included all the characters I
>used in the diagrams.
>Then with Acrobat's text touch-up tool, I simply removed them
>from the pdf file.  The characters showed up in the diagram.
>After a while, I got more creative and simply built the
>characters into the narrative that appeared before the
>diagram, so no after-the-fact touch up was needed.
>
>Others may have simpler suggestions, but this method has
>always worked for me.
>