Re: CM-Super font package v0.2.0

2001-10-10 Thread Tom Kacvinsky

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 with respect to font subsetting.  In
particular, one problems is that one cannot (usually) reencode a font
multiple times and subset the PFB/PFA file sent to dvips.  Tom Rokicki and
I are aware of this problem and we will work on getting this fixed.

The fonts that Vladimir asked me to look at are OK; the problem is with
dvips.

Tom

On Wed, 10 Oct 2001, Harald Hanche-Olsen wrote:

 + Rolf Niepraschk [EMAIL PROTECTED]:

 | Harald Hanche-Olsen wrote:
 | [...]
 |  texc.prot1.enctexps.pro. sfti0900.pfb Second number not found in Char 
string of '/FontName'
 | 
 |
 | I have found a similar problem with dvips 5.86e and the brushscript font
 | (the previous version). With
 |
 |   .. type1fix --infile=pbsi.pfa.orig --outfile=pbsi.pfa \
 |--kill-unenc=yes --ofmt=pfa
 |   .. t1binary pbsi.pfa pbsi.pfb
 |
 | I have solve this problem. `type1fix' is a perl script from the TeXtrace
 | package. May be this helps also with CM-Super...

 No, it didn't help. With --kill-unenc=yes it removed a bunch of glyphs
 from the font file; and whether I included that or not, dvips failed
 in the same way.

 + Nicolas Markey [EMAIL PROTECTED]:

 | Le 08.10.01, Harald Hanche-Olsen a écrit :
 |
 |Just a quick question to you all: Did any of you successfully use the
 |CM-super fonts with teTeX 1.07 (or dvips 5.86)?
 |
 | I got the same problem; installing dvips 5.86d solves that problem.

 Well, Nelson Beebe did some extensive testing. With dvips(k) 5.86e, he
 got these results:

 On linux: ok; on irix: segfault; on alpha/osf: 531 Subr not found.
 The latter happened also with 5.86d.

 He also suggested trying t1disasm, t1binary, and t1ascii on the
 fonts. They will work on the font files (well, I only worked on
 sfrm1000.pfb) without complaint, and converting between format and
 then back to pfb yields a file identical to the original. I also got
 hold of Adobe's specifications, and can certainly see no lack of
 compliance there.

 I know it's usually bad form to quote private mail in a public forum,
 but this one from a mail exchange with Nelson Beebe sums up the
 situation better than I could have stated it myself:

 + Nelson H. F. Beebe [EMAIL PROTECTED]:

 | You are right that dvips may well make assumptions about fonts
 | that are unwarranted.  This has been an ongoing problem, with
 | Adobe's own TypeManager assuming more stylized formatting than
 | Adobe's black-and-white book requires in its documentation
 | of the Type 1 format.

 So, I guess the next step is to try to understand t1part.c and how it
 fails on these font files. Then maybe the font files can be tweaked so
 the problem does not happen, and an improved t1part.c might make it
 into dvips in the long run.

 Please note that, as I no longer believe the dvips version is an
 important factor in this problem, I think this discussion properly
 belongs on the tex-fonts lists and should be discontinued on the teTeX
 list. I have set the Reply-To header accordingly; override it only if
 you must.

 - Harald





Re: embedding times for distilling to pdf

2001-06-29 Thread Tom Kacvinsky


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 ptmb8a.pfb
ptmbi8r Times-BoldItalic TeXBase1Encoding ReEncodeFont 8r.enc ptmbi8a.pfb
ptmr8r Times-Roman TeXBase1Encoding ReEncodeFont 8r.enc ptmr8a.pfb
ptmri8r Times-Italic TeXBase1Encoding ReEncodeFont 8r.enc ptmri8a.pfb

So, assuming that Times-Roman is defined int he PFB file ptmr8a.pfb, this
font map entry would make dvips include the PFB file for Times-Roman.

Tom

On Fri, 29 Jun 2001, gijs van soest wrote:


 Hi,

 I have a problem that I fear is related to the eternal \usepackage{times}
 + dvips -Ppdf discussion; still, I can't find the solution in the
 archives. To the point:
 My document is typeset in Times (Roman, Bold, and Italic), with occasional
 use of Helvetica Bold. I make a ps file using

 $ dvips -Pgijspdf bell
 This is dvips(k) 5.86 Copyright 1999 Radical Eye Software (www.radicaleye.com)
 ' TeX output 2001.06.29:1820' - bell.ps
 tex.proalt-rule.protexc.pro8r.enctexps.pro. cmsy10.pfbcmr10.pfb
 msam10.pfbcmbsy10.pfbcmmib10.pfb[1]

 where config.gijspdf is an slightly modified version of config.pdf,
 commenting out the character shifting.

 The problem is that the times and helvetica fonts are not embedded in the
 ps file, while the cm and math fonts are. I need the fonts embedded,
 because the ps is going to be distilled to pdf, with all the fonts
 embedded as Type 1. The pdf now looks fine, but uses Windows font
 substitution, unsuitable for professional (book)printing.

 Apparently dvips does know how to include the .pfb's for the cmbsy, cmmib,
 msam, etc., but not the normal text. I tried to extend the list of font
 map files in config.pdf, but that did not work. I either misunderstand the
 problem (very possible) or I include the wrong files.
 Can anybody help me out?

 Cheers,

 Gijs


 From config.gijspdf:

 % This is for using BlueSky/AMS/YY Type 1 fonts. Change this for other
 % Type 1 fonts.

 p +psfonts.cmz
 p +cs.map
 %p +pdftex.map
 p +bakoma-extra.map
 p +bsr.map
 p +bsr-interpolated.map
 p +hoekwater.map
 p +adobe.map

 
 Gijs van Soest   ([EMAIL PROTECTED])

 Van Der Waals-Zeeman Institute  | Valckenierstr. 65
 University of Amsterdam | 1018 XE Amsterdam NL
 tel. + 31 20 525 5663 / fax + 31 20 525 5788

 URL www.randomlasers.com
 or  www.science.uva.nl/research/scm
 





Re: now I think this is a bug

2000-12-11 Thread Tom Kacvinsky

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 that last comment...

Tom

On Mon, 11 Dec 2000, Thomas Esser wrote:

  # kpsewhich -expand-var='$SELFAUTOLOC -- $SELFAUTODIR -- $SELFAUTOPARENT'
  /usr/local/teTeX/bin/i686-pc-linux-gnu --   /usr/local/teTeX/bin/i686-pc-linux -- 
/usr/local/teTeX/bin/i686-pc

 Looks very broken. This sould be impossible. Look at the kpathsea code
 (progname.c, I think). Must be a compiler bug.

  This glibc is the official update of RH to their 7.0 distro.  I have
  absolutely nothing on my system which is not official RH (except tetex).
 ...
  # gcc -v
  Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/2.96/specs
  gcc version 2.96 2731 (Red Hat Linux 7.0)

 And still: I think that your compiler is broken.

 Thomas





Re: re-installed, help

2000-11-03 Thread Tom Kacvinsky

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:
   
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 t1lib-error messages which indicate that the respective Type
   1 font could not be loaded. Since (AFAIK) t1lib can process all
   cm-outline fonts, I suspect it could be problem intorduced by font
   subsetting, but I'm not sure. Maybe this is not tetex-related at all.
   
  
  The PDF file is just fine, font wise.  I am beginning to suspect the problem has
  to do with xpdf and how it extracts the fonts for hand-off to t1lib.
  
  I only got the error messages for font IDs 3 and 4, but not for font ID 10.
  This was with xpdf 0.90 (I haven't yet upgraded to 0.91, but that upgrade was
  for security fixes, not font handling "bugs").
  
  I'll contact Derek about this...
  
  
  If the relevant subsetted fonts could be extracted into isolated Type
  1 files I could try to help finding the problem (Tom? Derek?)
 
 I tried viewing the PDF file (which Tom sent me) on my system, and it
 worked fine.  After emailing back and forth, it looks like Tom is using
 an older version of t1lib (0.9.1), so I'm guessing that's the problem,
 but I'm still waiting to hear back from him.
 

Ah yes, I started the compile, but had to leave for a going away party for one of
my co-workers...

When I got back to it, I had all sorts of compile errors because of freetype2
includes with freetype 1.3.1 libs.  After sorting that out, things are fine.
t1lib 1.0.1 resolves the problems...

 I seem to recall some of the t1lib bug fixes dealt with problems like
 this (?)
 
 In any case, I'd be happy to extract the fonts from the PDF file if
 upgrading to a newer t1lib doesn't fix the problem.
 


No need to do this; t1lib resolves the problems.

Thank you all!

Tom




Re: re-installed, help

2000-11-02 Thread Tom Kacvinsky

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, C. Michael McCallum wrote:

 
 Well, this always happens, and I'll be danged if I can
 figure out how to fix up my installation now that I've updated.
 
 First problem:  I can't remember the command to make all my
 fonts with mktexpk ... somewhere I know Thomas has given a script so you can
 generate all your fonts "allneeded" or whatever.
 
 Second problem:  I'm getting errors in xpdf about missing fonts
 after running through pdflatex.  It was working with my old setup,
 of course:
 
 merckx [161] 9xpdf hw-7.pdf
 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)
 
 
 for example, CM math doesn't show up, and \mathbf{..} doesn't either.
 
 I'm sorry if these questions are FAQs.. I searched and searched!
 
 Cheers,
 
 Mike
 




Re: re-installed, help

2000-11-02 Thread Tom Kacvinsky

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 t1lib-error messages which indicate that the respective Type
 1 font could not be loaded. Since (AFAIK) t1lib can process all
 cm-outline fonts, I suspect it could be problem intorduced by font
 subsetting, but I'm not sure. Maybe this is not tetex-related at all.
 

The PDF file is just fine, font wise.  I am beginning to suspect the problem has
to do with xpdf and how it extracts the fonts for hand-off to t1lib.

I only got the error messages for font IDs 3 and 4, but not for font ID 10.
This was with xpdf 0.90 (I haven't yet upgraded to 0.91, but that upgrade was
for security fixes, not font handling "bugs").

I'll contact Derek about this...

Tom




Re: RPMs for Suse?

2000-09-29 Thread Tom Kacvinsky

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 Martin at TUG 2000, and he strikes me as being very astute
at source code compiling, etc...

In that sense, I guess Debian is good, in this way: I have been told
that one can easily make a package from the compiled sources and then
install that.  Now, my source on this thinks everything package
building and/or compiling related is easy, but I don't think he knows
the extent of the teTeX packages and their dependencies, etc...

I have Debian installed on my PowerMac, and am slowly getting oriented
with how Debian package management works (when I can boot my box into
Linux).  So I cannot comment on the ease of Debian package building...

Anyway, my point is this: I assume that when one asks for a package,
its not because they are lazy and don't want to compile from source,
it is because they want to have better management of what is installed
on their boxes.

Signing off, and hoping I don't start a flame war.

Tom




Re: Can dvips support truetype font?

2000-04-24 Thread Tom Kacvinsky

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 written out.
Then, a new procedure (say, type42rf, instead of rf) is used to read
this information.  The reason being is that Type 1 fonts use a
"standard" measure of 1000 units per 1 point, whereas TrueType fonts
use a "standard" measure of 2048 units per 1 point.

Tom Rokicki, what say you?

Tom

On Mon, 24 Apr 2000, Sebastian Rahtz wrote:

 Mr. Wang Lei writes:
   Hi, I installed tetex on my RedHat/Sun Solaris and it works
   well. Using dvips and type1 fonts get good quality PS files.
   Now I have a problem, can dvips support truetype font?
 
 sadly, no. use pdftex, and then acrobat to generate a PS file...
 
 Sebastian
 




Re: dvips(k) state and maintainer

2000-01-20 Thread Tom Kacvinsky

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 subsetted) have the following
lines in it?

/Encoding 255 array
0 1 255 {1 index exch /.notdef put}

If it doesn't, it probably is a Fontographer generated font, which means that
the encoding in the original font looks like this:

/Encoding 255 array

256 assignments, including the necessary /.notdefs needed to fill out
the 256 slots

You can solve your problems either by (a) fixing the original font or
(b) getting the latest snapshot of tetex, which uses Han The Thanh's
writet1 module to handle font subsetting (instead of t1part).

Tom

def (or readonly def)
On Thu, 20 Jan 2000, Karsten Tinnefeld wrote:

 Who is the one who currently maintains dvips? I have some trouble with 
 partially encoded fonts with non-standard encoding and late postscript 
 interpreters in recent hp printers.
 
 unfortunately, I have no idea who is the current maintainer. ctan has 
 dvips versions up to 5.67, dvipsk to 5.78a, and 
 http://www.radicaleye.com/dvipsalpha.html talks of 5.83 as being 
 current. However, tetex 1.0.6 comes with 5.86.
 
 Below the description of the problem:
 I have written a short test text which uses a few characters of an 
 expert font. When running dvips on the resulting dvi file with partial 
 font encoding on, it shortens the definition of the Encoding vector to
 
 /Encoding 256 array
 dup 58 /ff put
 dup 63 /ffi put
 dup 64 /ffl put
 readonly def
 
 . Our postscript printers hp 2000n and clj 4050 complain and do not 
 print: "Error: typecheck; OffendingCommand: definefont". They are 
 right, since the postscript specs say "All unused posistions must
 be filled with the name .notdef"
 
 When inserting the following line after "... array", the error vanishs:
   0 1 255 {1 index exch /.notdef put} for
 
 Ideas or references? Thank you, greetings,
 



Re: dvips(k) state and maintainer

2000-01-20 Thread Tom Kacvinsky

That should be

/Encoding 256 array

Sorry about the mix up...

Tom

 
 /Encoding 255 array
 0 1 255 {1 index exch /.notdef put}