It comes with a „myfontskit.css“ and a folder „webfonts“.
At the server I put both into the rootfolder and connect the .css it via before :
It works perfect online on the server.
My question here is, how do I achieve this too in a lokal preview in FW?
Where should I put the .css file / webfonts folder and how would be the correct path in the head section? And can I have both? A correct lokal preview AND a correct embedded fonts online at a server at the same time?
That is a relative path and if you changed it to an absolute one you will
get what you want
Dave, I think Hanna is asking about previewing the font locally… so an
absolute path would break that. I do question her example url-- should it
not have a leading slash / before the css filename? Shouldn’t it be:
She could load it automatically to the Site folder using the Upload Stuff
action and place it beside the html file.
When I used Adobe’s Typekit the font was only visible from the web server,
never locally. Now, I admit that I’m too lazy to look at how MyFonts
implements their webfonts – if there are some similar script requirements
or such. If that’s the case, then the font can only be previewed online,
uploaded to a server.
Services who use this scheme do so for licensing reasons-- they can see
where and how the font is used, and turn it off when your subscription
expires (at least that was my experience with Typekit). This is why I now
use Google Fonts-- more generous license, easier technology which can be
previewed in Freeway, downloadable screen font so also previews in the
Freeway Workspace. Fewer font choices though, and sometimes fonts are
removed from the list, but I can live with all that. After all, fonts are
merely decoration.
Hanna, I’d look at MyFonts and see if they have any advice for locally
previewing font choices in your browser while you are building a website –
mentioning that you use Freeway would likely be counter-productive as you
don’t want their support people getting all hung up on that as it is
irrelevant… you are building websites with html and css-- front-end code.
That is what Freeway does for you. If their system supports local
previewing is all you want to know.
That is a relative path and if you changed it to an absolute one you will
get what you want
Dave, I think Hanna is asking about previewing the font locally… so an
absolute path would break that. I do question her example url-- should it
not have a leading slash / before the css filename? Shouldn’t it be:
She could load it automatically to the Site folder using the Upload Stuff
action and place it beside the html file.
When I used Adobe’s Typekit the font was only visible from the web server,
never locally. Now, I admit that I’m too lazy to look at how MyFonts
implements their webfonts – if there are some similar script requirements
or such. If that’s the case, then the font can only be previewed online,
uploaded to a server.
Services who use this scheme do so for licensing reasons-- they can see
where and how the font is used, and turn it off when your subscription
expires (at least that was my experience with Typekit). This is why I now
use Google Fonts-- more generous license, easier technology which can be
previewed in Freeway, downloadable screen font so also previews in the
Freeway Workspace. Fewer font choices though, and sometimes fonts are
removed from the list, but I can live with all that. After all, fonts are
merely decoration.
Hanna, I’d look at MyFonts and see if they have any advice for locally
previewing font choices in your browser while you are building a website –
mentioning that you use Freeway would likely be counter-productive as you
don’t want their support people getting all hung up on that as it is
irrelevant… you are building websites with html and css-- front-end code.
That is what Freeway does for you. If their system supports local
previewing is all you want to know.
Thanks Dave, it is how Ernie described it indeed. I want to preview locally. And yes Earnie that licensing thing can be the reason. Sorry. It was my mistake to use the leading slash/.
It should be:
Thanks you for pointing at it.
I will ask Myfonts as you suggested Ernie.
Thanks a lot!
Hanna
That doesn’t mean that you cannot use the full URL for this. All it means is that the font is served to you via your internet connection if you are connected.
I don’t think this is a very good idea. You will get two copies of the same sheet, not a fallback. Two different URLs are treated differently by a browser. There are a couple or more articles in the SP KnowledgeBase about setting up Web fonts so they can be previewed locally. The key is to install those fonts on your Mac as local system fonts, and then you can refer to them by name in your Freeway-generated stylesheet, and they will be picked up from the local system, not as Web fonts, just as Helvetica Neue or Palatino would be.
That ‘Open Sans’ would attempt first to resolve to a locally-installed font, failing that, the one defined in the MyFontsWebfontsKit.css would be used.
Walter
On Feb 14, 2015, at 6:00 AM, DeltaDave email@hidden wrote:
Thanks Dave, it is how Ernie described it indeed
That doesn’t mean that you cannot use the full URL for this. All it means is that the font is served to you via your internet connection if you are connected.
Cant see that as much of an issue as we are probably only talking about a few Kb in size.
The problem as I see it - and I have seen it often - is that a FW user sets up the font on their Mac and as a Font Set in FW to give them local display.
But something goes wrong with the path to the CSS file or naming of files within it and the FW user still sees the ‘web font’ but only because they have it on their system and are lulled into a false sense of security.
I had a case earlier this week where the Client’s machine would not display the web font but the FW user could and couldn’t understand what the problem was.
The problem as I see it - and I have seen it often - is that a FW user sets up the font on their Mac and as a Font Set in FW to give them local display.
Yep.
But something goes wrong with the path to the CSS file …
I’m not aware how MyFonts works. I assume you get two things:
The css-file and the FONTs. Furthermore, I assume that the path within the css file points to somewhere or nowhere - so my questions is:
Where to you put your FONT resources?
What is the path (structure) within the css-file?
If my assumptions are wrong - sorry, but my experience is that you can make bread display local (if you want).
If you don’t get the resource (FONTs) physically (such as TypeKit works), you need a developing surrounding - e.g. MAMP as a local dev. The path is then something like 127.0.0/bla/bla or whatever, cause you need to enable TypeKit to point back and forth (remote hosting).
On your webfont.css: is the path file to those web fonts correct (depending on where the css file and the web fonts are located)?
Have you added the font-family name exactly as stated in the webfont.css to your font sets within Freeway? – That includes the surrounding single quotes b.t.w.