Han The Thanh (of pdftex fame) did the work on this module.
Tom
On Sun, 23 Jan 2000, Tomas G. Rokicki wrote:
> Just so you know:
>
> the dvips in the pretest works *great* on the files that Karsten sent out.
> That new writet1 looks good! Who did the work?
>
> -tom
>
Hi Karsten,
I am CC'ing this to the tex-k mailing list.
To answer your question, Tom Rokicki is the official maintainer of
dvips(k).
To answer your question about the encoding problem:
Does the original Type 1 font you are subsetting (you wrote partially
encoded but I think you really meant su
That should be
/Encoding 256 array
Sorry about the mix up...
Tom
>
> /Encoding 255 array
> 0 1 255 {1 index exch /.notdef put}
>
On Tue, 7 Mar 2000, Sebastian Rahtz wrote:
> Ken Smith writes:
> > > > D 8000
>
> >
> > > the config.pdf needs a M line specifying a Metafont mode for an 8000
> > > dpi device. hmm.
> >
> > Has anyone, anywhere,
Hi,
>
> It may be time to think about overhauling dvips, probably stealing as much
> as possible from pdftex's output routines.
>
You must mean *completely* rewriting dvips. The grid fitting that
dvips does comes from the days when only PK (at fixed resolutions)
fonts were used; this grid fit
I was thinking about this tonight; I suspect that one can use TrueType
fonts (in Type 42 format) if the following restriction is obeyed:
the font is never ever subsetted
There might be a need to hack soemthing into dvips so that an
appropriate FontMatrix array and Metrics dictionary is writte
that we use /Fa for the dvips name of Times New Roman. Then
we get one font from the ouline font in the PS file, one version of
the font from how rf redefine Times New Roman, and version of the font
from invoking the procedure Fa. If that makes sense...
Tom
On Mon, 24 Apr 2000, Tom Kacvinsky
Use -Go in your dvips flags.
On Wed, 17 May 2000, Verwalter Dr.Betz wrote:
>
> When I use the letters 'fi' (like in benefit), I get them allright in the
> DVI file, but get a pound sign in the PDF file instead.
> Likewise I get a crossed circle sign for 'fl'.
>
> Why is that? Workaround?
> I a
What fonts are using? The message you are seeing is related to
virtual fonts. It could be that one of your virtual fonts is
corrupted (if you are using VFs).
Tom
On Tue, 1 Aug 2000, Nicklas Ekstrand wrote:
> Hi!
>
> I'm trying to compile my thesis with the teTeX-1.0 package but it
> doesn't
This is not a bug; it is known behaviour. dvips was acting as
intended. You did the right thing for your circumstances...
Tom
On Fri, 4 Aug 2000, Rex Dieter wrote:
> I have found in tetex 1.0.6 (redhat linux 6.2) what appears to be a bug in
> the interaction between the times latex package (
Hi all,
I think that most people who are on this list know how to compile the
binaries from source. But these competent people ask for RPMs or
Debian packages because they are managing what is installed on their
boxes with a package manager. That might be an egregious assumption,
but I met Mart
Can we see the problem file? Can you make it available via ftp/web. If not,
mail it directly to me.
I can confirm Rainer's mail that T1Lib works with the CM fonts. I tested xpdf
for use here at the AMS (when we ran into problems with Reader on Digital UNIX).
Thanks,
Tom
On Wed, 1 Nov 2000,
Hi all
On Thu, 2 Nov 2000, Rainer Menzner wrote:
> C. Michael McCallum wrote:
>
> > T1_LoadFont(): Loading font with ID = 3 failed! (mode = -2)
> > T1_LoadFont(): Loading font with ID = 4 failed! (mode = -2)
> > T1_LoadFont(): Loading font with ID = 10 failed! (mode = -2)
> >
>
> These are t1
Hi all,
More below...
On Thu, 2 Nov 2000, Derek B. Noonburg wrote:
> On 3 Nov, Rainer Menzner wrote:
> > Tom Kacvinsky wrote:
> >
> >>
> >> On Thu, 2 Nov 2000, Rainer Menzner wrote:
> >>
> >> > C. Michael McCallum wrote:
> >
The problem is that the xpdf you are using was compiled with an older version of
t1lib. I recompiled my copy of xpdf with a newer version of t1lib, and my
problems went away.
Tom
On Fri, 3 Nov 2000, C. Michael McCallum wrote:
>
> Thanks a lot for the help, everyone... so let me get this strai
I thought it was a known fact that Red Hat boobooed and used a *prerelease*
version of gcc (2.96) to make the system libs and what not for RH 7.0. Which is
probably the cause of the problems. I don't know what to recommend in this
case. Switch to Debian?
Not trying to start a flame war with th
I am using teTeX 1.0.7 and I don't have an adobe.map file. I do, however,
have a file named ar-std-adobe-kb.map that has these lines in it:
ptmb8r Times-Bold "TeXBase1Encoding ReEncodeFont" <8r.enc
> Hi,
>
> I have a problem that I fear is related to the eternal \usepackage{times}
> + dvips -P
I have been watching this thread and meant to respond sooner. Any dvips
which uses t1part for font subsetting is BROKEN with respect to font
subsetting. Use the latest dvips from TeX Live 6.0, which uses the writet1
module from pdftex to take care of susetting.
There are other bugs in dvips wit
18 matches
Mail list logo
