Page 1 of 1

very interesting:file manager vs font-face manager

Posted: Mon Feb 11, 2019 1:17 am
by crownfield
fonts and I are not getting along.
@font-face is confusing me.

what are the _necessary_ and _sufficient_ conditions for @font-face to work?
why does it fail, and not give an error until it publishes?


if I look in filemanager, c:\windows\fonts has my fonts.

in the program tools/fonts/@font-face/ manage my fonts manually
and try 'add' and c:\windows has no font directory,
so I can add no fonts manually.

why would the file manager and @font-face not show the same path?

ok, adobe ps fonts it does not support.
ttf it should support. (ttf should work in almost any browser?)

(windows supports ttf)
(ios supports ttf.
android seems tricky, maybe, maybe not.)

I can see that the fonts work
in windows 7 on one pc, and in 10 on another pc.

any special fonts do not seem to work in iphone 7,
and do not work in an android tablet.

how can I tell which ttf fonts I can use, and which I can not?

Re: very interesting:file manager vs font-face manager

Posted: Mon Feb 11, 2019 3:13 am
by Bluesman
Hi, when using the @font-face option it's best to manually install, so you have ttf and at least .woff files for the actual font.
See: http://www.wysiwygwebbuilder.com/webfonts.html

Re: very interesting:file manager vs font-face manager

Posted: Mon Feb 11, 2019 7:00 am
by Pablo
To make a fonts work in modern browser you will need to include at least two variants: ttf sand woff.
For older devices you may also need to include svg.

Related tutorial:
http://www.wysiwygwebbuilder.com/webfonts.html