In this episode, a truly great and fun conversation with prolific and influential technical writer Tom Johnson. Tom joins us from Silicon Valley to talk about his interesting path to technical communication, failed Career Day booths, being a leader in techcomm, content management systems, DITA, static site generators, and much more.
Subscribe to the Content Content podcast in iTunes
Mentioned during the show: Continue reading Content Content podcast episode 4 – Curse of knowledge with Tom Johnson →
Podcast: Play in new window | Download (Duration: 1:08:29 — 94.1MB)
Subscribe: Google Podcasts | TuneIn | | More
This story is for intermediate to advanced help developers. It requires knowledge of HTML, CSS, and a help authoring tool such as MadCap Flare or Adobe Robohelp.
Have you ever been bored using Georgia, Tahoma, Verdana, and (sigh…) Arial over and over in your help projects? The font-face property has been available for some time in Cascading Style Sheets (CSS), but browser and font foundry support are only now allowing use of fonts other than those that ship with operating systems and applications, without workarounds like sIFR and cufon.
New technologies have sprouted up, with Google creating its own font API, and Adobe announcing font support through TypeKit. However, you can also save and host freely available font files on your company’s web server, or install on your users’ PCs, and use these fonts in your WebHelp projects. The web site Font Squirrel creates the CSS for you, using only free, embeddable fonts.
There are thousands of free fonts out there, but not all font creators support font embedding, so be sure to read any license agreement before using them in your projects.
MadCap’s Flare help authoring tool (HAT) uses CSS to style its WebHelp, so you can easily embed fonts into your help. This should work similarly in Adobe Robohelp. Continue reading How to Embed Fonts in MadCap Flare WebHelp →