Files made with PageMaker 6.0 then printed to a file using GhostScript are 5-6MB. I made the files the same way in PgS and I'm getting a 16MB file. Doesn't matter if I use "save as PDF" or just print to a PDF file. Photos are resized before being embedded -- no more than 120 dpi (and many not that large). I even have two FEWER pages this time than I normally do (22 instead of 24).

Why are the PgS PDF files so large, and what can I do to shrink them?

The more I use PgS and find these little "surprises" the more I'm coming to dislike it. I WANT to like it, and have chalked most of the idiosyncrasies I'm finding to my learning curve and having used PageMaker 6.0 for so long. But then things like these unexpectedly large PDF files come up! I don't have Acrobat, and will not be purchasing it just to reduce file sizes. Is PgS not compressing the files, or is the PostScript to PDF conversion causing the files to be so big?

Another problem -- a subscriber just informed me that Acrobat Reader 7 won't read the created PDF files. What's up with that?

PGS doesn't shrink resized bitmaps. It gives out the full dpi from the
original bitmap.
So, if you have a 120 dpi bitmap, and resize it in PGS, made smaller,
still the full 120 dpi comes out. And not what you expect, an even
smaller dpi corresponding the dpi you want to print (save as PDF). A bug
(small).

The inhouse, Deron, PGS version does that better.

I use Adobe Acrobat.

Theo

Op 18-7-2012 20:52, frank.swygert schreef:
> Files made with PageMaker 6.0 then printed to a file using GhostScript are 5-6MB. I made the files the same way in PgS and I'm getting a 16MB file. Doesn't matter if I use "save as PDF" or just print to a PDF file. Photos are resized before being embedded -- no more than 120 dpi (and many not that large). I even have two FEWER pages this time than I normally do (22 instead of 24).
>
> Why are the PgS PDF files so large, and what can I do to shrink them?
>
> The more I use PgS and find these little "surprises" the more I'm coming to dislike it. I WANT to like it, and have chalked most of the idiosyncrasies I'm finding to my learning curve and having used PageMaker 6.0 for so long. But then things like these unexpectedly large PDF files come up! I don't have Acrobat, and will not be purchasing it just to reduce file sizes. Is PgS not compressing the files, or is the PostScript to PDF conversion causing the files to be so big?
>
> Another problem -- a subscriber just informed me that Acrobat Reader 7 won't read the created PDF files. What's up with that?
>

--
PageStream Pro 5.0.5.8 on Windows 7 Pro 64 bits (Dutch), Python 2.7.2 and PySide 1.1.0
AMD Athlon(tm) II X2 215 Processor at 2.70 GHz and 4 GB RAM

I sent a plea for help a couple of times, but for some reason, I never got return mail. Seems, on checking, my stuff was being bounced on the Yahoo groups account. Sigh!

Anyway, still more Pagestream blues...

Add to the strange on-screen behaviour when load files, which I mentioned before, I have another set of problems.

When making song sheets, I use Edit/Define/Text Styles, and everything comes up fine... I change things to the way I want, save it and then try to use the created Style (by choosing the appropriate Style in the Edit Palet at the bottom), Everything works fine... except the text I wanted outlined is no longer outlined. I have to change it manually. I do this by selecting Type/Line & Fill/Line/Stroked. I had already chosen this when I created my Style for Chords with the Define menu... but it does not "stick". Somewhere that particular selection disappears to God knows where. Yeah, I can then go back and change every line manually, but this really makes it long and tedious. Any suggestions why that particular choice does not want to "stay" selected?

As well, another problem that has cropped up just today, so that when I grab the text for a song, paste it into a file and try to Edit it, I simply can't. I set the cursor where I want and try to delete or add and nothing happens. I have tried to edit quite a number of songs, and now have that problem. Basically, Pagestream does not want to work for me.

So, now, as it stands, I can't use PageStream with this machine (my main one with Windows XP Pro, my wife's with XP Pro and my laptop with Windows 7 Enterprise). The only machine that I have that will work is an old iMac at school. It reads the files correctly and formats things as I desire. As I mentioned before, my main machine is a new install (well, about 6-8 weeks ago), and my laptop had the hard drive replaced and it too is a new install of less than two months old. Mind you, it did not work from day one of the new install.

I have some screen shots if that will help anyone to troubleshoot this ongoing problem.

Just in case that something on my regular email address is not accepting replies as spam, perhaps it might help to also send any reply to gil_knutson@sd33.bc.ca I should at least get one of them.

Hi Gil,

mmm, I never (anyway, I can't remember) use the Style in the Edit Palette.
I open a floating Style Palette (in the Window/Show Style Palette). In
fact it is always open the way I use it.
I never had any problem using this. But, maybe I am not using
complicated styles.

Hopes this works good for you!

Theo

Op 19-7-2012 13:00, GIL KNUTSON schreef:
> I sent a plea for help a couple of times, but for some reason, I never got return mail. Seems, on checking, my stuff was being bounced on the Yahoo groups account. Sigh!
>
> Anyway, still more Pagestream blues...
>
> Add to the strange on-screen behaviour when load files, which I mentioned before, I have another set of problems.
>
> When making song sheets, I use Edit/Define/Text Styles, and everything comes up fine... I change things to the way I want, save it and then try to use the created Style (by choosing the appropriate Style in the Edit Palet at the bottom), Everything works fine... except the text I wanted outlined is no longer outlined. I have to change it manually. I do this by selecting Type/Line & Fill/Line/Stroked. I had already chosen this when I created my Style for Chords with the Define menu... but it does not "stick". Somewhere that particular selection disappears to God knows where. Yeah, I can then go back and change every line manually, but this really makes it long and tedious. Any suggestions why that particular choice does not want to "stay" selected?
>
> As well, another problem that has cropped up just today, so that when I grab the text for a song, paste it into a file and try to Edit it, I simply can't. I set the cursor where I want and try to delete or add and nothing happens. I have tried to edit quite a number of songs, and now have that problem. Basically, Pagestream does not want to work for me.
>
> So, now, as it stands, I can't use PageStream with this machine (my main one with Windows XP Pro, my wife's with XP Pro and my laptop with Windows 7 Enterprise). The only machine that I have that will work is an old iMac at school. It reads the files correctly and formats things as I desire. As I mentioned before, my main machine is a new install (well, about 6-8 weeks ago), and my laptop had the hard drive replaced and it too is a new install of less than two months old. Mind you, it did not work from day one of the new install.
>
> I have some screen shots if that will help anyone to troubleshoot this ongoing problem.
>
> Just in case that something on my regular email address is not accepting replies as spam, perhaps it might help to also send any reply to gil_knutson@sd33.bc.ca I should at least get one of them.
>
--
PageStream Pro 5.0.5.8 on Windows 7 Pro 64 bits (Dutch), Python 2.7.2 and PySide 1.1.0
AMD Athlon(tm) II X2 215 Processor at 2.70 GHz and 4 GB RAM

PageStream will output PDFs with the whole original bitmaps inside them.

If you want them to be smaller, from the COMPRESSION tab in the PDF output window, switch to JPEG compression and scale the quality to where you want it.

--- In PageStreamSupport@yahoogroups.com, Theo Zweers <tjzwrs@...> wrote:
>
> PGS doesn't shrink resized bitmaps. It gives out the full dpi from
> the original bitmap.

It actually SHOULD resize the bitmaps if you specify the parameters in RESIZE BITMAPS in the PDF output window, but it doesn't. This feature seems broken (too bad - I really could have used it).

I suspect PageMaker is generating smaller PDFs because its either resampling bitmaps in the document to lower resolution, or using heavier JPEG compression, or both.

- Brent

Op 19-7-2012 19:09, Brent schreef:
> PageStream will output PDFs with the whole original bitmaps inside them.
>
> If you want them to be smaller, from the COMPRESSION tab in the PDF output window, switch to JPEG compression and scale the quality to where you want it.
>
> --- In PageStreamSupport@yahoogroups.com, Theo Zweers <tjzwrs@...> wrote:
>> PGS doesn't shrink resized bitmaps. It gives out the full dpi from
>> the original bitmap.
> It actually SHOULD resize the bitmaps if you specify the parameters in RESIZE BITMAPS in the PDF output window, but it doesn't. This feature seems broken (too bad - I really could have used it).
>
> I suspect PageMaker is generating smaller PDFs because its either resampling bitmaps in the document to lower resolution, or using heavier JPEG compression, or both.

Maybe!
PGS also has more finesses, or refinement if you like, for output. So
the size (print and PDF) is somewhat larger. Add the (not) capability
for shrinking bitmaps.

So what is the best way to loose some bits, and so: Bytes.
For the time being: resize the bitmap, outside PGS, to the right size
(and correct dpi), so you don't have to resize this bitmap in PGS!

Let us hope that Deron finds time to make us an update, someday.

Theo

>
> - Brent

--
PageStream Pro 5.0.5.8 on Windows 7 Pro 64 bits (Dutch), Python 2.7.2 and PySide 1.1.0
AMD Athlon(tm) II X2 215 Processor at 2.70 GHz and 4 GB RAM

On Thu, 19 Jul 2012 13:09:37 -0400, Brent <woodenflutes@yahoo.ca> wrote:

>
> PageStream will output PDFs with the whole original bitmaps inside them.
>
> If you want them to be smaller, from the COMPRESSION tab in the PDF output window, switch to JPEG compression and scale the quality to where you >want it.
>
> --- In PageStreamSupport@yahoogroups.com, Theo Zweers <tjzwrs@...> wrote:
>>
>> PGS doesn't shrink resized bitmaps. It gives out the full dpi fromthe original bitmap.
>
> It actually SHOULD resize the bitmaps if you specify the parameters in RESIZE BITMAPS in the PDF output window, but it doesn't. This feature seems >broken (too bad - I really could have used it).
>
> I suspect PageMaker is generating smaller PDFs because its either resampling bitmaps in the document to lower resolution, or using heavier JPEG >compression, or both.
It seems to work in my version of Pagestream on linux. I did a compression on images, used jpeg2000 format and 100% quality. almost cut the pdf file size in half,40.1 megs without compression 23.8 megs with.

[Non-text portions of this message have been removed]

Op 20-7-2012 4:21, admfubar@gmail.com schreef:
> On Thu, 19 Jul 2012 13:09:37 -0400, Brent <woodenflutes@yahoo.ca> wrote:
>
>> PageStream will output PDFs with the whole original bitmaps inside them.
>>
>> If you want them to be smaller, from the COMPRESSION tab in the PDF output window, switch to JPEG compression and scale the quality to where you >want it.
>>
>> --- In PageStreamSupport@yahoogroups.com, Theo Zweers <tjzwrs@...> wrote:
>>> PGS doesn't shrink resized bitmaps. It gives out the full dpi fromthe original bitmap.
>> It actually SHOULD resize the bitmaps if you specify the parameters in RESIZE BITMAPS in the PDF output window, but it doesn't. This feature seems >broken (too bad - I really could have used it).
>>
>> I suspect PageMaker is generating smaller PDFs because its either resampling bitmaps in the document to lower resolution, or using heavier JPEG >compression, or both.
> It seems to work in my version of Pagestream on linux. I did a compression on images, used jpeg2000 format and 100% quality. almost cut the pdf file size in half,40.1 megs without compression 23.8 megs with.
>

That isn't the point.
JPEG's do (!) shrink the bitmaps in PGS. JPEG2000 does that better than
JPEG (optical: less JPEG faults - blocks - and sharper and colorful image).
The resulted pdf , however, is a large pdf. Larger than expected.

One should expect that the resized (smaller) made bitmap (in PGS!) gives
a smaller sized (less Bytes) output than a not resized bitmap. Not so,
in this version of PGS (and older PGS 5 versions).

What I do, and this gave me the best result, is this: I use JPEG2000 at
5 % in Compression in Save As PDF (Shrink Bitmaps doesn't work).
The resulted pdf I open in Acrobat, and save it as 'Adobe PDF-file,
optimized'.
A 5 MB pdf shrinks to 4 MB (depending to the amount of bitmaps in the
document).

Theo

--
PageStream Pro 5.0.5.8 on Windows 7 Pro 64 bits (Dutch), Python 2.7.2 and PySide 1.1.0
AMD Athlon(tm) II X2 215 Processor at 2.70 GHz and 4 GB RAM

Terminology used here is getting a little muddled and confused. Bitmaps arent being shrunk because one uses one image format over another.
The bitmaps are the same the data in the file is compressed differently, to reduce the file size, not the overall image pixels.

On Fri, 20 Jul 2012 01:52:23 -0400, Theo Zweers <tjzwrs@gmail.com> wrote:

>
>
> That isn't the point.
> JPEG's do (!) shrink the bitmaps in PGS. JPEG2000 does that better thanJPEG (optical: less JPEG faults - blocks - and sharper and colorful image).
> The resulted pdf , however, is a large pdf. Larger than expected.
>
> One should expect that the resized (smaller) made bitmap (in PGS!) givesa smaller sized (less Bytes) output than a not resized bitmap. Not so,in this version of PGS (and older PGS 5 versions).
>
> What I do, and this gave me the best result, is this: I use JPEG2000 at5 % in Compression in Save As PDF (Shrink Bitmaps doesn't work).
> The resulted pdf I open in Acrobat, and save it as 'Adobe PDF-file,optimized'.
> A 5 MB pdf shrinks to 4 MB (depending to the amount of bitmaps in thedocument).
>

[Non-text portions of this message have been removed]