[Pro] WEB Fonts

I noticed that in Ernie’s “Basic Inline Layout Template” he tends to use a lot of web fonts. I’m intrigued by this, but I’ve never tried it myself.

What’s involved in using a web font in FWP?


offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

I don’t know what you mean by “a lot”. Too much of anything is bad for you.
Here is a Google font tutorial I began and never finished – having been
distracted by the discovery of making round stuff with CSS…

Thebigerns.com

And… here is something I’ve been fiddling with that utilizes different
Google font combinations on different pages…

thebigerns.com


Ernie Simpson

On Wed, Oct 2, 2013 at 9:42 AM, RavenManiac email@hidden wrote:

I noticed that in Ernie’s “Basic Inline Layout Template” he tends to use a
lot of web fonts. I’m intrigued by this, but I’ve never tried it myself.

What’s involved in using a web font in FWP?


offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options


offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Well, perhaps a LOT was a bit of an exaggeration. You had quite a few WEB Fonts in your FWP font menu, but only a few were actually being used. :slight_smile:


offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Well, perhaps a LOT was a bit of an exaggeration. You had quite a few WEB
Fonts in your FWP font menu, but only a few were actually being used. :slight_smile:

Ahhh… in the Freeway Pro file. Those are defined font-sets so to bring the
font into the FWP working environment. You still have to add the other
Google code, per my partially finished tutorial (which is completely
finished as far as the “how to” bit goes).

Font-sets are weird - if you define one in a document, it stays in that
document. If you define one with no document open, it will appear in all
new documents but never in any that already exist. So favorite font-sets
are hard to make. I tend to keep their code handy in Sticky Notes.

It’s stupid behavior, as if fonts were a last minute add-in for the first
version, then nobody ever bothered to look back in on it. It’s that Mess in
the Closet nobody ever acknowledges… except at parties when you politely
ask “what on Earth is that dreadful smell?” Then they laugh nervously and
change the subject.


offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

I take it that although I can see your Font Sets in FWP I cannot edit them using the Edit Font Sets menu, correct? Is that because I would physically need to add them to my copy of FWP?


offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

It’s even worse than that. It’s a hold-over from System 7.5, when Freeway was first written. Freeway 1 - 3 used a font technology invented by Apple called QuickDraw GX. This was later “Steved” by someone at Apple (not actually SJ; he was busy at NeXT at the time), but quietly preserved in the form of a System extension called GX Graphics. This caused all sorts of fun headaches with Adobe Type Manager and friends. I remember it not fondly at all.

When Freeway was converted to run natively (as a Carbon app) in the early days of OS X, naturally GX was not available in the newly-scrubbed Carbon APIs (all vestiges of Mac OS 8 were removed, only a very few extensions made the cut).

Softpress had to re-invent the entire font engine at that point (and man, did it suck hard at composition in the earliest versions) but they kept the basic premise that had persisted since the earliest days of Freeway, forced upon them by GX Graphics. At system startup, all enabled fonts were quietly copied over from the system to the GX Fonts collection, and saved separately for any GX applications to use. This meant that the list of GX fonts could only be altered by restarting your entire Mac. Since Softpress had always worked within this constraint, the very notion of on-the-fly font list manipulation was entirely foreign, and the hooks just weren’t put into the application. I’m not sure how they could be at this point without a rather deep set of incisions.

My usual caveats apply here – this is hearsay and deduction, no actual source code has been viewed by yours truly.

Walter

On Oct 2, 2013, at 12:32 PM, Ernie Simpson wrote:

It’s stupid behavior, as if fonts were a last minute add-in for the first
version, then nobody ever bothered to look back in on it. It’s that Mess in
the Closet nobody ever acknowledges… except at parties when you politely
ask “what on Earth is that dreadful smell?” Then they laugh nervously and
change the subject.


offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

I take it that although I can see your Font Sets in FWP I cannot edit
them using the Edit Font Sets menu, correct? Is that because I would
physically need to add them to my copy of FWP?

No, as I said they are part of that FWP document and can always be used in
that document or a Saved As variant. You can save that document as a
template and then every new document from that template would have them.

AFAIK, you would have to manually recreate them in your FWP with no
documents open to otherwise make them persist. This is why I heap ridicule
on the poor sod who first thought up this whole mechanism and then every
programmer since who let it stand.


Ernie Simpson


offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options