#Ppage V1.2?
3 messages in this thread
I haven't had to run into the text limitation yet since most of my stuff is
still on a white background. I guess that's why they call them "white
papers". I tried out the color sep to see what got produced and thought I
was getting burned for a moment. I had included a bitmap which didn't
print out! Turns out they hid a switch to control printing of bitmaps in
the print requester. Oh well, maybe they'll have a workable version out as
fast as they put out a revision for Comicsetter.
I have given a Mac friend an EPSF file from Pro Draw to see how it plays
with Xpress. Will let you know what happens. I wonder if V1.2 of PPage
will be able to trade EPSF both ways. Would be nice since we have Xpress
and a Ventura setup lying around. My friend was sort of wowed when he saw
me able to produce a true color sep and not just mechanical overlays.
Incidentally if you've ever tried to ZAP a document or drawing file,
they've hidden a CRC in there somewhere. I had one document with a fair
number of bitmaps referencing a disk on another system. PPage would bitch
about not finding the files and then would only prompt for a new path for
the first bitmap encountered. I tried to ZAP the new device name into the
document file, but PPage complained about a corrupt document when it tried
to load it. Wish they would open up their formats!
Propage will report a "unable to load…" error if things other than
inability to find a file occur. For example, if there is insufficient
system memory to make a screen representation of the file, it says "can't
find .." and asks if you wish to substitute. That's a confusing error
message.
I like the CRC check on the files. That might prevent some nasties from
geting loaded (viruses, perhapos?) and resulting in a munged file when
re-saved.
If you pore through the Quick Reference Card and eyeball the file
format, it probly wouldn't be difficult to figure it out. that stuff is
mostly the same thing as mentioned in the QrefCard.
J: (no I don't work folr GoldDisk)
Bill, I was talking to Arno Krautter from Gold Disk today about the
"Document corrupt" problem that Professional Page has occasionally (not
always because of zapping the file, either!)… Arno says there is an
`ignore checksum' flag you can set by zapping a particular zero byte to
1… unfortunately, he couldn't remember off-hand the offset of the byte;
however, it is one of the sea of zeroes that comes after the string
identifying `Professional Page' near the beginning of the document and,
since it is the only byte amongst those (except for that string's
terminating null) that has any significance, changing them ALL to 1 should
work.
BTW, if you ever get a `Document Corrupt' that happens spontaneously (i.e.
PP's fault), this is apparently because of a bug in which the font size is
inadvertently set to zero by the program… search the document for
"fs<0>", zap the 0 to whatever point size you want, then zap the checksum
ignore flag as described above.
Arno says this bug has been fixed for the next version (2.0, I guess).