Services & Resources / Wolfram Forums
-----
 /
MathGroup Archive
1999
*January
*February
*March
*April
*May
*June
*July
*August
*September
*October
*November
*December
*Archive Index
*Ask about this page
*Print this page
*Give us feedback
*Sign up for the Wolfram Insider

MathGroup Archive 1999

[Date Index] [Thread Index] [Author Index]

Search the Archive

Re: LaTeX Output

  • To: mathgroup at smc.vnet.net
  • Subject: [mg19581] Re: LaTeX Output
  • From: paulh at wolfram.com (P.J. Hinton)
  • Date: Sat, 4 Sep 1999 01:34:21 -0400
  • Organization: "Wolfram Research, Inc."
  • References: <7qkqsu$h4r@smc.vnet.net>
  • Sender: owner-wri-mathgroup at wolfram.com

In article <7qkqsu$h4r at smc.vnet.net>, jslater at cs.wright.edu (Joseph C. Slater) writes:

>I'm having trouble getting LaTeX to view print the mysymdoc.tex file. In
>viewing I konw I need to figure out how to get my dvi viewer to use the
>virtual fonts. It currently is trying to make pk fonts from Math1.mf and
>other similar files that do not exist.

At this time, there is no way to generate PK versions of the Math fonts.
Attempts by outside parties to use a tool like ps2pk to translate the
Type 1 fonts have run into complications.  The font glyphs are viewable
only after the document has been translated to PostScript by DVIPS.

>In printing, I can only print up to page for before I get a postscript
>error. I think it's coming back from my printer, but I can't be sure.
>Ghostview won't view the generated ps file. I get the following:
>
>Folder:msymdoc.ps) run } .runjob
>Error: /invalidfont in -dict-
>Operand stack:
>   false   Math2-Bold   --dict:11/20(L)--   Font   Math2-Bold  
>--dict:11/20(L)--   Math2-Bold
>Execution stack:
>   %interp_exit   .runexec2   --nostringval--   --nostringval--  
>--nostringval--   2   %stopped_push   --nostringval--   0   3  
>%oparray_pop   --nostringval--   %loop_continue   1   3   %oparray_pop  
>--nostringval--   --nostringval--   false   1   %stopped_push  
>--nostringval--   --nostringval--   false   1   %stopped_push   1   3  
>%oparray_pop   1   3   %oparray_pop   .runexec2   --nostringval--  
>--nostringval--   --nostringval--   2   %stopped_push   --nostringval--  
>3   3   %oparray_pop   --nostringval--   --nostringval--   3   4  
>%oparray_pop   4   4   %oparray_pop   --nostringval--   --nostringval--  
>--nostringval--   8   5   %oparray_pop   --nostringval--   8   5  
>%oparray_pop   --nostringval--   --nostringval--
>Dictionary stack:
>   --dict:858/941(G)--   --dict:0/20(G)--   --dict:51/200(L)--  
>--dict:858/941(G)--   --dict:16/23(G)--
>Current allocation mode is local
>Current file position is 23895
>GS<1>
>
>
>Does the Save as Special:LaTeX actually work? It doesn't seem like
>everything you need has been put together.

This is unrelated to the LaTeX export feature in the kernel.  It 
is a known problem with the Type 1 font Math2-Bold.pfa.  There is
an FAQ page on this at the Technical Support website.

http://support.wolfram.com/FrontEnds/Export/TeX/DVIPS.html

Later versions of both Ghostscript and DVIPS are susceptible to 
failure when processing a file that requires Math2-Bold.  It 
sounds as if you may be using an older version of DVIPS and a newer
version of Ghostscript.

--
P.J. Hinton
Mathematica Programming Group           paulh at wolfram.com
Wolfram Research, Inc.
Disclaimer: Opinions expressed herein are those of the author alone.


  • Prev by Date: Re: Range[imin,imax,di]; was it better in 3.0 than in 4.0 ?
  • Next by Date: Re: Freeing memory in Mathematica
  • Previous by thread: LaTeX Output
  • Next by thread: Re: LaTeX Output