If i add a Font using the Edit Font Sets when i do not have an active FW file open, the Font set added does not appear within the available Fonts the next time i open a FW file… is this correct? To use a particular font within a FW file i have to edit the Font set when the FW file is open… is this how it is meant to work?
Also i noted that if i add a font using the Caxton action that particular font appears in every FW file i choose to open…
Viewing the system Fonts under the Web Category i have a number of Fonts showing that do not appear in the list of Fonts available in FW is this correct?
What I know is that if you make a new font set with no Freeway Pro file
open, that font set is only available to NEW documents - documents created
after the font set was created. Existing documents you must recreate the
font set.
Previously created Freeway Pro files will not contain that font set. As
Far As I Know, there is no way to import or export a font set, nor is there
any other shorthand way to import the font set.
I’ve never used the Caxton action, but afaik that isn’t the same as
creating a font set. Font sets are all about browser fallbacks…
Translates to (if available) Helvetica, (if not, then) Ariel, (or try)
Geneva, (or try the user browser’s) sans-serif (setting).
I don’t know about which system fonts you refer to (or what version of
system you’re on) but my system fonts work. That said, I’ve had plenty of
problems with other fonts. Before someone chimes in with the old “good
font, bad font” ditty, let me just say what we all know that Freeway is
crappy about fonts. I’ve heard explanations about font history and
programming history but the bottom line is FWP has fundamental font issues.
Fortunately for me, that doesn’t matter because I purposely limit the fonts
I use, only recently expanding them to include Google webfonts (of which
the few of those I’ve used, I’ve not had a problem).
Font handling is just one of those lingering issues that have gone on so
long as to be absurd and ridiculous. Softpress really needs to do a
moonshot - raise serious capital and redo the core application so the app
becomes truly modern.
Best, always…
Ernie Simpson, aka The Big Erns
If i add a Font using the Edit Font Sets when i do not have an active FW
file open, the Font set added does not appear within the available Fonts
the next time i open a FW file… is this correct? To use a particular font
within a FW file i have to edit the Font set when the FW file is open… is
this how it is meant to work?
Also i noted that if i add a font using the Caxton action that particular
font appears in every FW file i choose to open…
Viewing the system Fonts under the Web Category i have a number of Fonts
showing that do not appear in the list of Fonts available in FW is this
correct?
Actually, I think it’s subtly different. Anything you do in Freeway when no documents are open will affect all documents you create after that change. Any documents you have previously created already inherited their defaults from whatever Freeway was set to before that time. Think of these application-level defaults like a rubber stamp. When you create a new document, it gets “stamped” with the font sets, colors, document setup preferences, etc. that you set Freeway to use globally. At that moment, the two things (Freeway and that document) diverge – any changes made to each affect only the thing you changed, not every other document extant. This is a good thing, if you think about it.
Walter
On Nov 1, 2013, at 4:37 AM, ejw wrote:
If i add a Font using the Edit Font Sets when i do not have an active FW file open, the Font set added does not appear within the available Fonts the next time i open a FW file… is this correct? To use a particular font within a FW file i have to edit the Font set when the FW file is open… is this how it is meant to work?
Also i noted that if i add a font using the Caxton action that particular font appears in every FW file i choose to open…
Viewing the system Fonts under the Web Category i have a number of Fonts showing that do not appear in the list of Fonts available in FW is this correct?
Actually, I think it’s subtly different. Anything you do in Freeway when
no documents are open will affect all documents you create after that
change. Any documents you have previously created already inherited their
defaults from whatever Freeway was set to before that time. Think of these
application-level defaults like a rubber stamp. When you create a new
document, it gets “stamped” with the font sets, colors, document setup
preferences, etc. that you set Freeway to use globally. At that moment, the
two things (Freeway and that document) diverge – any changes made to each
affect only the thing you changed, not every other document extant.
This is a good thing, if you think about it.
I have thought about it for at least a decade… Walter - I love you but
could not disagree more with this.
Thank you for the response, OK i understand now about adding new Font Sets and how they are implemented in new FW Files.
However i cannot understand why FW pro is not using the Web fonts that are listed in my System Fonts library.
I use an application called Font Book (think it came with the system) and in there it displays Fonts by “Collection” ie English, Chinese, Windows office Compatible etc, and Web and in there i have about 7 or 8 fonts and some of these are not available by FW Pro… why is this?
If you have a font set in one FW document and copy/paste a selection of text that has that set applied to it to another FW doc I believe the font set goes with it.
I agree that it could be better, in terms of the global collection of fonts and colors, but there are other things that are treated the same way that I would not want to have changed in legacy documents, but that I might want to change going forward with new ones.
I suspect that part of this has to do with workflow. If you work alone, and you’re the only one who ever touches your documents, then fine, I can accede the argument that you should be able to affect documents from the past like this. But part of Freeway’s charter is to support larger workgroups. Without delving into creating a Workgroup Edition of Freeway, with a dedicated central server or some sort of background synch, there’s no good way to make options like this travel with the document unless you also save them (exclusively? maybe there is a way out of this corner after all) in the document itself.
As I’m writing this, I am thinking maybe when you subsequently open a legacy document in Freeway, it could prompt you to merge the settings if they differ from the last time that document was saved. I do know that this is insanely hard to do correctly, so it’s no mystery for me as to why it may have lain fallow, lo these many years.
Walter
On Nov 1, 2013, at 7:34 AM, Ernie Simpson wrote:
Actually, I think it’s subtly different. Anything you do in Freeway when
no documents are open will affect all documents you create after that
change. Any documents you have previously created already inherited their
defaults from whatever Freeway was set to before that time. Think of these
application-level defaults like a rubber stamp. When you create a new
document, it gets “stamped” with the font sets, colors, document setup
preferences, etc. that you set Freeway to use globally. At that moment, the
two things (Freeway and that document) diverge – any changes made to each
affect only the thing you changed, not every other document extant.
This is a good thing, if you think about it.
I have thought about it for at least a decade… Walter - I love you but
could not disagree more with this.
As I’m writing this, I am thinking maybe when you subsequently open a
legacy document in Freeway, it could prompt you to merge the settings if
they differ from the last time that document was saved.
Or maybe prompt you about replacing the legacy document font set with the
newer/altered application font set… then if you choose to keep the legacy
document font set, renaming it from MyFontSet to MyFontSet2.
