Index » PageStream Support » Macintosh OSX » new update
Sign in to add a comment. Pages: 1
2008-06-13 14:58:36 CT #1
Deron Kazmaier
From: United States
Registered: 2006-01-29
Posts: 4639

Hi,

I uploaded a 5.0.4.19 update this morning, but a bug was reported that I
fixed right away. Loading a document would cause a crash everytime if
you were affected by this bug.

Anyway, new 5.0.4.20 should be available in a short while. Regular
download notice will be sent.

Sorry for the mixup, but with things getting so close I want to make
sure that nothing stands in the way of it being useful that I can help.
At this point, the only serious problem is the various non-postscript
printer problems. Generally works, but according to an Apple engineer,
not all printer driver manufactures properly handle postscript rendering
to their non-postscript devices. it is 100% possible with CUPS, but
evidently they don't always test for it?

Anyway, I've got a non-postscript printer to pickup that supposedly has
this problem, and suggested workarounds have been given to me by Apple
so we shall see.

If you have any problems, _please_ report them.

Deron

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


2008-06-15 19:50:25 CT #2
Jeff Krispow
From: United States
Registered: 2006-02-06
Posts: 19


Hi Deron,

I've been having an issue with the SAVE AS PDF expore feature, that I
thought I should bring to your attention.

Text and object colors in the PDF file do not match those in my
original PgS document. All colors are being rendered out "darker" in
the PDF file. (I also attempted various combinations of the
"compression" settings to see if that fixed anything, but had no
success.)

The reason I'm sending in this report is because I recall that some
colors were rendered slightly betters when using earlier betas of
PgS. But "something" changed somewhere around 5.0.4.15 or so -- a
fancy-schmancy document title I created just with some overlaying
text, line and fills used to look "okay" when rendered out to PDF,
and suddenly it looked like dark mush. And still did when I rendered
it out with this new version of PgS. I figured since the issue was
still there, I'd send in this report -- hopefully some of my
findings will help improve the color output issue.

Just as a quick example, here are some of the color difference that
occured when rendering out one of my document via SAVE AS PDF (using
standard RGB values):

PgS Blue (0, 0, 255) renders as PDF Midnight Blue (32, 25, 106)
PgS Blue 50% (128, 128, 255) = PDF Slate Grey (108, 96, 160)
PgS Dark Blue (0, 0, 139) = PDF Dark Slate Gray (55, 48, 83)
PgS Red (255, 0, 0) = PDF Crimson (213, 0, 0)
Pgs Gold (255, 215, 0) = PDF Goldenrod (249, 201, 0)
PgS Yellow (255, 255, 0) = PDF Yellow (255, 245, 0)

As you can see, there are some rather noticeable changes going on
here. I spent much of this afternoon doing additional testing of the
SAVE AS PDF feature color output without much success. I tried all
the various combinations of Compression options during save to see if
that affected the color rendering, but had no success other than
discovering other bugs with PgS.

One such bugs is that shape fills are not rendering out correctly via
SAVE AS PDF either -- however, I cannot recall if these ever worked
previously. Currently, shape fills are rendering out to PDF as a
solid fill, defaulting to whatever the first FILL Color is (i..e, a
Blue to Yellow shape fill renders to PDF as a solid Blue). Just as an
FYI, the same color changes occur with the shape fills when rendering
to PDF as previous stated.

That one positive note I can provide is that imported graphic files
were always rendered properly -- I've never noticed any changes in
the color palette with graphic files I've used to date.

Another major problem that repeatedly occurred to me today was that
with PgS v5.0.4.20 I was unable tio EVER use the SAVE AS PDF feature
twice without having PgS crash. It didn't matter if I changed some of
the document, or even closed the file and reopened the document again
(or a new doc). Trying to use SAVE AS PDF twice during a PgS session
resulted in a crash -- PgS would begin creating the PODF file, but it
would crash out at some point during the process. I would have to
Quit PgS and restart it after each SAVE TO PDF attempt. This
definitely wasn't an issue with versions 5.0.4..18 and earlier, but
is certainly occurring now with my 5.0.4.20.

I wanted to do a bit more testing of the color changes in the PDF
rendering, so I created a test doc consisting of 17 square objects,
each one filled with one of the 17 different fill color listed in the
PgS color palette. Here are the results (using standard RGB values as
gathered by a Color Picker program...):

PgS Black (0, 0, 0) = PDF Black (20, 20, 20)
PgS White (255, 255, 255 ) = PDF White (~235, 235, 235) + (255, 255,
255) -- all whites appears to have small pixel areas ranging from
(235, 235, 235) to (241, 241, 241) with the majority at (255, 255,
255)
PgS Blue (0, 0, 255 ) = PDF Midnight Blue (32, 25, 106)
PgS Brown (117, 81, 22) = PDF Dark Olive Green (107, 95, 67)
PgS Cyan (0, 255, 255 ) = PDF Dodger Blue (0, 146, 220)
PgS Green (0, 255, 0 ) = PDF Forest Green (0, 142, 57) -- this also
varies a bit in the color swatch, with small pixel difference ranging
from (0, 134, 53) to (0, 142, 57), with the majority at (0, 142, 57)
PgS Lavender (198, 140, 244) = PDF Rosy Brown (176, 125, 167)
PgS Lime (170, 255, 6Cool = PDF Dark Khaki (149, 204, 82)
PgS Magenta (255, 0, 255) = PDF Medium Violet Red (214, 0, 103)
PgS Mustard (255, 221, 94) = PDF Sandy Brown (249, 210, 83)
PgS Orange (255, 127, 0) = PDF Chocolate (233, 120, 0)
PgS Peach (242, 178, 45) = PDF Sandy Brown (230, 169, 45)
PgS Pink (255, 191, 255) = PDF Pink (242, 185, 203)
PgS Purple (178, 51, 255) = PDF Dark Magenta (152, 51, 126)
PgS Red (255, 0, 0) = PDF Crimson (213. 0, 0)
PgS Violet (63, 51, 255) = PDF Dark Slate Blue (69, 50, 125)
PgS Yellow (255, 255, 0) = PDF Yellow (255, 245. 0)

I only listed a couple of color swatches where there were "larger"
variations in color throuighout the swatch (rather like dithering,
but invisible to the eye). In actuality, all of the swatches had some
minor pixel areas with slightly different RGB values. Shouldn't solid
colors contain the same RGB values for all pixels in the swatch after
rendering to PDF?

In any event, should you wish to see my original PgS Fill Test doc
and the resulting PDF output, just let me know where to send it....


* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

On a separate note, when creating my test doc for the fill color
issues, I also discovered a new problem with LINE & FILL -- the FILL
attribute is broken. You now cannot properly change just the LINE
attribute for multiple filled objects.

I wanted to add a .5pt line around the 17 square box objects on my
test doc, each of which had a different fill color. Went through the
usual moves - Apple-A (Select All), "L" to bring up LINE & FILL,
selected "Stroked". changed my Line options, and pressed OK. All my
boxes now had a .5pt line around them... and also all changed to a
Yellow fill! Definitely not what I wanted!

I then discovered I could not UNDO this change; PgS wouldn't let me.
Instead I had to revert back to my saved doc to try again. (This
UNDO issue was repeatable each time after I had a LINE & FILL:
attribute mishap. PgS would not UNDO it, and the Edit Menu options
listed "Can't Undo".)

I went through the motions again, made my Line change, but this time
also examined the FILL section. I quickly saw what the problems were.
First off, the "Stroked": checkbox contained a Checkmark rather than
the expected "-" (hyphen) to signify multiple attributes were
present. Also, the "Color" field listed "Yellow" (which was the color
of the final box object created on my doc) rather than "<MIXED>".

So basically, the FILL section is broken with regard to multiple
object attributes. I tried to manually select <MIXED> in the Color
Field, but that didn't work (all my boxes still changed to a Yellow
fill).

However, I did test the LINE attribute, and that DOES work as it should.

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Well, that be it for now, Deron...

Sorry for the length of this posting, but I hope the detailed info
proves helpful in some manner.

Once again, thanks for all the hard work you're doing on our OSX
version -- it's very much appreciated! As always, can't wait to see
the new updated...

Best wishes,
Jeff Krispow


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


2008-06-23 12:37:14 CT #3
Deron Kazmaier
From: United States
Registered: 2006-01-29
Posts: 4639

Hi Jeff,

> Text and object colors in the PDF file do not match those in my
> original PgS document. All colors are being rendered out "darker" in
> the PDF file. (I also attempted various combinations of the
> "compression" settings to see if that fixed anything, but had no
> success.)
>

I think this is fixed for the next release _unless_ you define your
colors in CMYK. PageStream was writing all the colors in CMYK and for
whatever reason their color "correction" was generating those wacked
colors. Fixed in next release. But if you define your colors in CMYK,
PageStream will leave them in CMYK and you will still get wacky onscreen
colors. Nothing I can see to fix that.

BTW, this is not something that changed ever.

> One such bugs is that shape fills are not rendering out correctly via
> SAVE AS PDF either -- however, I cannot recall if these ever worked
> previously. Currently, shape fills are rendering out to PDF as a
> solid fill, defaulting to whatever the first FILL Color is (i..e, a
> Blue to Yellow shape fill renders to PDF as a solid Blue).

Shape fills have never been supported. It is _just_ about the last thing
that is not supported to PDF output. No idea when it will be.

> That one positive note I can provide is that imported graphic files
> were always rendered properly -- I've never noticed any changes in
> the color palette with graphic files I've used to date.
>

In the case of pictures, RGB pictures were left as such. I'll bet a CMYK
picture will display odd on screen as well.

> Another major problem that repeatedly occurred to me today was that
> with PgS v5.0.4.20 I was unable tio EVER use the SAVE AS PDF feature
> twice without having PgS crash. It didn't matter if I changed some of
> the document, or even closed the file and reopened the document again
> (or a new doc). Trying to use SAVE AS PDF twice during a PgS session
> resulted in a crash -- PgS would begin creating the PODF file, but it
> would crash out at some point during the process.

I can't reproduce this. It has been reported by a few others. If this
happens to you, please send the resulting crash log output that it
offers to show you!

> I only listed a couple of color swatches where there were "larger"
> variations in color throuighout the swatch (rather like dithering,
> but invisible to the eye).

That would have nothing to do with PageStream. That would be their
display code, and no I don't know why they would do that! I've seen that
done on less than 24bit per pixel screen modes.

> On a separate note, when creating my test doc for the fill color
> issues, I also discovered a new problem with LINE & FILL -- the FILL
> attribute is broken. You now cannot properly change just the LINE
> attribute for multiple filled objects.
>
>
>
Nothing new, but fixed in next release.

> I then discovered I could not UNDO this change; PgS wouldn't let me.
> Instead I had to revert back to my saved doc to try again. (This
> UNDO issue was repeatable each time after I had a LINE & FILL:
> attribute mishap. PgS would not UNDO it, and the Edit Menu options
> listed "Can't Undo".)
>
>
Never could undo that. Now you can in the next release.

Thanks for the report,

Deron

--
Happy Trails,
Deron Kazmaier deron@dogstarkennel.com
KD0AYO Western South Dakota
Dog Star Kennelhttp://www.dogstarkennel.com
---
Racing AKC Sepp-Star Seppala Siberian Husky Sled Dogs


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


Sign in to add a comment. Pages: 1
Index » PageStream Support » Macintosh OSX » new update

This topic is closed due to inactivity.