Including locally hosted Web Fonts

HI,
been trying nto get a Webfornt working - not from Google, but. locally stored font (for some reason, Sinclair ZX Spectrum fonts aren’t in Google’s library…).

So, I have added the font to the Fonts list, and, yes, Xway displays the font. However, looking at the source, I can’t see any css to load the font. What do I need to do to get Xway to include the font files (ttf, woff, etc) and supporting CSS? The manual doesn’t seem to cover how to handle locally hosted web fonts.

All the best,
Paul.

I don’t know the answer to this off the top of my head, but if you could do it in Freeway you should be able to do it in Xway.

Xway supports the same kind of page markup that Freeway did. There’s a Generic Markup section in the Page Inspector, where you can add markup in the same way that you would have done in Freeway’s HTML Markup dialog (Before </head> etc.) Freeway templates that use web fonts (including Google web fonts) add links via this dialog. Xway makes this a bit easier by providing a field where you can enter a font URL.

If you need to add CSS markup or JavaScript markup, the CSS Markup and JavaScript Markup sections of the Page Inspector provide an easier way of doing this (compared with Generic Markup and Freeway’s HTML Markup).

Hi,
In FReeway, I used an Action to handle the CSS and supporting files. In Xway, I’d need to not just handle the CSS, but the actual font files - ttf, woff, etc… I don’t think there’s anything which allows me to bundle supporting files in the way that I could with Actions.

All the best,
Paul.

I think that’s similar to your previous question about including a file as an external resource, which is on our to-do list.

In the meantime, I think you could upload the fonts using a third-party upload program (Cyberduck etc.)

Hi Jeremy,
in an effort to bend it to my will(!), I have done the following:
1 - Created a Component that contains the font files (.ttf,woff,etc)
2 - Made sure the markup.html file references them.
3 - Put that Component on a blank carrier page.

The font files then end up in the Resources folder.

The CSS with the @fontface code can be put in a markup… Right now, this looks like a useful way to package resources like web fonts for local hosting.

I have to remind myself that this is a 1.0 product, and such activities will hopefully be less necessary.

All the best,
Paul.

1 Like