View Ghostscript Fonts?

  • Thread starter Thread starter John Corliss
  • Start date Start date
Anybody know of a freeware or way to do this?

These are Adobe Type 1 fonts. So you could view them with Adobe Type
Manager Light (ATM Light). This is freeware (registerware) by Adobe.
With Google you should find enough direct downloads, too.

BeAr
 
B. R. 'BeAr' Ederson said:
These are Adobe Type 1 fonts. So you could view them with Adobe Type
Manager Light (ATM Light). This is freeware (registerware) by Adobe.
With Google you should find enough direct downloads, too.

Sorry BeAr, I should have mentioned that I tried that and it didn't
work. Was unable to preview anything. And after doing that when I
tried to print a WordPerfect (6.1) document to a .PDF file, it locked
up the printer module. Luckily, I'd set a system restore point. I
uninstalled the ATM Lite and restored the computer, then was able to
print the document to .PDF. By the way, the link I found was directly
to an Adobe server and no registration was required to get the
program. However, I've lost the link at this point.
Still, the problem is that when I used a particular font (a
handwriting style one) and then printed it to .PDF, the document came
out in a totally unrelated font. Guess maybe I should look to see if
there are any more Ghostscript fonts out there.
 
John said:
Sorry BeAr, I should have mentioned that I tried that and it didn't
work. Was unable to preview anything. And after doing that when I
tried to print a WordPerfect (6.1) document to a .PDF file, it locked
up the printer module. Luckily, I'd set a system restore point. I
uninstalled the ATM Lite and restored the computer, then was able to
print the document to .PDF. By the way, the link I found was directly
to an Adobe server and no registration was required to get the
program. However, I've lost the link at this point.
Still, the problem is that when I used a particular font (a
handwriting style one) and then printed it to .PDF, the document came
out in a totally unrelated font. Guess maybe I should look to see if
there are any more Ghostscript fonts out there.


My suggestion is to try to *embed TrueType font* directly to PDF file,
rather than use font substitution and then embed matching Type 1
(PostScript) font to PDF file. Embedding TrueType fonts should be
possible with the most recent Ghostscript versions. But used Post-
Script printer driver also affects the results, so driver settings
should be also correct, when creating the intermediate PostScript
file.

This should help:
http://www.geocities.com/mobrien_12/pdfwin.htm

Also, some other information:
http://www.srcf.ucam.org/~rejc2/pdf/
http://www.geocities.com/mobrien_12/pdfwin.htm
 
Sauli said:
My suggestion is to try to *embed TrueType font* directly to PDF file,
rather than use font substitution and then embed matching Type 1
(PostScript) font to PDF file. Embedding TrueType fonts should be
possible with the most recent Ghostscript versions. But used Post-
Script printer driver also affects the results, so driver settings
should be also correct, when creating the intermediate PostScript
file.

This should help:
http://www.geocities.com/mobrien_12/pdfwin.htm

Also, some other information:
http://www.srcf.ucam.org/~rejc2/pdf/
http://www.geocities.com/mobrien_12/pdfwin.htm

Sauli,
Thanks for the links! I'm on my way....
 
My suggestion is to try to *embed TrueType font* directly to PDF file,
rather than use font substitution and then embed matching Type 1
(PostScript) font to PDF file.

You might also find this useful http://ttf2pt1.sourceforge.net/ .
This program allows you to convert your windows fonts so they can be
used in ghostscript. Otherwise what happens is the windows program
uses one font and ghostscript a substitution since it ghostscript does
not use ttf. This way they both will use the same. BTW you have to
edit Fontmap.GS too.

I have program on my site called fixes on the pspice tips page that
explains what to do since this is a problem I had on the wmf printer I
have in the tips. Printing to wmf used to mess up the fonts since it
would go font A to font B to font C when going from windows to
ghostscript to windows, :-(. Now it stays at font A :-).


--

Malcolm Reeves BSc CEng MIEE MIRSE, Full Circuit Ltd, Chippenham, UK
([email protected], (e-mail address removed) or (e-mail address removed)).
Design Service for Analogue/Digital H/W & S/W Railway Signalling and Power
electronics. More details plus freeware, Win95/98 DUN and Pspice tips, see:

http://www.fullcircuit.com or http://www.fullcircuit.co.uk

NEW - Desktop ToDo/Reminder program (free)
 
Sorry BeAr, I should have mentioned that I tried that and it didn't
work. Was unable to preview anything. And after doing that when I
tried to print a WordPerfect (6.1) document to a .PDF file, it locked
up the printer module. Luckily, I'd set a system restore point. I
uninstalled the ATM Lite and restored the computer, then was able to
print the document to .PDF.

You seem most unfortunate. :-( Everything works fine here. I don't use
WordPerfect, though. That's why I can't say anything about possible
conflicts between WP and GS.

One thing to keep in mind is: There have been lots of incompatibilities
between MS Win and ATM(light) before. I remember a font cache overflow. -
You had to delete some PostScript (/GhostScript) fonts to solve this
problem. Another error was caused by the loading order of font drivers.
(Solved somewhere within the latest Service Packs for Win2k / WinXP.)

So maybe you want to check if you had the *latest* ATMlight installed
and all ServicePacks and fixes for your OS.

But according your previous experiences you most possibly won't test
ATMlight further. I most possibly wouldn't want to either after your
experiences... :-(
Still, the problem is that when I used a particular font (a
handwriting style one) and then printed it to .PDF, the document came
out in a totally unrelated font. Guess maybe I should look to see if
there are any more Ghostscript fonts out there.

Hm. If this isn't a font from the standard GS package, the reason you
ran into problems could be a missing entry within the font substitution
table, which is part of ATMlight. Another cause could be a missing entry
within the GS fontmap (as Malcolm already pointed out) or a wrong font
path given to Redmon (or which redirector you possibly use.)

Sorry, that I couldn't be of more help. Good luck when looking for
a solution!

BeAr
 
Malcolm said:
You might also find this useful http://ttf2pt1.sourceforge.net/ .
This program allows you to convert your windows fonts so they can be
used in ghostscript. Otherwise what happens is the windows program
uses one font and ghostscript a substitution since it ghostscript does
not use ttf. This way they both will use the same. BTW you have to
edit Fontmap.GS too.

I have program on my site called fixes on the pspice tips page that
explains what to do since this is a problem I had on the wmf printer I
have in the tips. Printing to wmf used to mess up the fonts since it
would go font A to font B to font C when going from windows to
ghostscript to windows, :-(. Now it stays at font A :-).

Thanks Malcolm. I've downloaded it and will check it out later. At
this point, I managed to get my project done with slightly less
satisfactory results, but done nonetheless.
 
Back
Top