From: ronkko@cc.helsinki.fi
Newsgroups: comp.sys.amiga.applications
Subject: PageStream problems
Date: 30 Jul 92 17:21:34 GMT
Organization: University of Helsinki

I have some questions about PageStream 2.2 HL:

1) How can I scale bitmap graphics objects so that they "match" printer
resolution? In PPage this is achieved very easily, because when scaling of
a picture is set to 1.0x (both horizontally and vertically), it equals 75
dpi on the page. So, it is easy to calculate that e.g. when scaling is set
to 0.25, each pixel of the picture is printed as one dot in a 300 dpi
laser printer. But how is this achieved in PageStream? When scaled to 25 %
(or 50, 75, 100...) the pictures do _not_ match laser resolution, but are
unevenly scaled. Also the aspect ratio of imported bitmaps seems to be
distorted, so that the pictures are streched vertically, even if the 
scaling is set to 100% both vertically and horizontally.

2) Why does PageStream 'modify' by itself x and y coordinates of objects,
page sizes etc, which have been entered manually to the requesters? This 
can be seen immediately after entering the coordinates, by reselecting
"change coordinats" item from menus (so there is no question of moving 
an object accidentally; I have also checked that I endeed deleted all 
'hidden' decimals). If I enter e.g. 0.6 cm (or 0.600000 cm, it doesn't 
make any difference), it may be changed to some peculiar decimal monster 
slighthly larger or smaller than 0.6 cm. This 'rounding error' also 
happens when I just change the default measuring system from cm to mm. 
(And millimeter should be _exactly_ 1/10 of centimeter, as far as I 
know!;-)

What is even worse, PageStream seems also have similar problems with grid
spacing. If I e.g. choose the 0.5 cm grid spacing (preset), and then 
immediately check it, it has been changed to peculiar decimal number 
smaller than 0.5 cm! But if I enter the 0.5 cm as a custom grid, it is 
not changed. On the contrary, if I try values like 0.4, 0.3, 0.2 or 
0.1 cm, they are again changed to a inaccurate decimal numbers. This has 
the effect that objects are not placed correctly on the page (the error 
is naturally larger the further the object is placed from the top left 
corner). Another problem is that when you check and adjust placement 
and aligning of objects manually, you have to deal with complicated 
decimal numbers which are difficult to figure, remember, and edit, 
instead of neat integers or short decimal values.
(BTW, this problem I have not noticed in PPage so far)

If anyone knows a solution to the problems above, I would be most 
grateful for your answer! I am in middle of making a poster and really 
in trouble... (deadline, you know;-).

3) Then a few less urgent questions...:-)  PageStream seems to understand
CG-fonts of PPage just by including the right path with font manager, and 
also prints them to non-postscript printers. But how can I use them with 
a postscript laser, so that they are replaced with the respective PS-fonts 
(like is the case in PageStream's own CG-fonts)? In manual there is 
mentioned "a PSF header file", which is needed for 'internal' PS-fonts. 
Is it needed also for PPage fonts, and how can it be created?

4) I have not been able to get PageStream to recognize type 3 postscript
fonts (included with PPage), even if I have set the right path. What's 
the problem? It is said in the manual (p. 1.32) that PageStream IS able 
to use type 3 fonts... 


---------------------------------------------------------------------------
  Reijo Ronkko     University of Helsinki, Dept. of General Microbiology,
                   Mannerheimintie 172, 00300 Helsinki, FINLAND
                   Fax +358-0-4735426     Ronkko@cc.helsinki.fi
---------------------------------------------------------------------------
Newsgroups: comp.sys.amiga.applications