MICROSOFT SANS SERIF FONT LATEX PDF
MICROSOFT SANS SERIF FONT LATEX SOFTWARE
MICROSOFT SANS SERIF FONT LATEX CODE
MICROSOFT SANS SERIF FONT LATEX PLUS

While they are quite practical and legible, I must beg to differ with DEK about their appropriateness for technical documents. I find moderns make a document look like something from the Victorian era or the 1920s or 30s. Moderns such as CM or Century Schoolbook got done to death in the 19th and first half of the 20th centuries, so they tend to come with a lot of cultural baggage. ITC Garamond (Used extensively by Apple in the 1980s and 1990s) is a re-imagining of Garamond with a larger x-height, so doesn't suffer from this problem. Mixing these inline with a sans-serif typeface with a bigger x-height can look strange. Garamonds, Bembo, Baskerville) look quite nice and are legible in text, but have a low x-height so they need to be set in larger sizes. Traditional old-style or transitional types (e.g. The main reason to avoid these fonts is personal taste or a desire to avoid looking like amateur word processing (which may be more important than you think if you need the document to be taken seriously.) The document will look like something done with MS Word, but the typefaces are serviceable. Stand-bys Times and Arial (or Helvetica) work OK, although I find that Times italic tends not to stand out very well on laser printed documents.

MICROSOFT SANS SERIF FONT LATEX PDF

The Lucida family was also designed to render well on low-res output devices such as screens or early laser printers, so it is a good choice in a font intended for PDF output.

MICROSOFT SANS SERIF FONT LATEX PLUS

Another big plus is that most O/S platforms come with Lucida fonts. It has a pleasant, contemporary look and works well. The Lucida family is designed for this type of work, and has serif, sans-serif and monospace fonts. MacOS and most Linux distros also come with a decent rendition of Palatino from Adobe or URW.

It will go with any of the Sans-serif fonts (Arial, Tahoma, Trebuchet, Calibri etc) that ship with Windows. It got done to death in the DTP era as it came bundled with most Postscript printers, but that is a bit of a dying memory so it can stand on its own merits. Palatino is quite a pleasant typeface for text if you are writing large bodies of prose.

MICROSOFT SANS SERIF FONT LATEX SOFTWARE

Although I briefly worked as a typesetter about 20 years ago most of the technical documentation work I do these days is functional specifications and I am typically constrained by the software available in the client's standard desktop build. If you are stuck with fonts supplied by your operating system vendor then the story is slightly different. If you have the option of buying in the fonts then you can pick any combination that looks appropriate many resources on the web have helpful suggestions for this.

MICROSOFT SANS SERIF FONT LATEX CODE

Also, Courier doesn't really go with anything and the version that ships with most O/S platforms is very light and not terribly legible for reading large code listings. Don't use Courier for this as it is relatively wide other monospace fonts such as Lucida Console will give you more monospaced characters in the same width for the same point size or general legibility. This should visually complement any sans-serif typefaces. If you intend to have code listings or other monospaced items in the document then you will have a third typeface for the monospaced text. If you use a serif font for the body text make sure the texture of the sans-serif font complements but does contrast significantly from the text type. Footnotes will be smaller than the body text, so don't use a font for the body that is too small.Р”Р‡or emphasis, the italic or oblique version of the font should have a noticeably different texture to the body text.Р”Р‡or tables, captions and pull outs you should use a sans-serif font in most cases. If you have a lot of illustrations with labels or captions, pull-outs or tables you might want to use a sans-serif font for the body text and a serif font for headings. It should have a complementary style to your body text, but the headings should provide an obvious visual structure to the document.Р”Р„ decent serif or sans-serif typeface is fine for the body text if you have a lot of prose. The main distinguishing feature of technical documents tends to be complex structure.Р”Р‡or headings, you can use any reasonably legible font this could be serif or sans-serif. Technical documents will have a deeply nested, hierarchical structure, and also make use of footnotes, different types of emphasis, cross-referencing, pull outs and side bars of one sort of another and captions.

Microsoft sans serif font latex