Skip to Main Content
2011-12-24 04:54 am (UTC)
While that's a little quicker and will generally work when you as owner are viewing the page, the downside to that is that other users might not be seeing it in that font if they do not have that font installed on their machines.
Say you set it to read in "Arial". If I went to your page and I didn't have Arial installed on my computer I wouldn't be seeing the page the same way you do. I'd see it in whatever the journal backup default or possibly my browser default font happens to be. Depending on whether you're coding for just yourself or for a community of users, this might prove problematic.
The CSS code, however, is the workaround solution. It's a little more time, but with the code in place it doesn't matter if the other user did or did not have the font in question installed, as it's hosted remotely. Essentially, the CSS option just guarantees a little more uniformity, which may or may not be important.
Reply to this
Thread from start
Post a comment in response:
This account has disabled anonymous posting.
You can comment on this post while signed in with an account from many other sites, once you have confirmed your email address.
Sign in using OpenID
If you don't have an account you can
create one now
HTML doesn't work in the subject.
Check spelling during preview
This account is set to log the IP addresses of everyone who comments.
Links will be displayed as unclickable URLs to help prevent spam.
Log in with OpenID?
Forget your password?
Site and Journal Search
Buy Dreamwidth Services
Gift a Random User
Site and Account