Hi,

Here is the next release, with full debug as promised. This is not a full
installation, only the changed files from last time. The old archive is
still up for those who didn't get it.

The menus are fixed showing recently opened files, fonts and more, but are
currently outside the document window. The problem is that we can't seem to
find a standard for what was originally called MDI, which stands for
multiple document interface. 90% of the Linux apps I've run seem to put the
menus etc on each document window. But of course you don't get the menus if
you don't have a document open. Those apps always start out with an
untitled document. If you close it, some will just open another untitled,
and some will quit (which I hate even more).

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

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

Hi,

This was probably in the last one and I just didn't notice, but when you run
PgS the navigator window's ability to resize the width is restricted to
making it larger. Well, playing with it I was able to get it to shrink
slightly, but always less than the expansion I just did. But then it decided
to pop wider (25 - 50 pixels past the mouse pointer) and would not shrink for
anything. Minor and cosmetic, I know, but still quite strange.

The font substitution is still messed up (but differently). I'm expecting you
knew that.

The file save as requestor (after opening an existing document) still locks up
PgS. It doesn't crash, just ceases to respond immediately after opening the
file requestor and before drawing inside it. So I ran PgS inside of gdb and
it works. Requestor pops up, select new location and save. First thing that
pops to mind is a timing issue, though it can be most any subtle thing with
that kind of behavior. Still has that annoying encoding of spaces as %20 and
so on.

I then closed and reopened the document. I got the font substitution requestor
again, but this time something was different: on loading the orginal it had
wanted to substitute a font named just C for Cour-Normal. In the "saved-as"
document it wanted to know what font to use as a substitute for C.

Its too bad that the fonts I liked to use on the amiga were the Compugraphic
ones. As I recall they didn't convert to type1 very well so at present I have
very few fonts on my system. Ah well.

Tim Doty

On Mon, 25 Aug 2003 22:15:06 -0500
Tim Doty <drakki@rollanet.org> wrote:

> Hi,
[...]
>
> Its too bad that the fonts I liked to use on the amiga were the
> Compugraphic ones. As I recall they didn't convert to type1 very well
> so at present I have very few fonts on my system. Ah well.
>
> Tim Doty
=======================

Tim,
It is possible to convert your Truetypes to Type1 fonts that work very
well on your system and I suspect PgS will like them also. I have
converted several over with the program ttf2pt1 and it seems to do a
very nice conversion. You can also specify both the .pfb and .afm
files, so Ghostscript will not have trouble rendering them.

IIRC, there were several nice Type1 fonts with Amiga PgS, which can be
added to your system. Just be sure to get both the .pfb and .afm files
to copy. As seemingly easy as everyone thinks the truetypes work, the
Type1 one fonts still give the better results and fit in nicer with a
postscript system, like Linux.

Patrick
--
---SuSE Linux v8.2 Pro---
Registered Linux User #225206
"Life's a garden, Dig It!" --Joe Dirt

On Monday 25 August 2003 23:00, Patrick wrote:
> On Mon, 25 Aug 2003 22:15:06 -0500
>
> Tim Doty <drakki@rollanet.org> wrote:
> > Hi,
>
> [...]
>
> > Its too bad that the fonts I liked to use on the amiga were the
> > Compugraphic ones. As I recall they didn't convert to type1 very well
> > so at present I have very few fonts on my system. Ah well.
> >
> > Tim Doty
>
> =======================
>
> Tim,
> It is possible to convert your Truetypes to Type1 fonts that work very
> well on your system and I suspect PgS will like them also. I have
> converted several over with the program ttf2pt1 and it seems to do a
> very nice conversion. You can also specify both the .pfb and .afm
> files, so Ghostscript will not have trouble rendering them.

Unfortunately the ones I'm missing are Compugraphic, not True Type. They can
be converted, but in the past I have been disappointed with the results.
Unless forced otherwise I use only type1. As you say, the linux print system
is postscript centric and I always get postscript printers.

Tim Doty

Using the current linux beta I got around to fixing up some of the font issues
I have and loaded up a document. The font translation seems to have some
issues, like remembering what has been checked for "remember" and a font that
was selected to be converted was only displayed as.

Moreover, when I printed the page all fonts were converted to courier anyway.
Is this expected behavior at this point? There is a box with a very light
fill on the page and this printed fine.

Tim Doty

On Saturday 13 September 2003 17:15, Tim Doty wrote:
> Using the current linux beta I got around to fixing up some of the font
> issues I have and loaded up a document. The font translation seems to have
> some issues, like remembering what has been checked for "remember" and a
> font that was selected to be converted was only displayed as.
>
> Moreover, when I printed the page all fonts were converted to courier
> anyway. Is this expected behavior at this point? There is a box with a very
> light fill on the page and this printed fine.

I did a second test. I opened the document and did the font substitution and
saved it as a pdf. This time all but one of the fonts came out right (and
that might have been from a Display-As instead of Convert-To problem in the
font substitution requestor), but there is something squirrely about the PDF.

Loaded into acrobat reader 5 (linux) it can't scroll down to the bottom of the
page if I grab the scroll bar and pull, but it will if I click beneath the
scrollbar handle. Although this might be a bug in acrobat reader, I suspect
that it is a problem parsing PgS's pdf output.

Secondly, the box that output fine to my printer is simply not there. Strange.

Tim Doty

>Using the current linux beta I got around to fixing up some of the font
>issues
>I have and loaded up a document. The font translation seems to have some
>issues, like remembering what has been checked for "remember" and a font that
>was selected to be converted was only displayed as.

Yes, I noticed that as well the other day. Unfortunately that is in display
library. That means I have to fix it

>Moreover, when I printed the page all fonts were converted to courier anyway.
>Is this expected behavior at this point? There is a box with a very light
>fill on the page and this printed fine.

It should work correctly if the font exists on the printer already (ie,
built in). Otherwise, not yet. Part of the downloading font part (I am
having to strip code from the Amiga font engines that converted fonts to
downloadables. Why the h*** that is not part of FreeType, or FontConfig, or
CUPS I do not know since everyone would have to do it if they want to print
what they display!!!) Very soon!

>Tim Doty

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

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

>I did a second test. I opened the document and did the font substitution and
>saved it as a pdf. This time all but one of the fonts came out right (and
>that might have been from a Display-As instead of Convert-To problem in the
>font substitution requestor), but there is something squirrely about the PDF.
>
>Loaded into acrobat reader 5 (linux) it can't scroll down to the bottom of
>the
>page if I grab the scroll bar and pull, but it will if I click beneath the
>scrollbar handle. Although this might be a bug in acrobat reader, I suspect
>that it is a problem parsing PgS's pdf output.

Send me the file, and I'll try it on Windows. I've not encountered a
problem like this before, and I use the PDF output all the time.

>Secondly, the box that output fine to my printer is simply not there. Strange.

Was it a light fill? Sometimes acrobats color "corrections" can screw
things up.

>Tim Doty

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

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

On Sunday 14 September 2003 00:21, PageStream Support wrote:
> >Using the current linux beta I got around to fixing up some of the font
> >issues
> >I have and loaded up a document. The font translation seems to have some
> >issues, like remembering what has been checked for "remember" and a font
> > that was selected to be converted was only displayed as.
>
> Yes, I noticed that as well the other day. Unfortunately that is in display
> library. That means I have to fix it
>
> >Moreover, when I printed the page all fonts were converted to courier
> > anyway. Is this expected behavior at this point? There is a box with a
> > very light fill on the page and this printed fine.
>
> It should work correctly if the font exists on the printer already (ie,
> built in). Otherwise, not yet. Part of the downloading font part (I am
> having to strip code from the Amiga font engines that converted fonts to
> downloadables. Why the h*** that is not part of FreeType, or FontConfig, or
> CUPS I do not know since everyone would have to do it if they want to print
> what they display!!!) Very soon!

Good! I'm not sure of the font list in the printer -- its a new (to me)
printer and I haven't checked the font specs. However, it should have the
standard postscript fonts. One problem is simply that I can't find time roman
anywhere except as the intellifont stuff on the amiga. Only a couple of them
were cached as type1 fonts and TypeSmith leaves a lot to be desired it turns
out in intellifont to type1 conversion. Haven't had time to try with anything
else.

Tim Doty

On Sunday 14 September 2003 00:22, PageStream Support wrote:
> >I did a second test. I opened the document and did the font substitution
> > and saved it as a pdf. This time all but one of the fonts came out right
> > (and that might have been from a Display-As instead of Convert-To problem
> > in the font substitution requestor), but there is something squirrely
> > about the PDF.
> >
> >Loaded into acrobat reader 5 (linux) it can't scroll down to the bottom of
> >the
> >page if I grab the scroll bar and pull, but it will if I click beneath the
> >scrollbar handle. Although this might be a bug in acrobat reader, I
> > suspect that it is a problem parsing PgS's pdf output.
>
> Send me the file, and I'll try it on Windows. I've not encountered a
> problem like this before, and I use the PDF output all the time.
>
> >Secondly, the box that output fine to my printer is simply not there.
> > Strange.
>
> Was it a light fill? Sometimes acrobats color "corrections" can screw
> things up.

Yes, it is a very light fill. However, this is the same fill as I've been
using for years now and it has yet to fubar like that.

Sending the file separately.

Tim Doty

> Sending the file separately.

Don't bother checking. I just saw the same behavior on a PDF that to the best
of my knowledge was not created by Pgs at all, much less the linux version. I
don't know why I've never seen this behavior from acrobat reader before, but
it is clearly reader.

Tim Doty

I like these kinds of bugs best

> > Sending the file separately.
>
>Don't bother checking. I just saw the same behavior on a PDF that to the best
>of my knowledge was not created by Pgs at all, much less the linux version. I
>don't know why I've never seen this behavior from acrobat reader before, but
>it is clearly reader.
>
>Tim Doty

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

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