Hello all,

Question:

When I use a font in PGS and use an extended character, what steps are
required to make all characters used with this font appear on paper as it is
on screen when using postscript output through TP7 and ghostscript?

The reason I ask is, I'm using Vagrounded PS font and I entered guillemots
(alt-9 and alt-0), and on screen they appear as they should, but when I
print to postscript through TP, I get a totally different pair of characters
printed on paper where the guillemots should be. This also affects smart
quotes and dashes. It actually prints nothing in place of the smart quotes
and dashes.

Thanks for any help...

Kind regards
--
Peter Coates
Waterloo, Ontario
*CANADA*
--
*A3000 OS3.1 Cybervision Warpengine 040 40 Mb Ram*

On 30-Jun-00, P. Coates wrote:

>When I use a font in PGS and use an extended character, what
>steps are required to make all characters used with this font
>appear on paper as it is on screen when using postscript output
>through TP7 and ghostscript?

>The reason I ask is, I'm using Vagrounded PS font and I entered
>guillemots (alt-9 and alt-0), and on screen they appear as they
>should, but when I print to postscript through TP, I get a totally
>different pair of characters printed on paper where the guillemots
>should be.

I just tried to duplicate your problem, using PageStream 4.0r7, and
a Type 1 PostScript Vagrounded light font (VAGR11.PFB, from Ares
Software) from the Super Fonts CD-ROM. This font used 256-array
encoding. A short text was made up with left and right guillemot
characters generated both by the alt/9, alt/0 system and by
ctrl/c << and ctrl/c >>. The PageStream display showed the
characters properly formed.

"Printed" to a file in RAM: from PageStream with "no PPD selected"
the test file displayed normally via HWG Post. Printing the test
file using the GhostPrint_LJET2P module in GhostScript 5.1, the
guillemot characters printed properly.

I tried adding "smart quotes" and a "smart dash", and they came out
properly displayed via HWG Post and printed via GhostPrint.

There are these possibilities:

1. Your Vagrounded font had a bitmap screen-font which included
the proper characters, but the actual pfb vector font which
was downloaded with the document did not. This could be revealed by
magnifying the screen display past the point where the screen-
font is used. If the guillemots disappear, that was the problem.

2. You were using a PPD which thought Vagrounded was a resident font
in the target printer, so there was no font downloaded with the
document. GhostScript or Turboprint substituted some other font which
did not have the requisite characters at the specified positions.
"Print" from PageStream to a file in RAM: and examine the file to
see if a Vagrounded font was in fact downloaded.

3. TurboPrint interfered with the font download. Try getting TP out
of the loop and see if the lost characters reappear. (This assumes
it's possible to drive your printer directly. With some of the new
printers, of course, TP is the only driver currently available.)

--Geoff

--
ggass@teleport.com Geoffrey A. Gass Foulecourt Press
Also at this address: T. Bain Stokes Fignewton Frogberry

On 30-Jun-00, P. Coates wrote:

>When I use a font in PGS and use an extended character, what
>steps are required to make all characters used with this font
>appear on paper as it is on screen when using postscript output
>through TP7 and ghostscript?

>The reason I ask is, I'm using Vagrounded PS font and I entered
>guillemots (alt-9 and alt-0), and on screen they appear as they
>should, but when I print to postscript through TP, I get a totally
>different pair of characters printed on paper where the guillemots
>should be.

CANCEL EVERYTHING I just wrote in answer to this message. I just
double-checked my PostScript files, and they had a Triumvirate,
not a Vagrounded download. Although my PageStream palette showed
that I was using Vagrounded, the program was actually substituting
Triumvirate. After 3 more updates of the font file, it suddenly
started actually using the Vagrounded font, and the guillemot
characters could not be displayed or printed. Although there is
one guillemot character available (Ctrl/c Y"), the normal ways
of obtaining them and smart quotes do not work with this particular
font. It would have to be overhauled in TypeSmith to respond
properly to the standard keyboard input for thre extended character
set.

Sorry I spoke up so soon.

--Geoff

--
ggass@teleport.com Geoffrey A. Gass Foulecourt Press

Hello Geoffrey

On 30-Jun-00, Geoffrey Gass wrote:
> On 30-Jun-00, P. Coates wrote:

>> When I use a font in PGS and use an extended character, what
>> steps are required to make all characters used with this font
>> appear on paper as it is on screen when using postscript output
>> through TP7 and ghostscript?

>> The reason I ask is, I'm using Vagrounded PS font and I entered
>> guillemots (alt-9 and alt-0), and on screen they appear as they
>> should, but when I print to postscript through TP, I get a totally
>> different pair of characters printed on paper where the guillemots
>> should be.

> CANCEL EVERYTHING I just wrote in answer to this message. I just
> double-checked my PostScript files, and they had a Triumvirate,
> not a Vagrounded download. Although my PageStream palette showed
> that I was using Vagrounded, the program was actually substituting
> Triumvirate. After 3 more updates of the font file, it suddenly
> started actually using the Vagrounded font, and the guillemot
> characters could not be displayed or printed. Although there is
> one guillemot character available (Ctrl/c Y"), the normal ways
> of obtaining them and smart quotes do not work with this particular
> font. It would have to be overhauled in TypeSmith to respond
> properly to the standard keyboard input for thre extended character
> set.

> Sorry I spoke up so soon.

> --Geoff

I just tried some other postscript fonts, and they behave the same way. One
even went so far as to not even have a regular quote character (ascii 34)! I
got some of these fonts from a CD collection of fonts and clipart for dtp
use. But I can't see how these fonts are of much use when you really can
only use them for alpha-numeric characters with any reliability.

I tried also using a couple of old CG Fonts and they printed postscript
okay, without any strange or missing characters. I guess most of my
postscript fonts really bite!

Regards
--
Peter Coates
Waterloo, Ontario
*CANADA*
--
*A3000 OS3.1 Cybervision Warpengine 040 40 Mb Ram*