#CGfonts /propage help?
13 messages in this thread
I downloaded some Shareware CG fonts that were uploaded recently here. I
only tried one, but it has the same problem I've seen in some converted
Adobe fonts. That is, in ProPage, the font looks like a bunch of drawn
boxes, some of which have small letters in them. The font is
Adine-Kirkenberg-Script from Adine.lha.
I'm asking now {without much experimentation} because of previous similar
problems. This ProPage verion is 1.3.
What am I doing wrong?
-DonM – On Autopilot from 1Q1 –
Altitude hold is on; now all's I need is coupled nav!
Not all of the characters are necessarily defined — those that aren't are
represented by boxes. Print of view the entire typeface to see what's
there.
Mmm … tricky that one.
I haven't got the AdineKirnbergScript file in its converted form, only the
original PostScript Type-1 … and there's certainly nothing odd about the
font. It has a full set of upper- and lower-case letters, numerals and a
few punctuation symbols … there are no drawn boxes with small letters in
them.
It's almost as though ProPage is getting the wrong font file when it's
trying to load the AdineK file. When you say `a bunch of drawn boxes', do
you mean they look hand drawn? Also, the `some' which have letters in
them, what is their correspondence to the keys you're pressing to generate
the character (in other words, what do you get when you press different
keys?)
I can't see why, but it's always possible that ProPage 1.3 has problems
with converted font files … after all, the FontManager conversion seems
very far from perfect and it may be that PPage3.0 is designed to handle any
errors in them.
Mike (from the UK)
Oops. It's PPage 3.0. I had forgotten to update my updates file.
sheesh.
The 'drawn box' just consists of a box with rounded corners for each
character; corresponding roughly in size to the selected font size.
Within some of the boxes is a 'normal (Topaz?)' character that corresponds
to that character's position in the ascii table. This seems to be PPage's
reaction to an almost-recognizable font. I have downloaded and translated
a number of Type-1 fonts from here. Some of them have this
characteristic, as well. Most work fine.
The test method is a previously generated 'font tester' file. It's just a
text box with all u/l case, punctuation and numerals. Highlight all, and
choose a font, and there ya go.
Steve Ahlstrom replied with the suggestion that some of the characters
were missing. That seems not to be the case (see above). I was unable to
reply with AutoPilot, as I'm doing now, because a subsequent AutoPilot
crash lost, among others, that message. Note the irony. <grin>
Still dunno.
-DonM – On Autopilot from 1Q1 –
Altitude hold is on; now all's I need is coupled nav!
Problem fixed thanks to Gold Disk Tech Support.
Thanks for helping.
-DonM – On Autopilot from 1Q1 –
Altitude hold is on; now all's I need is coupled nav!
Don,
I have downloaded Adine Script and it converted ok using Fontmanager and
Propage 3. I can't say for sure but I suspect that ProPage 1.3 can't read
the file. Ask Philip Laiter at Gold Disk.
BTW, not all the so called pd fonts do convert correctly, if at all.
Pete from Dorset in Englands West Country – via Whap!
Don,
ProPage doesn't know that the new font is available to it! You need to run
a program called CGUpdate that will let PPage know all about the new font.
You should have this progarm on a CGFonts disk. If I were you, I'd upgrade
to PPage 3 pronto. You'll never look back!
Best Wishes,
John
Don,
To summarize all the useful info posted to you:
– PPage 1.3 will not support the CGFONTS converted with FontManager. A
major change in AGFA's font technology occured when we created PPage 2.1.
You will need to upgrade if you want to use Typefaces converted with
FontManager.
– For those who are using PPage 3.0, after converting fonts with
FontManager, you will need to run a utility file called "CGUPDATE". This is
available here on CS or it shipped with Professional Draw 3.0.
You should not have PPage or PDraw running while you update your font list
with CGUPDATE.
– Some Type 1 Fonts will not convert because they contain 'illegal'
characters within their code…others may not convert because there is a
problem with FontManager's compatibility with certain fonts.
– It best to have the .afm and .pfb file in the same directory…run
FontManger, select only the .pfb file and convert it…creating the PS
download file at this time is a good idea. The font should be written to
your CGFONTS: directory. Then run CGUPDATE when done.
Philip Laitar
Manager
Ok, got it. Thank you.
It is PPage 3.0. I keep a text file with major software current versions.
I try to keep it updated, but … <sigh>
The problem was fixed by the CG_Update program in PDraw 3.0; which is in
an 'Artwork' drawer. A little too separated, methinks.
While I've got you <g>, what's an optimal setup for fonts? I may have a
bit of a mess. There's a CGFONTS dir, of course. There's also a FONTS
dir, which seems to contain bitmap fonts and the metrics. Many of those
appear to duplicate what's in my FONTS: directory. Bearing in mind that I
go back to the earliest PageSetter days, and that I'm sure there's stuff
in both PPage and PDraw still there from previous versions, how much of
this stuff do I really need?
That all this stuff still works is certainly no fault of mine. Tip'o'the
hat to you folks!
-DonM – On Autopilot from 1Q1 –
Altitude hold is on; now all's I need is coupled nav!
Don,
On most systems, you will have a fonts: directory, which contains bit-map
fonts used by your entire system. This directory is assigned during the
running of your startup-sequence file on boot up.
This directory is normally in the root of your hard drive, i.e. DH0:fonts.
PPage and Pagesetter shipped with some 'bit-map fonts' (but I don't know
why anyone would want to use them now-a-days) and depending on how one
installs PPage or Pagesetter you may have placed them already in the
assigned fonts: directory or had a new fonts: directory created in the
PPage directory along with a icon you must double click on to 're-assign'
fonts: to use only this new directory…wow!
To simplify, if you want to use the bit-map fonts (for any application that
uses bit-map fonts), they should be copied to your assigned system fonts
directory, if you don't want't them any more you may want to delete
them…but only the ones form PPAGe, deleting all bit-map fonts will cause
you problems.
If all you are using is PPage 2.1 or higher, the CGfont only requires the
.lib, .metric, and .dat files. The .atc file was required for PPage 2.0 and
Pagesetter II and may be removed.
PDraw 3.0 also can access the CGFonts directly and you may wish to remove
the .pdfont files from your PDRAW/Fonts directory.
Finally, under older versions of PPage and Pagesetter (Ppage 2.0 and
PageSetter II) a directory within the programs directory called CGCACHE was
created and stored font info. This directory, along with a file called CGT
may be removed. PPage users were given the opportunity to remove the
CGCache when PPAGE 2.1 was installed.
Any Questions? ;^)
Philip Laitar
Manager
Philip,
It may be worth pointing out that no one using Propage (I use V3.0) should
delete Topaz from Fonts: as this will well and truly screw up all the
menus, requesters etc etc. I know, I found out last week.
Pete from Dorset in Englands West Country – via Whap!
Pete,
Funny, I thought I mentioned something like that…oops! Thanks for making
a catch if I goofed.
Philip Laitar
Manager
PL> Any Questions? ;^)
Yes. May I go to the bathroom now? B-)
Thank you. I think that's going to clear out quite a bit of hd space.
-DonM – On Autopilot from 1Q1 –
Altitude hold is on; now all's I need is coupled nav!