On Sun, Jan 05, 2003 at 10:13:38PM -0500, David Z Maze wrote:
> What's the error message you're getting? CM, being the TeX standard
> font, really should Just Work...
No message. CM works fine.
> Has absolutely nothing at all to do with TeX, PostScript, or
> displaying things in gv.
The proble
Oki DZ <[EMAIL PROTECTED]> writes:
> I converted a .dvi file into a .ps one. The converter (dvips) couldn't
> find the font (Computer Modern) for the .ps file, so the font displayed
> wrongly in gv.
What's the error message you're getting? CM, being the TeX standard
font, really should Just Work.
Carel Fellinger <[EMAIL PROTECTED]> writes:
CF> You *really* can't do LaTeX without the real book "LaTeX, A
CF> document preparation system" by Lamport. At least that has been my
CF> experience in twenty odd years of TeXing. And if you're into very
CF> arcane type setting you can't do without "The
On Wed, Jul 25, 2001 at 12:06:09PM -0500, Dave Sherohman wrote:
> On Tue, Jul 24, 2001 at 06:17:16PM -0500, Richard Cobbe wrote:
...
> > (I found this documented, if sparingly, in the LaTeX Companion, by
> > Goossens, Mittelbach, and Samarin; ISBN 0-201-54199-8, section 11.9.1.)
>
> That seems to
On Tue, Jul 24, 2001 at 06:17:16PM -0500, Richard Cobbe wrote:
> There are a number of postscript fonts provided with dvips that you can use
> in TeX. As you have discovered, though, finding them is the trick.
> Check out psfonts.map, from the tetex-base package. In potato, at least,
> there are
On Tue, Jul 24, 2001 at 08:46:54PM -0500, Dave Sherohman wrote:
> dvips sends its output directly to the printer by default and I haven't
> gotten around to determining how to change that yet, so I've been viewing
> it as rendered by an HP LaserJet (IIRC) 5000.
>
From the dvips manpage:
-o
Alan Shutko got most of your questions in a separate mail; there are just a
couple of loose endings.
Lo, on Tuesday, July 24, Dave Sherohman did write:
> On Tue, Jul 24, 2001 at 06:17:16PM -0500, Richard Cobbe wrote:
> > Hm. When you say that cmr17 looks almost as bad as cmr10, what exactly do
>
Dave Sherohman <[EMAIL PROTECTED]> writes:
> cmr10 and cmr17 both come out looking like bitmapped fonts (gee, I wonder
> why...) which have been blown up without decent antialiasing - the closure
> at the top of "o" is so thin it practically isn't there, the sides
> (particularly the left side) of
On Tue, Jul 24, 2001 at 06:17:16PM -0500, Richard Cobbe wrote:
> Yeah, this gets confusing. TeX just needs the .tfm file, which basically
> tells it how tall and how wide each letter is, as well as how far below the
> baseline it extends. There's also some ligature and kerning info (how TeX
> tur
Dave Sherohman <[EMAIL PROTECTED]> writes:
> This error message may have given me the thought to try cmr17 instead
> of CMR17, which does work (although it looks almost as bad as cmr10),
> but it still doesn't provide any hints towards finding out what fonts
> are available (and usable) on my syst
Lo, on Tuesday, July 24, Dave Sherohman did write:
> I've finally gotten around to learning some TeX and I'm having a terrible
> time with fonts:
>
> First I looked at the Gentle Guide's list of 'normally available'
> fonts and grabbed the biggest Roman I could find, only to be told
> "! Font \sf
-BEGIN PGP SIGNED MESSAGE-
Hallo Syrus,
On Sat, 29 Mar 1997, Syrus Nemat-Nasser wrote:
>
> I don't know, but I'm very happily using the new tetex packages from
> unstable which seem to fix most of the previous problems with the tex
> packages. I'm doing this on two machines that I upg
On Sat, 29 Mar 1997, Ralf Comtesse wrote:
> -BEGIN PGP SIGNED MESSAGE-
>
> Hi,
>
> When I use some of the not so common fonts in a TeX document, MakeTeX* of
> debian 1.2.7 cannot generate them automatically anymore. The *.tfm files
> are present and I think all paths in texmf.conf are co
13 matches
Mail list logo
