From: Alan W. I. <ir...@be...> - 2004-01-26 20:51:01
|
On 2004-01-26 19:33-0000 Jo=E3o Cardoso wrote: > On Monday 26 January 2004 18:36, Alan W. Irwin wrote: > | On 2004-01-26 17:29-0000 Jo=E3o Cardoso wrote: > | > | For LBP I recently discovered the solution to the "horrible > | > | characters on screen" problem with ps2pdf. In the dvips step > | > | specify the -Ppdf -G options, and suddenly ps2pdf results look > | > | good on screen. > | > > | > The problem is that the generated dvi file ask for "ec" fonts, and > | > bitmap versions of them are generated and included in the ps file > | > (look at the .ps file: > | > ... > | > The following cm font will be type-1, scalable > | > %!PS-AdobeFont-1.1: CMSY7 1.0 > ^^^^^ > | > ... > | > The following ec font will be bitmap > | > %DVIPSBitmapFont: Fb ectt1095 > ^^^ > | > > | > The solution would be to use type-1 fonts from the very beginning, > | > or generate a latex file instead of a dvi, and then change its > | > preamble (I use \usepackage{ae,aecompl}) and then use jadetex and > | > "dvips -Pcmz") > | > | For my Debian stable system, I have the bluesky fonts (type 1 form of > | the Computer Modern fonts) installed. > > You have not read what I wrote. Sorry, but I did not completely understand what you said before because statements like "The following cm font will be type-1, scalable" do not appear in the RC1 version of the postscript documentation. However, I did find the following which I think agrees with what you said. %DVIPSBitmapFont: Fb ectt1095 10.95 31 %DVIPSBitmapFont: Fg ectt0800 8 6 %DVIPSBitmapFont: Fh ectt0800 5 2 %DVIPSBitmapFont: Fi ecit1000 10 31 %DVIPSBitmapFont: Fj ecit0900 9 33 %DVIPSBitmapFont: Fk tcrm0800 8 1 %DVIPSBitmapFont: Fl ecrm0600 6 9 %DVIPSBitmapFont: Fm ecrm0900 9 49 %DVIPSBitmapFont: Fn ecsx1440 14.4 54 %DVIPSBitmapFont: Fo ectt0900 9 91 %DVIPSBitmapFont: Fp ecti1000 10 58 %DVIPSBitmapFont: Fq ecbx1000 10 41 %DVIPSBitmapFont: Fr ecrm0800 8 64 %DVIPSBitmapFont: Fs tcrm1000 10 1 %DVIPSBitmapFont: Ft ecrm1000 10 102 %DVIPSBitmapFont: Fu ecsx1000 10 31 %DVIPSBitmapFont: Fv ecsx1200 12 64 %DVIPSBitmapFont: Fw ecsx1728 17.28 20 %DVIPSBitmapFont: Fx ecsx2074 20.74 56 %DVIPSBitmapFont: Fy ecsx2488 24.88 27 For the corresponding ps2pdf-generated pdf document there are all sorts of type 3 fonts, but the names don't seem to correspond to any of the above so it is confusing. For the original pdf form of our documentation, the fonts are all type 1 (and computer modern) which is why it looks good on screen. Thus, I believe I am in general agreement with Joao, although a lot of the specifics here on my system don't match what he said. In sum, you have to make sure that acroread reports only type 1 fonts. That is definitely the case for our current pdf documentation, but not the case if you attempt to produce it with ps2pdf from our current dvi file. My fundamental point continues to be ps2pdf results look good if you arrang= e to use only pure computer modern fonts for your dvi file. Also, I just checked in the LBP case (with ps2pdf-generated results with type 1 computer-modern fonts) that word-searching works. So it is possible linkin= g would work as well once we sort out the font difficulties. Alan __________________________ Alan W. Irwin email: ir...@be... phone: 250-727-2902 Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the PLplot scientific plotting software package (plplot.org), the Yorick front-end to PLplot (yplot.sf.net), the Loads of Linux Links project (loll.sf.net), and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ |