Hi,

I have now got the TTF fonts working properly within PageStream - thanks
a lot for your help.

I do though experience some problems when printing using the TTF fonts.
If I use the PostScript driver and output to my HP 6MP PostScript printer,
PageStream freezes (sometimes the printer simply outputs a lot of crap
after some time). However, if I use the non-PostScript driver I experience
none of these problems and the TTF fonts prints properly.

Can anybody confirm this problems I have using TTF fonts and PostScript
printing?

Uffe Holst

On 17-Jul-00, Uffe Holst wrote:

> I do though experience some problems when printing using the TTF
> fonts. If I use the PostScript driver and output to my HP 6MP
> PostScript printer, PageStream freezes (sometimes the printer simply
> outputs a lot of crap after some time). However, if I use the
> non-PostScript driver I experience none of these problems and the TTF
> fonts prints properly.
>
> Can anybody confirm this problems I have using TTF fonts and
> PostScript printing?

PageStream has to make a Type 1 version of the font for the printer.
While it is doing this, the printer times out.

The Type 1 font is saved on disk, so the next time you print it will be
OK.

You get the same problems if you install Compugraphic fonts.

Regards
--
Don Cox
doncox@enterprise.net

On 17-Jul-00, Uffe Holst wrote:

>I do though experience some problems when printing using the TTF fonts.
>If I use the PostScript driver and output to my HP 6MP PostScript
>printer, PageStream freezes (sometimes the printer simply outputs
>a lot of crap after some time). However, if I use the non-PostScript
>driver I experience none of these problems and the TTF fonts prints
>properly.

>Can anybody confirm this problem I have using TTF fonts and PostScript
>printing?

I have run into a similar problem with PostScript output even without
TTF fonts. If I go immediately from telecomm operations (YAM, iBrowse)
to PageStream4, asking for PostScript output to a disk file (RAM
may result in a hangup: the little clock shows up, the CPU is very
busy (all-black screen in the screensaver) for five minutes or
longer, but nothing happens.

If I reboot and repeat the operation with a "clean" machine, no
problem. With a TTF font, the PostScript Type 3 conversion takes
only a few seconds, and HWG Post and GhostScript have no problem
handling the resulting file.

I suspect our old friend MUI has something to do with this problem.
Try starting with a newly-rebooted machine and send the PostScript
output to RAM: where it can be examined using PageLiner. If it
looks OK (any TTF font will be rendered as a Type 3 font with
clear line and curve instructions for each character), copy the file
to PAR: and see if the printer likes it.

--Geoff

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

Uffe Holst schrieb in einer persoenlichen Nachricht ueber
"[PageStreamSupport] More TTF problems":
>
> Hi,
>
> I have now got the TTF fonts working properly within PageStream - thanks
> a lot for your help.
>
> I do though experience some problems when printing using the TTF fonts.
> If I use the PostScript driver and output to my HP 6MP PostScript
> printer,
> PageStream freezes (sometimes the printer simply outputs a lot of crap
> after some time). However, if I use the non-PostScript driver I
> experience
> none of these problems and the TTF fonts prints properly.
>
> Can anybody confirm this problems I have using TTF fonts and PostScript
> printing?

Yes, its a long standing, very annoying bug since 3.x. I mentioned
this bug several times, but no fix.

---
with best regards

Klaus Gillarek klgill@gmx.de
Klaus.Gillarek@gfk.de

In a message of 17-Jul-00 Klaus Gillarek wrote:

>> Can anybody confirm this problems I have using TTF fonts and PostScript
>> printing?

> Yes, its a long standing, very annoying bug since 3.x. I mentioned
> this bug several times, but no fix.

Hmmm... so it is according to you not exactly like Don says. I have tried
experimenting a bit with, alas with the same results as previously.

Don also claimed that the fonts would be save to disk to be used the next
time, but as far as I can see using SnoopDOS, PageStream is doing nothing
but read the #?.ttf files -- nothing new is written.

So the conclusion must be: To use TTF fonts one must not use the PostScript
driver...

But thanks for the help even though it didn't help a lot ))

Uffe Holst

On 17-Jul-00 16:38:20 uhc@post6.tele.dk Uffe Holst wrote:

>In a message of 17-Jul-00 Klaus Gillarek wrote:

> >> Can anybody confirm this problems I have using TTF fonts and
> >> PostScript printing?

> > Yes, its a long standing, very annoying bug since 3.x. I mentioned
> > this bug several times, but no fix.

>Hmmm... so it is according to you not exactly like Don says. I have
>tried experimenting a bit with, alas with the same results as
>previously.

>Don also claimed that the fonts would be save to disk to be used the
>next time, but as far as I can see using SnoopDOS, PageStream is doing
>nothing but read the #?.ttf files -- nothing new is written.

>So the conclusion must be: To use TTF fonts one must not use the
>PostScript driver...

>But thanks for the help even though it didn't help a lot ))

If I remember correctly, when PageStream is outputting to postscript
using CG fonts, it will convert the CG font to postscript, saving the
postscript version to disk as well as including it in the postscript
output. When using TT fonts to postscript, it also tries to convert
those to postscript and include them in the output, but it *doesn't*
save these to disk.

I use a print-spooler called PrintManager (frequently updated on
AmiNET), which has the option of holding the postscript output until a
later time, instead of sending it straight out to the printer. This
allows me to, among other things, look over the postscript files, to see
what is going into them. I have set PM to send these files to my VMEM
partition, where I have nothing that I absolutely need to keep.

If you have a setup like this, you might try sending out a postscript
file, using TT fonts, to disk and look at the result, to see if the
fonts are being included in the output or not. If they are, you might
try using PrintManager also, or try setting the timeout on your printer
as high as you can without generating an error condition (I ran into
this problem with my HP4MP).

--
William F. Maddock ICQ:14668944 http://www.icon-stl.net/~wmaddock
Time: 17-Jul-0 19:16:10 CDT Jesus Saves mailto:wmaddock@icon-stl.net
St. Louis, Missouri, USA ftp://ftp.icon-stl.net/users/wmaddock
Team AMIGA Written using THOR 2.6a Registered User Number 1621
--
Psalms 31:21 Praise be to the LORD, for he showed his wonderful love to
me when I was in a besieged city.

On or about 03:38 PM 7/17/00 a carrier pigeon from Uffe Holst delivered:

>So the conclusion must be: To use TTF fonts one must not use the PostScript
>driver...

Can you generate PostScript to a disk-file, and then copy the
result to the printer port later (by which time the conversions are done?)

--
> ============================================================== <
> wlfraed@ix.netcom.com | Wulfraed Dennis Lee Bieber KD6MOG <
> wulfraed@dm.net | Bestiaria Support Staff <
> ============================================================== <
> Bestiaria Home Page:http://www.beastie.dm.net/ <
> Home Page:http://www.dm.net/~wulfraed/ <

Uffe Holst schrieb in einer persoenlichen Nachricht ueber
"[PageStreamSupport] Re: More TTF problems":
>
> In a message of 17-Jul-00 Klaus Gillarek wrote:
>
> >> Can anybody confirm this problems I have using TTF fonts and
> >> PostScript
> >> printing?
>
> > Yes, its a long standing, very annoying bug since 3.x. I mentioned
> > this bug several times, but no fix.
>
> Hmmm... so it is according to you not exactly like Don says. I have
> tried
> experimenting a bit with, alas with the same results as previously.
>
> Don also claimed that the fonts would be save to disk to be used the
> next
> time, but as far as I can see using SnoopDOS, PageStream is doing
> nothing
> but read the #?.ttf files -- nothing new is written.

Once i saved the Postscript output to disk. I ended up with interupting
at 180MB output. There was only garbage in the file.

There is only one "workaround". If you printed one page successfully,
leave PGS and start it again. Print the next.

> So the conclusion must be: To use TTF fonts one must not use the
> PostScript
> driver...

There is more than one reason to print Postscript. And the ttf-plugin
costs money and it is nearly unusable.

---
with best regards

Klaus Gillarek klgill@gmx.de
Klaus.Gillarek@gfk.de

hmmm...

I was holding off on this letting those who are more eloquent speak and
explain, but this thread seems to indicate that TTF fonts won't print to
PostScript from PageStream and this is not true.

As a test I looked for a font in my setup that was ttf, opened a new
document, typed some frameless text, set the font from my default (Times)
to the ttf (Goblin) and printed as PostScript (my normal mode) to my HP4p
PS printer. Although it did take the printer about three minutes to render
the page (Goblins is one of those "clip art" fonts) it did so and the
printed page faithfully matches what I saw on screen.

I *have* seen a problem with PostScript printing involving timeout with
large documents because PageStream sends the postscript header to the
printer and *then* sees about finding and flowing the text for the page(s)
to be printed. IIRC this can be averted by selecting "Print Current Page"
in the requestor, or by printing PS to disk and copying to printer.
However, the latter can generate some huge files depending on your
graphics, etc.

As a matter of fact, this timeout problem caused me to break up a document
into four sub-documents because it had gotten so large that I couldn't
print PS anymore (single pages at a time aren't reasonable for 200+ page
documents and the other workaround is a pain in the *ss).
Regards
--
:: Tim Doty
 
drakki@rollanet.org
tdoty@umr.edu
http://www.rollanet.org/~drakki
pgp public key available on request

On 18-Jul-00, Timothy Doty wrote:

>IIRC this can be averted by selecting "Print Current Page"
>in the requestor, or by printing PS to disk and copying to printer.
>However, the latter can generate some huge files depending on your
>graphics, etc.

A recent one-page PS document had a large AI-EPS graphic, three non-
standard fonts, and a little 1100x500 pixel bitmap (the Special
Olympics logo). The PostScript file was 4 Megs. Kicking the bitmap
back to BME for tracing as a DR2D image brought the whole file down
to less than 500k. PostScript does /not/ do bitmaps efficiently: they
should be converted when possible to some more compact format.

--Geoff

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

On 18-Jul-00, Timothy Doty wrote:

> I *have* seen a problem with PostScript printing involving timeout
> with large documents because PageStream sends the postscript header to
> the printer and *then* sees about finding and flowing the text for the
> page(s) to be printed. IIRC this can be averted by selecting "Print
> Current Page" in the requestor, or by printing PS to disk and copying
> to printer. However, the latter can generate some huge files depending
> on your graphics, etc.
>
> As a matter of fact, this timeout problem caused me to break up a
> document into four sub-documents because it had gotten so large that I
> couldn't print PS anymore (single pages at a time aren't reasonable
> for 200+ page documents and the other workaround is a pain in the
> *ss). Regards

I find 25-30 pages at a time is the limit. It is somewhat annoying. It
would be better if PGS didn't contact the printer until it was ready to
send.

This applies both to long documents and to the construction of Type 1
fonts.

Regards
--
Don Cox
doncox@enterprise.net

On 18-Jul-00,* Timothy Doty*, of Planet Eros, wrote these Wise Words:

> As a matter of fact, this timeout problem caused me to break up a
> document into four sub-documents because it had gotten so large that
> I couldn't print PS anymore (single pages at a time aren't
> reasonable for 200+ page documents and the other workaround is a
> pain in the *ss).

I agree totally! I have a songbook I have created over the years...
comes in at about 230 pages. I have never been able to print
it on PageStream 3.x, although, IIRC, I could print it on the
old PageStream 2.22... where I started it and got up to about
page 200. I had been hoping to be able to double side the pages
with that nearly cool concept of print odd/print even pages.
However, in practice, this has never happened. When I tell
PGS3 to print, it gives me maybe 20 pages max, then starts
sending stuff to my printer which begins flashing the "FLUSHING
BUFFER" on a regular basis every time PGS sends a new page over.
Basically my printing comes to a grinding halt...

I have never been able to successfully use that feature I had
asked for ages ago. I just assumed it was a problem with MY
printer... which you can see below...

I also assumed I have a computer problem because I have NEVER
been able to print to the PostScript printer via the native
Amiga port... it was only when I got the MFC III that I was
able to print to the Lexmark.

Gil

--
~~~~~~~~~~~~~~ Gil Knutson's Pride and Joy ~~~~~~~~~~~~~~~
gknutson@uniserve.com - OS3.5 - Sardis, BC, Canada
A3000/30/2+16 RAM + 240 meg Quantum + 1.06 gig Seagate + ZIP Drive
MFCardIII+GVC 56k Speakerphone+Lexmark 4039 10R w/16meg
THOR2.6, MUI3.8, MWB, Voyager3, AmIRC 2.0, AmFTP 1.65 (all reg)
~~~~~~~~~~~ The Amiga Shall Inherit the Earth ~~~~~~~~~~~~

One tequila, two tequila, three tequila, floor.

Stuff below is possibly useless... : )

.

In a message of 20-Jul-00 Gil Knutson wrote:

> I also assumed I have a computer problem because I have NEVER
> been able to print to the PostScript printer via the native
> Amiga port... it was only when I got the MFC III that I was
> able to print to the Lexmark.

Funny, I haven't had too much success using the port on my GVP IOExtender
with my HP 6MP. And using the internal port naturally slows down the whole
computer when printing. Hmmmm... perhaps I should try the one om my
Ariadne.

Uffe Holst

Hiya, on Thu, 20 Jul 2000 09:28:57 +0200,
Uffe Holst wrote about *"[PageStreamSupport] Re: More TTF problems".*

> In a message of 20-Jul-00 Gil Knutson wrote:

> > I also assumed I have a computer problem because I have NEVER
> > been able to print to the PostScript printer via the native
> > Amiga port... it was only when I got the MFC III that I was
> > able to print to the Lexmark.

> Funny, I haven't had too much success using the port on my GVP IOExtender
> with my HP 6MP. And using the internal port naturally slows down the whole
> computer when printing. Hmmmm... perhaps I should try the one om my
> Ariadne.

I had problems trying to print to Postscript on my HP6MP using the IoBlix
Parallel Exrender. Went back to the old PAR: port for that, but my Canon
BJC600 works frine from it. It's great to see my miggy printing from 2
applications, on 2 printers /simultaneously/ ;))

--

Russell Butler Amiga A1200, 32mhz '040, 32mb RAM, 1.2 gig HD
wurzel@itl.net Member, Team AMIGA The Amiga lives on!
wurzel@psilink.co.je Past President, Jersey Junior Chamber (JCI)
ICQ 35310100 Page me on http://www.mirabilis.com/35310100

Hello Gil

On 19-Jul-00, you wrote:

> page 200. I had been hoping to be able to double side the pages
> with that nearly cool concept of print odd/print even pages.
> However, in practice, this has never happened. When I tell
> PGS3 to print, it gives me maybe 20 pages max, then starts

Have you tried printing to a PS file? If you have enough hard drive space
for the output this can work. Select all, even, print to file, copy file to
par:, reload paper, repeat with odd pages.

Output is then in proper order. You have to watch the second printing
though: especially with lighter weight papers (I normally only use 24# or
heavier) as they may fail to feed properly the second time. However,
judicious watching of the printing can help keep such errors from becoming
long printing run errors. I have managed at times to keep it isolated to
the first page of an error and then selecting "print current page" can fill
in the gap.

Regards
--
:: Tim Doty
 
drakki@rollanet.org
tdoty@umr.edu
http://www.rollanet.org/~drakki
pgp public key available on request

On 21-Jul-00,* Timothy Doty*, of Planet Eros, wrote these Wise Words:

> Have you tried printing to a PS file?

No...

> If you have enough hard drive
> space for the output this can work. Select all, even, print to file,
> copy file to par:, reload paper, repeat with odd pages.

I would... but the file alone is about 1.2megs!!! I fear for
the final size of that printout document... : )))

> Output is then in proper order. You have to watch the second
> printing though: especially with lighter weight papers (I normally
> only use 24# or heavier)

I am using 20 lb....

> as they may fail to feed properly the second time.

I run across this at times... really screws things up.
(I have "double sided" a lot, but done it manually... print
the one side, take it out, turn it over and print the other
side... one page out, and it really screws things up!!!!)

> However, judicious watching of the printing can help
> keep such errors from becoming long printing run errors.

Don't we know them!!!

> I have
> managed at times to keep it isolated to the first page of an error
> and then selecting "print current page" can fill in the gap.

You are lucky there!!!

Gil
--
~~~~~~~~~~~~~~ Gil Knutson's Pride and Joy ~~~~~~~~~~~~~~~
gknutson@uniserve.com - OS3.5 - Sardis, BC, Canada
A3000/30/2+16 RAM + 240 meg Quantum + 1.06 gig Seagate + ZIP Drive
MFCardIII+GVC 56k Speakerphone+Lexmark 4039 10R w/16meg
THOR2.6, MUI3.8, MWB, Voyager3, AmIRC 2.0, AmFTP 1.65 (all reg)
~~~~~~~~~~~ The Amiga Shall Inherit the Earth ~~~~~~~~~~~~

Experience is something you don't get until just after you need it.

Stuff below is possibly useless... : )

.