PageStream 4.1.4.0:

- Printing thumbnails: preference printer does not print page borders, page numbers and page shadows. (I am using Turboprint)

- Printing thumbnails: PostScript printer prints page borders and numbers at the wrong place. Page thumbnails are right. (I am using Turboprint and Ghostscript)

- Printing PS: some characters, like "strange" russian characters are not printed, their position is blank.
Is it a Ghostscript problem?
(Since I do not own a true PS printer, I have to use Turboprint + Ghostscript to obtain 32 bit color printings)
The same file exported as pdf and printed externally by Ghostscript seems to be all right.

- Filename does not appear in article information.

- Text-frame FX: set margins to a two column text frame. Modfiing column spacing resets margins to 0.

- Text-frame FX: place, for example, a rectangle and set it as a text-frame. FX button on the bar is not available.

- Eyedropper (text) does not load text attributes in not filled (transparent) columns.

- Find a word into an article flowed over two o more pages: if the requested word is found in page 2, the page-back arrow looks like disabled, but it works. Page number shows a "1" overprinted to a "2".

- ILUS files: importing an ILUS file and setting it as "leave external" makes impossible to select it by mouse (only by TAB key). This not happens for all files. May it depend by the type of objects included in ILUS file?

- copy/paste: select two or more columns filled of text. Copy them and then paste them. Columns frame is correctly pasted, but many text contained are surely lost.

- Exporting PDF: no advertisment for file overwriting. No progress bar or message are shown during writing.

- text wrapping: place a picture over a text and set the text to wrap around the picture, in example, 1 cm (about half of inch) vertical and 1 cm vertical. Now rotate the picture of about 10 degrees. The spacing set is no more respected on the top and on the bottom of the picture.

... and please correct my English mistakes too ))

Regards
Giovanni Bianchessi

Hi,

On Sunday 13 October 2002 12:47, Giovanni Bianchessi wrote:
> PageStream 4.1.4.0:
[snip]
>
> - Printing PS: some characters, like "strange" russian characters are not
> printed, their position is blank. Is it a Ghostscript problem?
> (Since I do not own a true PS printer, I have to use Turboprint +
> Ghostscript to obtain 32 bit color printings) The same file exported as
> pdf and printed externally by Ghostscript seems to be all right.

PS is limited to a 256 character set -- if you use a non-postscript font it
may very well have characters that lie outside of the postscript mapping
(such as "strange" russian characters). These are then not printed. If it
works using pdf exporting then that function would appear to be doing some
more intelligent font remapping.

[snip]
>
> - ILUS files: importing an ILUS file and setting it as "leave external"
> makes impossible to select it by mouse (only by TAB key). This not
> happens for all files. May it depend by the type of objects included in
> ILUS file?

Hmmm... I never did figure out why some ILUS files (generated in PGS) would
become unselectable (I usually did select all then unselect the rest).
Might well be related? (I did send a samples to Deron).

[snip]
> - text wrapping: place a picture over a text and set the text to wrap
> around the picture, in example, 1 cm (about half of inch) vertical and 1
> cm vertical. Now rotate the picture of about 10 degrees. The spacing set
> is no more respected on the top and on the bottom of the picture.

I would add that using the text offset inside of a text frame gets lost
when, for example, resizing the frame.

Tim Doty

And while on the subject of printing to the PS: device via
TurboPrint.....
I use this almost exclusively when printing appraisals containing
pictures. Pretty good output. However, I do have one problem using the
Black Chancery font that I'm almost embarrassed to speak out on. When
printing this font the letter come out cryptically scrambled to some
extent - one letter off. For instance, "come to the show" would be
printed as "dpnf up uif tipx". I get around this by simply converting
the text to an object prior to printing and all works well. However, I
strongly suspect this is not the way printing is supposed to work,
so..... Anyone have a clue on a fix? Font mapping problem. This is with
PgS Amiga 4whateverthelatestversionis.

> On Sunday 13 October 2002 12:47, Giovanni Bianchessi wrote: PageStream
4.1.4.0:
> [snip]
> >
> > - Printing PS: some characters, like "strange" russian characters
are
> > not printed, their position is blank. Is it a Ghostscript problem?
> > (Since I do not own a true PS printer, I have to use Turboprint +
> > Ghostscript to obtain 32 bit color printings) The same file exported

> > as pdf and printed externally by Ghostscript seems to be all right.
>
> PS is limited to a 256 character set -- if you use a
> non-postscript font it may very well have characters that lie outside
of the
> postscript mapping (such as "strange" russian characters). These are
then not
> printed. If it works using pdf exporting then that function would
appear to
> be doing some more intelligent font remapping.

It must be bring out the weird bug week here at PageStream central

Do you know what font format the font is in? Is it Type1 or CG or
TrueType??? The creation of the postscript downloadable would be the most
likely problem. If you could print the word "hello" in Black Chancery to
disk with the postscript driver and email it to me at
support@grasshopperllc.com I'll take a look at it.

>And while on the subject of printing to the PS: device via
>TurboPrint.....
>I use this almost exclusively when printing appraisals containing
>pictures. Pretty good output. However, I do have one problem using the
>Black Chancery font that I'm almost embarrassed to speak out on. When
>printing this font the letter come out cryptically scrambled to some
>extent - one letter off. For instance, "come to the show" would be
>printed as "dpnf up uif tipx". I get around this by simply converting
>the text to an object prior to printing and all works well. However, I
>strongly suspect this is not the way printing is supposed to work,
>so..... Anyone have a clue on a fix? Font mapping problem. This is with
>PgS Amiga 4whateverthelatestversionis.

Deron Kazmaier - support@grasshopperllc.com
Grasshopper LLC Publishing -http://www.grasshopperllc.com
PageStream DTP for Amiga, Macintosh, and Windows

On 14-Oct-02, Jon Peterson wrote:
> And while on the subject of printing to the PS: device via
> TurboPrint.....
> I use this almost exclusively when printing appraisals containing
> pictures. Pretty good output. However, I do have one problem using the
> Black Chancery font that I'm almost embarrassed to speak out on. When
> printing this font the letter come out cryptically scrambled to some
> extent - one letter off. For instance, "come to the show" would be
> printed as "dpnf up uif tipx".

That was one of the first fonts to be released as a Public Domain (or
possibly Shareware) Postscript font. Many of those early fonts were
originally Type 3, and funny things happened in the conversion to Type
1.

I suggest loading it, with its AFM, into Typesmith and resaving both the
PFM and AFM.

Regards
--
Don Cox
doncox@enterprise.net

On 14-Oct-02 02:54:35 doncox@enterprise.net Don Cox wrote:

>On 14-Oct-02, Jon Peterson wrote:

>> And while on the subject of printing to the PS: device via
>> TurboPrint.....

>> I use this almost exclusively when printing appraisals containing
>> pictures. Pretty good output. However, I do have one problem using
>> the Black Chancery font that I'm almost embarrassed to speak out on.
>> When printing this font the letter come out cryptically scrambled to
>> some extent - one letter off. For instance, "come to the show" would
>> be printed as "dpnf up uif tipx".

>That was one of the first fonts to be released as a Public Domain (or
>possibly Shareware) Postscript font. Many of those early fonts were
>originally Type 3, and funny things happened in the conversion to Type
>1.

>I suggest loading it, with its AFM, into Typesmith and resaving both
>the PFM and AFM.

Make that PFB and AFM. ='D

--
William F. Maddock Jesus Saves http://www.icon-stl.net/~wmaddock
Team AMIGA Written using THOR 2.6a Registered User Number 1621

http://www.icon-stl.net/~wmaddock/Help-TheWorldHasBeenInvaded.txt

Salvation is by Grace alone, through faith alone in Christ alone
Leadership without personal commitment to an unchanging standard
leads to moral corruption and erosion.

"Islam is a religion in which God requires you to send your son to
die for him. Christianity is a faith in which God sends his son to
die for you."
US Attorney General John Ashcroft
--
Jeremiah 52:8 but the Babylonian army pursued King Zedekiah and overtook
him in the plains of Jericho. All his soldiers were separated from him
and scattered,

i have a similar proble here with some ttf fonts (found on a font cd,
afaik)

i can "use" them on screen but when i print them in a postscript file
and try to show it with ghostscript i always get an error that smth is
wrong inside the file. if i use another ttf font (areal or so) it
works ok. i will see if i can re-find the font.

byebye...

--
Michael Merkel (MiMe@IRC)
Michael.Merkel@gmx.net
http://home.t-online.de/home/Merkel.Michael/

On 14-Oct-02, William F. Maddock wrote:

>> I suggest loading it, with its AFM, into Typesmith and resaving both
>> the PFM and AFM.
>
> Make that PFB and AFM. ='D

Yup.

Regards
--
Don Cox
doncox@enterprise.net

On 14-Oct-02, Michael Merkel wrote:
> i have a similar proble here with some ttf fonts (found on a font cd,
> afaik)
>
> i can "use" them on screen but when i print them in a postscript file
> and try to show it with ghostscript i always get an error that smth is
> wrong inside the file. if i use another ttf font (areal or so) it
> works ok. i will see if i can re-find the font.

Best to convert them to Type 1. There is really no advantage at all to
using the Truetype format on Amiga over Type 1.

Regards
--
Don Cox
doncox@enterprise.net

<doncox@enterprise.net> wrote at Mon, 14 Oct 2002 19:55:46 +0000
about <Re: [PageStreamAmigaBeta] Re: PageStream Amiga and printing>:

> On 14-Oct-02, Michael Merkel wrote:
> > i have a similar proble here with some ttf fonts (found on a font cd,
> > afaik)
> >
> > i can "use" them on screen but when i print them in a postscript file
> > and try to show it with ghostscript i always get an error that smth is
> > wrong inside the file. if i use another ttf font (areal or so) it
> > works ok. i will see if i can re-find the font.
>
> Best to convert them to Type 1. There is really no advantage at all to
> using the Truetype format on Amiga over Type 1.

of course: using them on screen. no other font format looks as good on
screen as ttf!
unfortunately inside pagestream it is vice versa...

byebye...

--
Michael Merkel (MiMe@IRC)
Michael.Merkel@gmx.net
http://home.t-online.de/home/Merkel.Michael/

Regarding the problem mentioned while using Black Chancery and printing
to PS:. I converted the font from TTF to Adobe and, my, my, it works
like a charm now. I no longer get the "encrypted" output. Very
interesting and thanks to all for the assist.

On 14-Oct-02, Don Cox wrote:

> On 14-Oct-02, Michael Merkel wrote:

>> i have a similar proble here with some ttf fonts (found on a font cd,
>> afaik)

> Best to convert them to Type 1. There is really no advantage at all to
> using the Truetype format on Amiga over Type 1.
>
But as I pointed out in a Sspt. 18 posting to the general PageStreamSupport
list,

> ... the conversion [from ttf] to Type 1 done by TypeSmith 2.5 is a
> little buggy: the composite characters (accented letters) are terribly
> misaligned.

So long as you don't need to use composite characters, the TypeSmith
conversion works OK. And at least the Type 1 versions of /Black Chancery/
that I have don't have many composite characters to worry about (fi and
fl, but no accented characters).

But in general, TypeSmith's conversions from ttf to Type 1 are buggy, while
PageStream's on-the-fly conversion from ttf to PostScript Type 3 for
PostScript output seems to be perfect.

--Geoff

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

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